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,689 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%daydreams348d ago0x6cbc40…c92881
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams348d ago0xff9284…acdc70
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams348d ago0xaf1a64…439f68
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams348d ago0x224649…907c89
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams348d ago0x9ea5b3…7c0d00
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams349d ago0xa4f05a…8442cd
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams349d ago0x97ce95…98498b
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams349d ago0x15c09b…3f1709
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams349d ago0xbda9e6…11d700
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams349d ago0x3f25e4…efd1da
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams349d ago0xb5c330…dc02aa
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams350d ago0x286a6e…da6a03
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams350d ago0xa666b9…5041d8
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams350d ago0x323f54…a05ce3
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams350d ago0xe8dce0…e3f61b
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams351d ago0x117921…59546d
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams351d ago0x6c0b40…4922b8
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams351d ago0x23b933…e95689
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams351d ago0x4e3df7…eb42df
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams351d ago0xf320fa…7bbe3b
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams351d ago0x0093db…13941a
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams351d ago0xe792f7…b72ed7
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams351d ago0x776361…edd585
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams352d ago0x0d5814…818f91
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams352d ago0x6ccca5…9562ea

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.