0x53f7…f263
Paid $1.75 of the $846.98M Roundhouse has indexed across 1,330,524 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (16)
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.
| Group | Share | Spent | Calls | Sellers |
|---|---|---|---|---|
| Not in any catalogue | 100% | $1.75 | 16 | 3 |
$1.00 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; for 2 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x5da4…6c70 · last paid 2d ago$1.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xa26f…8147 · last paid 1d ago$0.6410 calls
▸5 of 5 catalogued endpoints list a price this agent paid
- /api/firm/risk-snapshotPrice match$0.03 listed
- /api/x402/approval-enumeratePrice match$0.03 listed
- /api/x402/invoice-decodePrice match$0.02 listed
- /api/x402/settlement-statusPrice match$0.02 listed
- /api/x402/preflightPrice match$0.05 listed
- 0xacfc…fb30 · last paid 1d ago$0.115 calls
▸3 of 3 catalogued endpoints list a price this agent paid
- /api/signal/:assetPrice match$0.003 listed
- /api/brief/:assetPrice match$0.03 listed
- /api/signal-batchPrice match$0.02 listed
Funds flow over time
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x5da4…6c70 | $1.00 | $0.00 | 1 | 2d ago | Graph |
| 0xa26f…8147 | $0.64 | $0.00 | 10 | 1d ago | Graph |
| 0xacfc…fb30 | $0.11 | $0.00 | 5 | 1d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
57% of observed volume is with a single counterparty, in all 16 observed settlements.
Recent activity
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 0x53f7…f263 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x53f7ad05a4bfd60c6d18527b001eaf213605f263
Show the promptHide 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: 0x53f7…f263 curl -s 'https://api.roundhouseai.io/v0/agents/0x53f7ad05a4bfd60c6d18527b001eaf213605f263' curl -s 'https://api.roundhouseai.io/v0/entities/0x53f7ad05a4bfd60c6d18527b001eaf213605f263/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.