0xcfaa…332c
Paid $36.75 of the $3216.24M Roundhouse has indexed across 1,445,098 wallets — less than 0.0001% of it.
Whole-history totals from the index rollup, which can be up to 30 minutes behind.
Chains (from the recent scan): Base (1) · Ethereum (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% | $36.75 | 3 | 2 |
$36.75 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.
- 0x5c7b…35c5 · last paid 41d ago$21.002 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x47c5…4fc3 · last paid 2d ago$15.751 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
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 | |
|---|---|---|---|---|---|
| 0x5c7b…35c5 | $21.00 | $0.00 | 2 | 41d ago | Graph |
| 0x47c5…4fc3 | $15.75 | $0.00 | 1 | 2d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
57% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xcfaa…332c0x47c5…4fc3 | Base | $15.75 | 70% | 0xf867…7e9b | 2d ago | 0xe4a0bc…e37646 |
| 0xcfaa…332c0x5c7b…35c5 | Ethereum | $10.50 | 70% | 0xd016…b67a | 41d ago | 0x0ef026…42185d |
| 0xcfaa…332c0x5c7b…35c5 | Ethereum | $10.50 | 70% | 0xc10a…ae5d | 45d ago | 0xda026f…fa84e7 |
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 0xcfaa…332c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xcfaa6c56ad17bee477548a1db9dfb5f6f97d332c
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: 0xcfaa…332c curl -s 'https://api.roundhouseai.io/v0/agents/0xcfaa6c56ad17bee477548a1db9dfb5f6f97d332c' curl -s 'https://api.roundhouseai.io/v0/entities/0xcfaa6c56ad17bee477548a1db9dfb5f6f97d332c/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.