0x1cf1…e42c
Paid $0.66 of the $846.65M Roundhouse has indexed across 1,329,967 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (7)
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.66 | 7 | 2 |
$0.66 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.
- 0x5c4e…a0fd · last paid 18d ago$0.381 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x4020…0003 · last paid 18d ago$0.286 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 | |
|---|---|---|---|---|---|
| 0x5c4e…a0fd | $0.38 | $0.00 | 1 | 18d ago | Graph |
| 0x4020…0003 | $0.28 | $0.00 | 6 | 18d 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 7 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x1cf1…e42c0x5c4e…a0fd | Base | $0.38 | 70% | 0x5c4e…a0fd | 18d ago | 0xe2d167…170013 |
| 0x1cf1…e42c0x4020…0003 | Base | $0.04 | 70% | 0xb3ed…641b | 18d ago | 0xc8abb9…14731a |
| 0x1cf1…e42c0x4020…0003 | Base | $0.04 | 70% | 0xb3ed…641b | 18d ago | 0x5abea2…6fa196 |
| 0x1cf1…e42c0x4020…0003 | Base | $0.06 | 70% | 0xb3ed…641b | 18d ago | 0x8f761f…335bd9 |
| 0x1cf1…e42c0x4020…0003 | Base | $0.04 | 70% | 0xb3ed…641b | 18d ago | 0x03b720…94f6d3 |
| 0x1cf1…e42c0x4020…0003 | Base | $0.06 | 70% | 0xb3ed…641b | 18d ago | 0x0b269c…c6de85 |
| 0x1cf1…e42c0x4020…0003 | Base | $0.04 | 70% | 0xb3ed…641b | 18d ago | 0xf00fd6…4e4be8 |
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 0x1cf1…e42c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1cf1837281995ac0a3f761d59aaf66f07924e42c
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: 0x1cf1…e42c curl -s 'https://api.roundhouseai.io/v0/agents/0x1cf1837281995ac0a3f761d59aaf66f07924e42c' curl -s 'https://api.roundhouseai.io/v0/entities/0x1cf1837281995ac0a3f761d59aaf66f07924e42c/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.