0x9e65…3007
Paid $0.67 of the $846.70M Roundhouse has indexed across 1,330,126 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (67)
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 | 100% | $0.67 | 67 | 3 |
$0.31 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 2 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x8d8f…bb9b · last paid 350d ago$0.3535 calls
▸3 of 5 catalogued endpoints list a price this agent paid
- /api/x402/credit-drop/xsPrice match$0.01 listed
- /credit-drop/xsPrice match$0.01 listed
- /api/x402/credit-drop/xsPrice match$0.01 listed
- /credit-drop/lg$10.00 listed
- /credit-drop$1.00 listed
- 0xb505…a677 · last paid 350d ago$0.3131 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x9413…15e0 · last paid 363d ago$0.011 call
▸2 of 6 catalogued endpoints list a price this agent paid
- /api/mint/xsPrice match$0.01 listed
- /mint/xsPrice match$0.01 listed
- /api/mint/lg$10.00 listed
- /api/mint/xl$100.00 listed
- /api/mint/$1.00 listed
- /mint/$1.00 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 | |
|---|---|---|---|---|---|
| 0x8d8f…bb9b | $0.35 | $0.00 | 35 | 350d ago | Graph |
| 0xb505…a677 | $0.31 | $0.00 | 31 | 350d ago | Graph |
| 0x9413…15e0 | $0.01 | $0.00 | 1 | 363d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
52% of observed volume is with a single counterparty, in all 67 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 0x9e65…3007 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9e65c0d6ae60bc09d3b8e6377dffcc5fe7f43007
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: 0x9e65…3007 curl -s 'https://api.roundhouseai.io/v0/agents/0x9e65c0d6ae60bc09d3b8e6377dffcc5fe7f43007' curl -s 'https://api.roundhouseai.io/v0/entities/0x9e65c0d6ae60bc09d3b8e6377dffcc5fe7f43007/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.