0x9a6e…41a9
Paid $0.97 of the $3061.41M Roundhouse has indexed across 1,398,256 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (170)
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 | 82% | $0.80 | 156 | 2 |
| Risk & Compliance | 18% | $0.17 | 14 | 1 |
$0.04 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.
- 0x3dcb…32e1 · last paid 113d ago$0.75151 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /us/gdpPrice match$0.005 listed
- 0xb3e7…bf5b · last paid 99d ago$0.1714 calls
▸5 of 5 catalogued endpoints list a price this agent paid
- /helloPrice match$0.001 listed
- /verifyPrice match$0.01 listed
- /screenPrice matchSanctions screening$0.01 listed
- /x402/kh7fe77q59v3ah76e7xtmnsqk58atbbkPrice match$0.001 listed
- /screen/batchPrice match$0.04 listed
- 0x9b68…398b · last paid 114d ago$0.045 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
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 | |
|---|---|---|---|---|---|
| 0x3dcb…32e1 | $0.75 | $0.00 | 151 | 113d ago | Graph |
| 0xb3e7…bf5b | $0.17 | $0.00 | 14 | 99d ago | Graph |
| 0x9b68…398b | $0.04 | $0.00 | 5 | 114d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
78% of observed volume is with a single counterparty, in all 170 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 0x9a6e…41a9 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9a6e0ec4ed901f9340b9497fbd03c7284cff41a9
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: 0x9a6e…41a9 curl -s 'https://api.roundhouseai.io/v0/agents/0x9a6e0ec4ed901f9340b9497fbd03c7284cff41a9' curl -s 'https://api.roundhouseai.io/v0/entities/0x9a6e0ec4ed901f9340b9497fbd03c7284cff41a9/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.