AgentReport

0x2204…0502

0x2204f5bcabeb4fd7a52741fc802d1a1937ec0502Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
273
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (273)

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.032731

$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 277d ago
    $0.03
    273 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.00273277d 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 273 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0xda0543…a2e3dd
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0x6b1859…aca984
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0x7eec41…25c404
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0xf91e50…d12a4e
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0xd604e6…259497
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0x559c76…6a048a
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0x40ca08…bd94e1
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0x1c3892…d41ca7
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0x654c04…d8a62f
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0x7405a8…5ddb91
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams344d ago0x534ef3…104e9a
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0x690878…7587e5
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0xdb7f09…c4f5ae
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0xa83378…7e8c9b
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0xc8f377…4e7ce0
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0xd9b886…049764
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0xa3ba8b…8a12bf
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0x3e8607…a2e370
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0x8da6ca…5d26fd
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0xd6e24a…0538ac
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0x4aea82…a3f74c
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0x34c055…87d85d
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams345d ago0xf3bc16…11af82
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams346d ago0x693471…60b44e
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams346d ago0x6e838c…9bcf61

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 0x2204…0502 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x2204f5bcabeb4fd7a52741fc802d1a1937ec0502

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: 0x2204…0502

curl -s 'https://api.roundhouseai.io/v0/agents/0x2204f5bcabeb4fd7a52741fc802d1a1937ec0502'
curl -s 'https://api.roundhouseai.io/v0/entities/0x2204f5bcabeb4fd7a52741fc802d1a1937ec0502/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.