0xc4c2…bcdb
Paid $0.10 of the $259.81M Roundhouse has indexed across 715,279 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.10 | 2 | 2 |
$0.0003 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.
- 0xde9e…3531 · last paid 333d ago$0.101 call
▸3 of 3 catalogued endpoints list a price this agent paid
- /api/mint_payaiPrice match$0.10 listed
- /api/mint_payaiPrice match$0.10 listed
- /mintPrice match$0.10 listed
- 0x13c1…c5e0 · last paid 333d ago$0.00031 call
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 | |
|---|---|---|---|---|---|
| 0xde9e…3531 | $0.10 | $0.00 | 1 | 333d ago | Graph |
| nexus.thirdweb.eth | $0.0003 | $0.00 | 1 | 333d 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, in all 2 observed settlements.
Organic volume $0.10 of $0.10 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xc4c2…bcdb0xde9e…3531 | Base | $0.10 | 100% | payAI | 333d ago | 0x3fcd86…8c1f07 |
| 0xc4c2…bcdbnexus.thirdweb.eth | Base | $0.0003 | 100% | thirdweb | 333d ago | 0xc23f19…bb25e1 |
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 0xc4c2…bcdb has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xc4c29ccedb137d4e942a502c8f6998525712bcdb
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: 0xc4c2…bcdb curl -s 'https://api.roundhouseai.io/v0/agents/0xc4c29ccedb137d4e942a502c8f6998525712bcdb' curl -s 'https://api.roundhouseai.io/v0/entities/0xc4c29ccedb137d4e942a502c8f6998525712bcdb/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.