0xf65c…5984
Paid $1.07 of the $3060.46M Roundhouse has indexed across 1,397,861 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (7)
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.07 | 7 | 2 |
$1.07 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.
- 0x5c4e…a0fd · last paid 11d ago$0.621 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x4020…0003 · last paid 11d ago$0.456 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 | |
|---|---|---|---|---|---|
| 0x5c4e…a0fd | $0.62 | $0.00 | 1 | 11d ago | Graph |
| 0x4020…0003 | $0.45 | $0.00 | 6 | 11d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
58% of observed volume is with a single counterparty, in all 7 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xf65c…59840x5c4e…a0fd | Base | $0.62 | 70% | 0x5c4e…a0fd | 11d ago | 0x9f8384…00514f |
| 0xf65c…59840x4020…0003 | Base | $0.05 | 70% | 0xb3ed…641b | 11d ago | 0x6a9212…4e2f61 |
| 0xf65c…59840x4020…0003 | Base | $0.05 | 70% | 0xb3ed…641b | 11d ago | 0x4fa578…d0eb5b |
| 0xf65c…59840x4020…0003 | Base | $0.05 | 70% | 0xb3ed…641b | 11d ago | 0xdf7c37…3ddcac |
| 0xf65c…59840x4020…0003 | Base | $0.10 | 70% | 0xb3ed…641b | 11d ago | 0x427a51…172976 |
| 0xf65c…59840x4020…0003 | Base | $0.10 | 70% | 0xb3ed…641b | 11d ago | 0x3931f9…b6cf20 |
| 0xf65c…59840x4020…0003 | Base | $0.10 | 70% | 0xb3ed…641b | 11d ago | 0x79d54f…bae6f5 |
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 0xf65c…5984 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf65ccb4ca9c7f6bc2e3763617287059b50235984
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: 0xf65c…5984 curl -s 'https://api.roundhouseai.io/v0/agents/0xf65ccb4ca9c7f6bc2e3763617287059b50235984' curl -s 'https://api.roundhouseai.io/v0/entities/0xf65ccb4ca9c7f6bc2e3763617287059b50235984/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.