0x240d…5ddf
Paid $5.19 of the $260.32M Roundhouse has indexed across 716,001 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (323)
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 | 77% | $3.99 | 188 | 1 |
| Web & Content | 23% | $1.20 | 135 | 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.
- 0xdd25…2ec0 · last paid 113d ago$3.99188 calls
▸38 of 141 catalogued endpoints list a price this agent paid
- /api/seats-aero/searchPrice match$0.02 listed
- /api/hotels/searchPrice match$0.03 listed
- /api/reference/locationsPrice match$0.0054 listed
- /api/hotels/listPrice match$0.03 listed
- /api/flights/availabilityPrice match$0.03 listed
- /api/hotels/autocompletePrice match$0.0054 listed
- /api/seats-aero/availability$0.04 listed
- /api/flights/search$0.05 listed
133 further catalogued endpoints not listed.
- 0x6d6e…9192 · last paid 122d ago$1.20135 calls
▸2 of 3 catalogued endpoints list a price this agent paid
- /searchPrice matchWeb search$0.007 listed
- /pay/agent_exa_aiPrice match$0.007 listed
- /contents$0.001 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 | |
|---|---|---|---|---|---|
| 0xdd25…2ec0 | $3.99 | $0.00 | 188 | 113d ago | Graph |
| 0x6d6e…9192 | $1.20 | $0.00 | 135 | 122d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
77% of observed volume is with a single counterparty, in all 323 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 0x240d…5ddf has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x240ddd7bb9faa87d758a0bbdd424089040ea5ddf
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: 0x240d…5ddf curl -s 'https://api.roundhouseai.io/v0/agents/0x240ddd7bb9faa87d758a0bbdd424089040ea5ddf' curl -s 'https://api.roundhouseai.io/v0/entities/0x240ddd7bb9faa87d758a0bbdd424089040ea5ddf/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.