0xc637…ae45
Paid $0.87 of the $261.61M Roundhouse has indexed across 717,689 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (50)
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 |
|---|---|---|---|---|
| Web & Content | 54% | $0.47 | 47 | 1 |
| Not in any catalogue | 46% | $0.40 | 3 | 2 |
$0.001 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 3 the amount paid narrows the list to the ones listed at that price.
- 0xca12…cd0c · last paid 322d ago$0.4747 calls
▸5 catalogued endpoints, none priced at an amount this agent paid
- /news-by-keyword$0.05 listed
- /news-ticker-summary$0.03 listed
- /pm-scorings$0.10 listed
- /newsNews search$0.03 listed
- /recaps$0.10 listed
- 0xf338…97ea · last paid 323d ago$0.402 calls
▸2 of 3 catalogued endpoints list a price this agent paid
- /api/video/create-sora2Price match$0.20 listed
- /api/video/createPrice match$0.20 listed
- /api/image/create$0.02 listed
- 0x159a…0748 · last paid 324d ago$0.0011 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 | |
|---|---|---|---|---|---|
| 0xca12…cd0c | $0.47 | $0.00 | 47 | 322d ago | Graph |
| 0xf338…97ea | $0.40 | $0.00 | 2 | 323d ago | Graph |
| 0x159a…0748 | $0.001 | $0.00 | 1 | 324d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
54% of observed volume is with a single counterparty, in all 50 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 0xc637…ae45 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xc637a3bc9676c4eda4e48ab1c64ee7bb87f8ae45
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: 0xc637…ae45 curl -s 'https://api.roundhouseai.io/v0/agents/0xc637a3bc9676c4eda4e48ab1c64ee7bb87f8ae45' curl -s 'https://api.roundhouseai.io/v0/entities/0xc637a3bc9676c4eda4e48ab1c64ee7bb87f8ae45/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.