0xaf85…0c04
Paid $0.01 of the $3105.41M Roundhouse has indexed across 1,406,887 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (3)
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 |
|---|---|---|---|---|
| AI & Media | 91% | $0.01 | 1 | 1 |
| Not in any catalogue | 9% | $0.001 | 2 | 1 |
$0.001 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.
- 0x6302…ad57 · last paid 139d ago$0.011 call
▸33 of 53 catalogued endpoints list a price this agent paid
- /api/v1/location/searchPrice match$0.01 listed
- /v1/speakPrice matchText to speech$0.01 listed
- /api/v1/location/nearby_searchPrice match$0.01 listed
- /listings/salePrice match$0.01 listed
- /api/v1/location/:locationId/reviewsPrice match$0.01 listed
- /createTaskPrice match$0.01 listed
- /v1/simplePrice match$0.01 listed
- /take$0.02 listed
45 further catalogued endpoints not listed.
- 0x7e34…eb94 · last paid 139d ago$0.0012 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x6302…ad57 | $0.01 | $0.00 | 1 | 139d ago | Graph |
| 0x7e34…eb94 | $0.001 | $0.00 | 2 | 139d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
91% of observed volume is with a single counterparty, in all 3 observed settlements.
Organic volume $0.01 of $0.01 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xaf85…0c040x6302…ad57 | Base | $0.01 | 100% | payAI | 139d ago | 0x98bbaa…46ab8e |
| 0xaf85…0c040x7e34…eb94 | Base | $0.0005 | 70% | 0x7e34…eb94 | 139d ago | 0x52051f…b26014 |
| 0xaf85…0c040x7e34…eb94 | Base | $0.0005 | 70% | 0x7e34…eb94 | 139d ago | 0x02143e…046700 |
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 0xaf85…0c04 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xaf85eb74d6e56be6ed510fe4d46035c228a60c04
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: 0xaf85…0c04 curl -s 'https://api.roundhouseai.io/v0/agents/0xaf85eb74d6e56be6ed510fe4d46035c228a60c04' curl -s 'https://api.roundhouseai.io/v0/entities/0xaf85eb74d6e56be6ed510fe4d46035c228a60c04/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.