0x88b8…e0b0
Paid $0.07 of the $3059.45M Roundhouse has indexed across 1,397,282 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (19)
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.06 | 16 | 1 |
| Reference Data | 20% | $0.02 | 3 | 1 |
Every merchant paid publishes at least one catalogued endpoint.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xb847…771e · last paid 35d ago$0.0616 calls
▸2 of 2 catalogued endpoints list a price this agent paid
- /v1/mcp-operation-risk/evaluatePrice match$0.0045 listed
- /api/convert-weightPrice match$0.002 listed
- 0xabf4…a9d0 · last paid 42d ago$0.023 calls
▸39 of 200 catalogued endpoints list a price this agent paid
- /api/onchain-sql$0.04 listed
- /api/perp-basis$0.002 listed
- /api/perp-fundingPerp funding and open interest$0.002 listed
- /v1/metered/chat/completionsText completion$0.001 listed
- /api/hash$0.001 listed
- /api/weather-historyWeather forecast$0.002 listed
- /api/searchWeb search$0.01 listed
- /v1/nano/chat/completionsText completion$0.003 listed
192 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 | |
|---|---|---|---|---|---|
| 0xb847…771e | $0.06 | $0.00 | 16 | 35d ago | Graph |
| 0xabf4…a9d0 | $0.02 | $0.00 | 3 | 42d 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 19 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 0x88b8…e0b0 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x88b806f73d3697914e2b25b814214b3d63e0e0b0
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: 0x88b8…e0b0 curl -s 'https://api.roundhouseai.io/v0/agents/0x88b806f73d3697914e2b25b814214b3d63e0e0b0' curl -s 'https://api.roundhouseai.io/v0/entities/0x88b806f73d3697914e2b25b814214b3d63e0e0b0/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.