0xc3d2…e943
Paid $0.83 of the $3059.84M Roundhouse has indexed across 1,397,384 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (20)
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.83 | 19 | 4 |
$0.20 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 4 the amount paid narrows the list to the ones listed at that price.
- 0x967f…880c · last paid 99d ago$0.634 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/tagsPrice match$0.25 listed
- 0x49d7…f5a9 · last paid 79d ago$0.1313 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x74ef…981c · last paid 98d ago$0.061 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xc82b…f6df · last paid 84d 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.
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 | |
|---|---|---|---|---|---|
| 0x74ef…981c | $0.06 | $1.00 | 2 | 98d ago | Graph |
| Shovels API | $0.63 | $0.00 | 4 | 99d ago | Graph |
| 0x49d7…f5a9 | $0.13 | $0.00 | 13 | 79d ago | Graph |
| 0xc82b…f6df | $0.01 | $0.00 | 1 | 84d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
58% of observed volume is with a single counterparty, in all 20 observed settlements.
Recent activity
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 0xc3d2…e943 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xc3d28f729be1f25103d32fe513a07e3f5864e943
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: 0xc3d2…e943 curl -s 'https://api.roundhouseai.io/v0/agents/0xc3d28f729be1f25103d32fe513a07e3f5864e943' curl -s 'https://api.roundhouseai.io/v0/entities/0xc3d28f729be1f25103d32fe513a07e3f5864e943/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.