AgentReport

0x2921…dad8

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

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,255 wallets — less than 0.0001% of it.

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

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.032631

$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
    263 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.00263276d 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 263 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams325d ago0x457e5c…88382e
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams325d ago0xcac8d1…671df9
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams325d ago0x0c49b7…539553
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams325d ago0x3d1529…a8175d
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams326d ago0xef2dbf…edb9d2
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams326d ago0xca8348…a7c2e3
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams326d ago0xaff6d9…ce400c
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams326d ago0xc4930f…80c0ce
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams326d ago0xf8d331…4e102f
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams326d ago0x036fe1…faba77
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams326d ago0xd07706…119f4e
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams326d ago0x91e1ce…bf08d8
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams326d ago0x81a649…a53ada
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams327d ago0x84a388…83e987
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams327d ago0x568f0b…b74e9a
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams327d ago0x469c0c…38f855
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams327d ago0xd36f5a…da681b
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams327d ago0x00737e…1831fc
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams327d ago0x422fa4…c2ec42
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams327d ago0x385058…445804
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams327d ago0x845ea3…46d422
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams335d ago0xb3f01b…246360
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams335d ago0x128b6d…6619a5
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams337d ago0x9ed793…0f5317
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams337d ago0x77efd4…55d153

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 0x2921…dad8 has actually paid for over the free read API. No key, no account.

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

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: 0x2921…dad8

curl -s 'https://api.roundhouseai.io/v0/agents/0x2921d811c5d9759ceee360e79d5f4ff79fe1dad8'
curl -s 'https://api.roundhouseai.io/v0/entities/0x2921d811c5d9759ceee360e79d5f4ff79fe1dad8/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.