0xcf93…a9fd
Paid $0.13 of the $3059.45M Roundhouse has indexed across 1,397,282 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (28)
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% | $0.13 | 28 | 3 |
$0.04 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.
- 0x3f4c…049b · last paid 29d ago$0.0815 calls
▸2 of 20 catalogued endpoints list a price this agent paid
- /api/trust/check-x402Price match$0.005 listed
- /api/trust/check-x402Price match$0.005 listed
- /api/trust/score-resource$0.01 listed
- /api/trust/score-resource$0.01 listed
- /api/procurement/plan$0.02 listed
- /api/monitor/snapshot$0.02 listed
- /api/procurement/plan$0.02 listed
- /api/procurement/quote$0.04 listed
12 further catalogued endpoints not listed.
- 0x0e52…36b1 · last paid 28d ago$0.048 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x7511…62b8 · last paid 59d ago$0.025 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/execute/webhookPrice match$0.003 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 | |
|---|---|---|---|---|---|
| 0x3f4c…049b | $0.08 | $0.00 | 15 | 29d ago | Graph |
| 0x0e52…36b1 | $0.04 | $0.00 | 8 | 28d ago | Graph |
| 0x7511…62b8 | $0.02 | $0.00 | 5 | 59d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
58% of observed volume is with a single counterparty, in all 28 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 0xcf93…a9fd has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xcf93dbe86553c8cce5888afb4f69ed9208f3a9fd
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: 0xcf93…a9fd curl -s 'https://api.roundhouseai.io/v0/agents/0xcf93dbe86553c8cce5888afb4f69ed9208f3a9fd' curl -s 'https://api.roundhouseai.io/v0/entities/0xcf93dbe86553c8cce5888afb4f69ed9208f3a9fd/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.