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%daydreams341d ago0x7a9118…f36b79
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams341d ago0x8a4a66…4eca32
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams341d ago0x6907f5…527dcf
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams341d ago0x02d5cc…417e69
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams341d ago0x8ba3a1…38eefc
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams341d ago0x5bf461…457e22
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams341d ago0xbb07a8…56fec9
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams341d ago0x11d23d…75481b
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams341d ago0xce66dc…bb4a3a
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams341d ago0xce08a9…e037d0
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0x8ba5b0…f13e8c
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0x571b36…24060b
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0xb02b35…d564ba
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0xde0187…68378d
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0x40d146…036663
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0xace55b…5ca396
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0x8cce65…be817e
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0xd90712…144a55
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0x764d37…e2665d
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0x3fd7c4…8006af
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams342d ago0x4a2c4a…8bdcbf
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams343d ago0xa6d7f9…82a843
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams343d ago0x171b93…f14924
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams343d ago0x523f6e…92b950
0x2921…dad80x6482…b779BaseBase$0.0001100%daydreams343d ago0xb33777…62f4ba

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.