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,510 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%daydreams345d ago0x04dfca…4f241f
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams345d ago0x5eca37…4f6a97
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams345d ago0xb55032…8ba0af
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0x04512a…8cf61e
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0xe552d0…427dc3
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0xc19702…dfdf1b
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0x4efc42…4780fa
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0x0707a8…55de54
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0x9cc099…6c1b5f
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0x90a71d…91f69e
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0xe21ce4…10961f
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0xa816ca…e34f1c
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0xc777bd…b04849
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams346d ago0x0da8c4…e63217
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams347d ago0xfc95c8…55f316
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams347d ago0x06ec61…4c42e4
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams347d ago0xe1883b…5cda09
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams347d ago0xf748dd…65a3ad
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams347d ago0x7032c7…d72d08
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams348d ago0x3badeb…be4ca0
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams348d ago0x9f561c…2a97c2
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams348d ago0x941861…53c4ab
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams348d ago0xc2f9a9…e21e63
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams348d ago0xf0a836…ba683f
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams348d ago0x542bb5…472f37

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.