0xcac3…10bc
Paid $50,000.00 of the $3054.69M Roundhouse has indexed across 1,395,510 wallets — 0.0016% of it.
Whole-history totals from the index rollup, which can be up to 30 minutes behind.
Chains (from the recent scan): 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% | $50,000.00 | 2 | 1 |
$50,000.00 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.
- 0x3b4d…5ca7 · last paid 2d ago$50,000.002 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 | |
|---|---|---|---|---|---|
| 0x3b4d…5ca7 | $50,000.00 | $0.00 | 2 | 2d 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; all observed volume is with one counterparty, in all 2 observed settlements.
Organic volume $50,000.00 of $50,000.00 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xcac3…10bc0x3b4d…5ca7 | Ethereum | $49,999.00 | 70% | 0xb381…ae08 | 2d ago | 0x07300d…63d10e |
| 0xcac3…10bc0x3b4d…5ca7 | Ethereum | $1.00 | 70% | 0xb381…ae08 | 2d ago | 0xdd459f…ee68c4 |
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 0xcac3…10bc has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xcac34f69e47b7652f96dee5b4c75c67e7af910bc
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: 0xcac3…10bc curl -s 'https://api.roundhouseai.io/v0/agents/0xcac34f69e47b7652f96dee5b4c75c67e7af910bc' curl -s 'https://api.roundhouseai.io/v0/entities/0xcac34f69e47b7652f96dee5b4c75c67e7af910bc/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.