0x4c40…aafd
Paid $3,624.00 of the $261.24M Roundhouse has indexed across 717,221 wallets — 0.0014% of it.
Chains (from the recent scan): Base (1000)
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% | $1,000.00 | 1,000 | 1 |
Every merchant paid publishes at least one catalogued endpoint.
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.
- 0xd85c…9d46 · last paid 339d ago$1,000.001,000 calls
▸1 catalogued endpoints, none priced at an amount this agent paid
Folded from this wallet's 1,000 most recent settlements of 3,624 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.
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 | |
|---|---|---|---|---|---|
| 0xd85c…9d46 | $1,000.00 | $0.00 | 1,000 | 339d 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 the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).
Organic volume $1,000.00 of $1,000.00 total.
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 0x4c40…aafd has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x4c40707debb1f1b1f1cca904a31a201b296caafd
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: 0x4c40…aafd curl -s 'https://api.roundhouseai.io/v0/agents/0x4c40707debb1f1b1f1cca904a31a201b296caafd' curl -s 'https://api.roundhouseai.io/v0/entities/0x4c40707debb1f1b1f1cca904a31a201b296caafd/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.