0xe372…b5f0
Paid $4.77 of the $3105.03M Roundhouse has indexed across 1,405,088 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (494)
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 |
|---|---|---|---|---|
| Web & Content | 90% | $4.27 | 493 | 1 |
| Not in any catalogue | 10% | $0.50 | 1 | 1 |
$0.50 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 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xdd5f…1ba6 · last paid 111d ago$4.27493 calls
▸76 of 76 catalogued endpoints list a price this agent paid
- /api/geoPrice match$0.001 listed
- /v1/messagesPrice match$0.01 listed
- /api/generate-imagePrice match$0.07 listed
- /api/wp/assessPrice match$0.005 listed
- /api/geoPrice match$0.001 listed
- /api/seo/site-auditPrice match$0.05 listed
- /api/seo/alt-checkPrice match$0.001 listed
- /api/pingPrice match$0.001 listed
68 further catalogued endpoints not listed.
- 0x2985…14f2 · last paid 111d ago$0.501 call
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.
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 | |
|---|---|---|---|---|---|
| 0xdd5f…1ba6 | $4.27 | $0.00 | 493 | 111d ago | Graph |
| 0x2985…14f2 | $0.50 | $0.00 | 1 | 111d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
90% of observed volume is with a single counterparty, in all 494 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 0xe372…b5f0 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xe3724232cd926d708737bddaa7b60e36d4bfb5f0
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: 0xe372…b5f0 curl -s 'https://api.roundhouseai.io/v0/agents/0xe3724232cd926d708737bddaa7b60e36d4bfb5f0' curl -s 'https://api.roundhouseai.io/v0/entities/0xe3724232cd926d708737bddaa7b60e36d4bfb5f0/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.