0x65d8…b4b6
Paid $0.40 of the $259.14M Roundhouse has indexed across 714,236 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (17)
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 |
|---|---|---|---|---|
| Reference Data | 75% | $0.30 | 15 | 1 |
| Web & Content | 25% | $0.10 | 2 | 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.
- 0x3783…3c5d · last paid 63d ago$0.3015 calls
▸15 of 27 catalogued endpoints list a price this agent paid
- /company/:cik/financialsPrice match$0.02 listed
- /company/:cik/filingsPrice matchSEC filings$0.005 listed
- /aggregate/:metricPrice match$0.05 listed
- /screenPrice matchSEC filings$0.10 listed
- /company/:cik/factsPrice match$0.01 listed
- /compare/:cikPrice match$0.05 listed
- /company/320193/insiderPrice matchSEC filings$0.02 listed
- /company/320193/signalPrice matchSEC filings$0.05 listed
19 further catalogued endpoints not listed.
- 0xa98e…50eb · last paid 69d ago$0.102 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /v1/parsePrice matchPage to markdown$0.05 listed
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 | |
|---|---|---|---|---|---|
| 0x3783…3c5d | $0.30 | $0.00 | 15 | 63d ago | Graph |
| 0xa98e…50eb | $0.10 | $0.00 | 2 | 69d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
75% of observed volume is with a single counterparty, in all 17 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 0x65d8…b4b6 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x65d8f2b228478f2f2d83205c1df7bc357b35b4b6
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: 0x65d8…b4b6 curl -s 'https://api.roundhouseai.io/v0/agents/0x65d8f2b228478f2f2d83205c1df7bc357b35b4b6' curl -s 'https://api.roundhouseai.io/v0/entities/0x65d8f2b228478f2f2d83205c1df7bc357b35b4b6/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.