0x9f5a…a36d
Paid $0.14 of the $3058.83M Roundhouse has indexed across 1,396,904 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (108)
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 | 98% | $0.13 | 80 | 1 |
| Crypto Markets | 2% | $0.0025 | 1 | 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.
- 0xa309…7674 · last paid 1d ago$0.1380 calls
▸24 of 28 catalogued endpoints list a price this agent paid
- /citePrice match$0.001 listed
- /diffPrice match$0.001 listed
- /readabilityPrice match$0.001 listed
- /fieldPrice match$0.002 listed
- /sealedPrice match$0.005 listed
- /verify/sigPrice match$0.002 listed
- /unitPrice match$0.001 listed
- /timePrice match$0.01 listed
20 further catalogued endpoints not listed.
- 0x2b6d…32c5 · last paid 74d ago$0.00251 call
▸23 of 200 catalogued endpoints list a price this agent paid
- /api/timezone/lookupPrice match$0.0025 listed
- /api/calendar/earningsPrice match$0.0025 listed
- /api/stocks/company-newsPrice match$0.0025 listed
- /api/geocode/addressPrice match$0.0025 listed
- /api/econ/fred-vintage$0.0042 listed
- /api/dev/rfc$0.003 listed
- /api/crypto/address-history$0.0036 listed
- /api/search/ai$0.05 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 | |
|---|---|---|---|---|---|
| 0xa309…7674 | $0.13 | $0.05 | 107 | 1d ago | Graph |
| 0x2b6d…32c5 | $0.0025 | $0.00 | 1 | 74d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
99% of observed volume is with a single counterparty, in all 108 observed settlements.
Organic volume $0.18 of $0.18 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 0x9f5a…a36d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9f5a5784d272c09195ced73d6512faa34cd1a36d
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: 0x9f5a…a36d curl -s 'https://api.roundhouseai.io/v0/agents/0x9f5a5784d272c09195ced73d6512faa34cd1a36d' curl -s 'https://api.roundhouseai.io/v0/entities/0x9f5a5784d272c09195ced73d6512faa34cd1a36d/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.