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 $3068.58M Roundhouse has indexed across 1,402,563 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%daydreams324d ago0x9ec154…d6dac9
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams324d ago0xd5153f…c38fab
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams324d ago0x4765d2…9727f1
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams324d ago0xe37417…d7c3d5
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams324d ago0x06b110…6d4c0d
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams324d ago0xebcd4a…9af929
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams324d ago0x160cb2…6d7823
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams324d ago0x6ae715…47a4f0
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams324d ago0x5e7ee1…aa2d06
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams324d ago0x5b29df…3ffa83
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams325d ago0x859eb6…eeab64
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams325d ago0x662a39…b28ad0
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams325d ago0x086cf4…4ee9cb
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams325d ago0x9aa755…a580f4
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams325d ago0x74aa82…b41f62
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams325d ago0x78373a…66a00b
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams325d ago0x9441d7…a5dba1
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams325d ago0x91e85d…0813fe
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams325d ago0x30443b…02a405
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams325d ago0xba08b6…173c3e
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams326d ago0x3d0665…4cc6c9
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams326d ago0x437ec9…e2cef3
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams326d ago0xd552c5…9aa316
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams326d ago0x5ddc70…7e412f
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams326d ago0x4ecd6d…30ab71

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.