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%daydreams343d ago0x0b7c17…98cf56
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams343d ago0x2328db…1fa0b3
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams343d ago0x899ea9…b6b619
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams343d ago0x98fdb9…b39c7a
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams343d ago0x50a5b7…c41179
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams343d ago0xd1acf0…263a96
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams343d ago0x60f4af…3f3cc4
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams344d ago0x7146ec…2c1c6a
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams344d ago0x4cfaf4…466d07
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams344d ago0x5e18f3…866e08
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams344d ago0xce6b2e…663a1e
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams344d ago0x60097d…39c4ab
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams344d ago0x7207fd…7612f0
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams344d ago0xf7f4f3…4a1366
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams344d ago0x872f20…c02241
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams344d ago0x22625f…1e4791
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams344d ago0xb5e3a8…8bc597
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams345d ago0x57d881…085023
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams345d ago0x6f4558…2df41f
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams345d ago0x586355…db538f
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams345d ago0x2d8f4e…bda89a
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams345d ago0x76ea5a…c56da7
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams345d ago0x082a92…e4dfb4
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams345d ago0x4089dd…aa80ee
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams345d ago0x543c97…e0d9ac

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.