0x4e6b…5ce2
Paid $0.26 of the $846.98M Roundhouse has indexed across 1,330,524 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (15)
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 | 81% | $0.21 | 13 | 2 |
| Web & Content | 19% | $0.05 | 1 | 1 |
$0.007 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.
- 0xdd25…2ec0 · last paid 17d ago$0.2010 calls
▸23 of 155 catalogued endpoints list a price this agent paid
- /api/seats-aero/searchPrice match$0.02 listed
- /api/google-flights/searchPrice match$0.02 listed
- /api/seats-aero/availability$0.04 listed
- /api/hotels/search$0.03 listed
- /api/flights/search$0.05 listed
- /api/reference/locations$0.0054 listed
- /api/hotels/list$0.03 listed
- /api/flights/availability$0.03 listed
147 further catalogued endpoints not listed.
- 0x8c12…f1b2 · last paid 17d ago$0.051 call
▸2 of 103 catalogued endpoints list a price this agent paid
- /checkSanctions screening$0.01 listed
- /base64-encode-url$0.01 listed
- /twenty-four/daily$0.005 listed
- /transcriptTranscription$0.02 listed
- /searchWeb search$0.02 listed
- /recent$0.005 listed
- /business-days$0.005 listed
- /list$0.005 listed
95 further catalogued endpoints not listed.
- 0x50eb…6480 · last paid 17d ago$0.0073 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x0c66…5462 | $0.00 | $1.00 | 1 | 17d ago | Graph |
| 0xdd25…2ec0 | $0.20 | $0.00 | 10 | 17d ago | Graph |
| 0x8c12…f1b2 | $0.05 | $0.00 | 1 | 17d ago | Graph |
| 0x50eb…6480 | $0.007 | $0.00 | 3 | 17d 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 15 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 0x4e6b…5ce2 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x4e6b84f9c7dec42c976a22f637e3705bbba35ce2
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: 0x4e6b…5ce2 curl -s 'https://api.roundhouseai.io/v0/agents/0x4e6b84f9c7dec42c976a22f637e3705bbba35ce2' curl -s 'https://api.roundhouseai.io/v0/entities/0x4e6b84f9c7dec42c976a22f637e3705bbba35ce2/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.