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%daydreams323d ago0x27ffb9…6c5d81
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams323d ago0x4dac1b…039da9
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams323d ago0x633bab…e3b4f6
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams323d ago0xb2ef5a…35260c
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams323d ago0x2ff689…633ca0
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams323d ago0x61fec3…34a59f
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams323d ago0x5c0e90…2bda57
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams323d ago0x801b7d…045809
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams323d ago0xda472f…834daa
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0xa6c094…d812b3
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0x68218c…ab759b
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0x45505c…d5bd55
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0x816d44…98ff96
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0x57e15f…8407ea
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0x8ab71f…dc734f
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0x999183…a0e9b8
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0xa944d2…d0adc9
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0xaed696…e9c2e9
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0x27cace…c48b4b
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams324d ago0x228352…4eb0df
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams325d ago0xb626ac…e49fb9
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams325d ago0xfec2f8…cf5d47
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams325d ago0x468f70…07f96e
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams325d ago0x7de861…805da7
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams325d ago0x2d1445…d07dc1

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.