0x97d2…ba2b
Paid $0.99 of the $3058.83M Roundhouse has indexed across 1,396,716 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (449)
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 | 80% | $0.79 | 445 | 1 |
| Risk & Compliance | 20% | $0.20 | 4 | 1 |
$0.79 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 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x4baf…1ebe · last paid 29d ago$0.79445 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x52ab…6c06 · last paid 30d ago$0.204 calls
▸69 of 118 catalogued endpoints list a price this agent paid
- /tradesPrice match$0.05 listed
- /pay/agent_labor_lonestaroracle_xyzPrice match$0.05 listed
- /pay/agent_metals_lonestaroracle_xyzPrice match$0.05 listed
- /ratesPrice matchCurrency conversion$0.05 listed
- /hazardPrice match$0.05 listed
- /analyzePrice match$0.05 listed
- /readPage to markdown$0.005 listed
- /calendar$0.03 listed
110 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0x4baf…1ebe | $0.79 | $0.00 | 445 | 29d ago | Graph |
| 0x52ab…6c06 | $0.20 | $0.00 | 4 | 30d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
80% of observed volume is with a single counterparty, in all 449 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 0x97d2…ba2b has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x97d28af4763aba1012f08a1060a5aea3ab5cba2b
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: 0x97d2…ba2b curl -s 'https://api.roundhouseai.io/v0/agents/0x97d28af4763aba1012f08a1060a5aea3ab5cba2b' curl -s 'https://api.roundhouseai.io/v0/entities/0x97d28af4763aba1012f08a1060a5aea3ab5cba2b/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.