0xc2f4…767f
Paid $0.02 of the $259.71M Roundhouse has indexed across 715,210 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.01 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.
- 0x3e9f…ca7b · last paid 305d ago$0.011 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x8d8f…bb9b · last paid 332d ago$0.011 call
▸3 of 5 catalogued endpoints list a price this agent paid
- /api/x402/credit-drop/xsPrice match$0.01 listed
- /credit-drop/xsPrice match$0.01 listed
- /api/x402/credit-drop/xsPrice match$0.01 listed
- /credit-drop/lg$10.00 listed
- /credit-drop$1.00 listed
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 | |
|---|---|---|---|---|---|
| 0x3e9f…ca7b | $0.01 | $0.00 | 1 | 305d ago | Graph |
| 0x8d8f…bb9b | $0.01 | $0.00 | 1 | 332d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
50% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xc2f4…767f0x3e9f…ca7b | Base | $0.01 | 100% | coinbase | 305d ago | 0xacdc30…8e160f |
| 0xc2f4…767f0x8d8f…bb9b | Base | $0.01 | 100% | coinbase | 332d ago | 0xfcfaeb…ad6c2b |
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 0xc2f4…767f has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xc2f41e28fa93314aa2ec4f5f1d05bdb52802767f
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: 0xc2f4…767f curl -s 'https://api.roundhouseai.io/v0/agents/0xc2f41e28fa93314aa2ec4f5f1d05bdb52802767f' curl -s 'https://api.roundhouseai.io/v0/entities/0xc2f41e28fa93314aa2ec4f5f1d05bdb52802767f/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.