0x9f7b…784f
Paid $1.70 of the $846.56M Roundhouse has indexed across 1,329,848 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (5)
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% | $1.70 | 5 | 1 |
$1.70 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xef43…6c7f · last paid 330d ago$1.705 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 | |
|---|---|---|---|---|---|
| 0xef43…6c7f | $1.70 | $0.00 | 5 | 330d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 5 observed settlements.
Organic volume $1.70 of $1.70 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x9f7b…784f0xef43…6c7f | Base | $0.50 | 100% | virtuals | 330d ago | 0x0d8a0f…32d12f |
| 0x9f7b…784f0xef43…6c7f | Base | $0.50 | 100% | virtuals | 330d ago | 0x0ee334…bed0e7 |
| 0x9f7b…784f0xef43…6c7f | Base | $0.10 | 100% | virtuals | 330d ago | 0x58aaa0…35f263 |
| 0x9f7b…784f0xef43…6c7f | Base | $0.50 | 100% | virtuals | 330d ago | 0x46b748…86aa78 |
| 0x9f7b…784f0xef43…6c7f | Base | $0.10 | 100% | virtuals | 330d ago | 0xf7859a…1276b0 |
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 0x9f7b…784f has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9f7b38d722ba7c868630481484c6c0d472ba784f
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: 0x9f7b…784f curl -s 'https://api.roundhouseai.io/v0/agents/0x9f7b38d722ba7c868630481484c6c0d472ba784f' curl -s 'https://api.roundhouseai.io/v0/entities/0x9f7b38d722ba7c868630481484c6c0d472ba784f/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.