0xf88c…2146
Paid $0.02 of the $261.16M Roundhouse has indexed across 717,066 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.02 | 2 | 2 |
$0.02 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.
- 0x2a46…a3a1 · last paid 23h ago$0.021 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xabf4…a9d0 · last paid 3d ago$0.0041 call
▸12 of 200 catalogued endpoints list a price this agent paid
- /api/perp-fundingPerp funding and open interest$0.002 listed
- /api/perp-basis$0.002 listed
- /api/hash$0.001 listed
- /api/ttsText to speech$0.05 listed
- /api/sol-token-safety$0.005 listed
- /api/bestsellers$0.005 listed
- /v1/nano/chat/completionsText completion$0.003 listed
- /api/demand-radar$0.005 listed
192 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0x2a46…a3a1 | $0.02 | $0.00 | 1 | 23h ago | Graph |
| 0xabf4…a9d0 | $0.004 | $0.00 | 1 | 3d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
83% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xf88c…21460x2a46…a3a1 | Base | $0.02 | 100% | coinbase | 23h ago | 0xf6d188…9c7080 |
| 0xf88c…21460xabf4…a9d0 | Base | $0.004 | 100% | coinbase | 3d ago | 0x2ddab8…c55e0b |
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 0xf88c…2146 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf88cc35f6847d438963456d39d902877f5432146
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: 0xf88c…2146 curl -s 'https://api.roundhouseai.io/v0/agents/0xf88cc35f6847d438963456d39d902877f5432146' curl -s 'https://api.roundhouseai.io/v0/entities/0xf88cc35f6847d438963456d39d902877f5432146/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.