0x01e5…c8d2
Paid $5.00 of the $844.70M Roundhouse has indexed across 1,326,449 wallets — less than 0.0001% of it.
Floors, not totals: this wallet has more history than one scan returns, and the index rollup has no row for it yet, so the figures above count only its 1,000 most recent settlements.
Chains (from the recent scan): Base (1000)
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 |
|---|---|---|---|---|
| Risk & Compliance | 100% | $5.00 | 1,000 | 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 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0xf732…b829 · last paid 4m ago$5.001,000 calls
▸122 of 122 catalogued endpoints list a price this agent paid
- /v1/meadowPrice match$0.005 listed
- /v1/prompt-injection-detectPrice match$0.005 listed
- /v1/agentsearch-web-search-v1Price match$0.005 listed
- /v1/meme-watchPrice match$0.005 listed
- /v1/pump-checkPrice match$0.005 listed
- /v1/taint-checkPrice match$0.005 listed
- /v1/dns-whois-rdapPrice match$0.005 listed
- /v1/kr-apt-trades-v1Price match$0.005 listed
114 further catalogued endpoints not listed.
Folded from this wallet's 1,000 most recent settlements, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not. One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xf732…b829 | $5.00 | $0.00 | 1,000 | 4m ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).
Organic volume $5.00 of $5.00 total.
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 0x01e5…c8d2 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x01e58af1dd85b548f9852aa7ad7584f4853bc8d2
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: 0x01e5…c8d2 curl -s 'https://api.roundhouseai.io/v0/agents/0x01e58af1dd85b548f9852aa7ad7584f4853bc8d2' curl -s 'https://api.roundhouseai.io/v0/entities/0x01e58af1dd85b548f9852aa7ad7584f4853bc8d2/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.