0x96af…0501
Paid $15.00 of the $846.52M Roundhouse has indexed across 1,329,508 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (6)
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% | $15.00 | 6 | 2 |
$10.00 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 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x55d2…f1dd · last paid 362d ago$10.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xffb3…d1ed · last paid 366d ago$5.005 calls
▸1 of 2 catalogued endpoints list a price this agent paid
- /mint?amount=1Price match$1.00 listed
- /mint10$10.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 | |
|---|---|---|---|---|---|
| 0x55d2…f1dd | $10.00 | $0.00 | 1 | 362d ago | Graph |
| 0xffb3…d1ed | $5.00 | $0.00 | 5 | 366d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
67% of observed volume is with a single counterparty, in all 6 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x96af…05010x55d2…f1dd | Base | $10.00 | 100% | payAI | 362d ago | 0x1fbd7f…b173a5 |
| 0x96af…05010xffb3…d1ed | Base | $1.00 | 100% | payAI | 366d ago | 0x4b716a…7c8f38 |
| 0x96af…05010xffb3…d1ed | Base | $1.00 | 100% | payAI | 366d ago | 0x44b812…3bf7f3 |
| 0x96af…05010xffb3…d1ed | Base | $1.00 | 100% | payAI | 366d ago | 0xbee362…e1bd23 |
| 0x96af…05010xffb3…d1ed | Base | $1.00 | 100% | payAI | 366d ago | 0x4679e2…5ecb70 |
| 0x96af…05010xffb3…d1ed | Base | $1.00 | 100% | payAI | 366d ago | 0x91f2d8…21af04 |
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 0x96af…0501 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x96af6c8235d8d0e1a3dc73890a421f7ce3400501
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: 0x96af…0501 curl -s 'https://api.roundhouseai.io/v0/agents/0x96af6c8235d8d0e1a3dc73890a421f7ce3400501' curl -s 'https://api.roundhouseai.io/v0/entities/0x96af6c8235d8d0e1a3dc73890a421f7ce3400501/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.