0x9ae6…3f3c
Paid $0.05 of the $258.47M Roundhouse has indexed across 713,069 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (22)
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.05 | 22 | 2 |
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.
- 0xbecc…dd0f · last paid 42d ago$0.0421 calls
▸2 of 2 catalogued endpoints list a price this agent paid
- /vulnscan/cve/CVE-2021-44228Price match$0.002 listed
- /ledger/reports/trial-balancePrice match$0.002 listed
- 0x9f54…ece4 · last paid 32d ago$0.0051 call
▸1 of 2 catalogued endpoints list a price this agent paid
- /api/metaPrice match$0.005 listed
- /api/extractPage to markdown$0.01 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 | |
|---|---|---|---|---|---|
| 0xbecc…dd0f | $0.04 | $0.00 | 21 | 42d ago | Graph |
| 0x9f54…ece4 | $0.005 | $0.00 | 1 | 32d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
89% of observed volume is with a single counterparty, in all 22 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 0x9ae6…3f3c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9ae6417e027d19014cb1b87457c5e60b5ab23f3c
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: 0x9ae6…3f3c curl -s 'https://api.roundhouseai.io/v0/agents/0x9ae6417e027d19014cb1b87457c5e60b5ab23f3c' curl -s 'https://api.roundhouseai.io/v0/entities/0x9ae6417e027d19014cb1b87457c5e60b5ab23f3c/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.