0x88cd…3aed
Paid $5.00 of the $258.78M Roundhouse has indexed across 713,781 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (104)
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% | $5.00 | 104 | 2 |
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.
- 0x0704…7ceb · last paid 227d ago$4.004 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/vote/mintPrice match$1.00 listed
- 0xec70…e2b3 · last paid 3h ago$1.00100 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/votePrice match$0.01 listed
ERC-8004 registration
- Declares 2 endpoints, and 2 are in a public catalogue
Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1
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 | |
|---|---|---|---|---|---|
| 0x0704…7ceb | $4.00 | $0.00 | 4 | 227d ago | Graph |
| 0xec70…e2b3 | $1.00 | $0.00 | 100 | 3h 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 104 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 0x88cd…3aed has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x88cd8e166e4c36855a7311e84808a82ac0123aed
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: 0x88cd…3aed curl -s 'https://api.roundhouseai.io/v0/agents/0x88cd8e166e4c36855a7311e84808a82ac0123aed' curl -s 'https://api.roundhouseai.io/v0/entities/0x88cd8e166e4c36855a7311e84808a82ac0123aed/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.