0x91e4…789d
Paid $0.29 of the $847.14M Roundhouse has indexed across 1,330,737 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (150)
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 | 100% | $0.29 | 150 | 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.
- 0x2b6d…32c5 · last paid 87d ago$0.29150 calls
▸80 of 200 catalogued endpoints list a price this agent paid
- /api/timezone/lookup$0.0025 listed
- /api/econ/fred-vintage$0.0042 listed
- /api/dev/rfc$0.003 listed
- /api/search/ai$0.05 listed
- /api/stocks/company-news$0.0025 listed
- /api/calendar/earnings$0.0025 listed
- /api/geocode/address$0.0025 listed
- /api/crypto/address-history$0.0036 listed
192 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| 0x2b6d…32c5 | $0.29 | $0.00 | 150 | 87d 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 all 150 observed settlements.
Organic volume $0.29 of $0.29 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 0x91e4…789d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x91e45e705a3b3a9a370fcf8f5d567a746d3b789d
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: 0x91e4…789d curl -s 'https://api.roundhouseai.io/v0/agents/0x91e45e705a3b3a9a370fcf8f5d567a746d3b789d' curl -s 'https://api.roundhouseai.io/v0/entities/0x91e45e705a3b3a9a370fcf8f5d567a746d3b789d/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.