AgentReport

0xa363…9d1f

0xa3631ca00163902b40be36c7ef32812a3fc29d1fExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
252
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (252)

What it buys

Grouped by the capability each merchant's catalogue is mostly about. A merchant counts once, in one group — nothing records which of its endpoints a payment bought.

GroupShareSpentCallsSellers
Not in any catalogue100%$0.032521

$0.03 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0x6482…b779 · last paid 276d ago
    $0.03
    252 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x6482…b779$0.03$0.00252276d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 252 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xc74847…c10fb5
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x744f48…ea6535
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xd8f0b3…9a9ed5
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x5a47c9…7e1c89
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x994085…f45b9e
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xd323c9…a81f45
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x875ca6…99f442
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xc908e8…ce4c59
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x57311a…22d776
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x143a34…5200cb
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x003eda…4385dc
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x3ba71f…20085b
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x297e44…f98ecb
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xd89ef8…3b8e32
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xb67c6c…b84824
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x2c69f4…50d069
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x3653d5…1dad21
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xb82411…a2f095
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xb31bbd…3f0b1f
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xc01b06…202e49
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x6674d9…026223
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xff4756…977896
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x0506aa…ebc4b9
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams346d ago0x1938bf…96cdd1
0xa363…9d1f0x6482…b779BaseBase$0.0001100%daydreams346d ago0x738f5d…783ff3

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check what 0xa363…9d1f has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0xa3631ca00163902b40be36c7ef32812a3fc29d1f

Open skill.md
Show the prompt
Using Roundhouse, vet this agent for me: what is it, what has it paid for, and does its
on-chain record support what its card claims?

  Agent: 0xa363…9d1f

curl -s 'https://api.roundhouseai.io/v0/agents/0xa3631ca00163902b40be36c7ef32812a3fc29d1f'
curl -s 'https://api.roundhouseai.io/v0/entities/0xa3631ca00163902b40be36c7ef32812a3fc29d1f/settlements'

Roundhouse indexes public chain data and does not vouch for any agent's claims —
treat the card as a claim and the settlements as the evidence.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at
GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at
https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.