0x9b1c…c0f3
Paid $0.03 of the $3059.84M Roundhouse has indexed across 1,397,384 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
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.03 | 2 | 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 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xf338…97ea · last paid 273d ago$0.021 call
▸1 of 3 catalogued endpoints list a price this agent paid
- /api/image/createPrice match$0.02 listed
- /api/video/create-sora2$0.20 listed
- /api/video/create$0.20 listed
- 0x749b…54ce · last paid 273d ago$0.011 call
▸3 catalogued endpoints, none priced at an amount this agent paid
- /api/image/generate$0.001 listed
- /api/image/generate$0.001 listed
- /protected$0.001 listed
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xf338…97ea | $0.02 | $0.00 | 1 | 273d ago | Graph |
| voicefirstllc.eth | $0.01 | $0.00 | 1 | 273d 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 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x9b1c…c0f30xf338…97ea | Base | $0.02 | 100% | coinbase | 273d ago | 0xc37211…ac919a |
| 0x9b1c…c0f3voicefirstllc.eth | Base | $0.01 | 100% | coinbase | 273d ago | 0xa2e176…def321 |
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 0x9b1c…c0f3 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9b1cfc101cc0202bafb53e7d8ab75b791ad6c0f3
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: 0x9b1c…c0f3 curl -s 'https://api.roundhouseai.io/v0/agents/0x9b1cfc101cc0202bafb53e7d8ab75b791ad6c0f3' curl -s 'https://api.roundhouseai.io/v0/entities/0x9b1cfc101cc0202bafb53e7d8ab75b791ad6c0f3/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.