0xcf2b3c8aecca567dcbf4d9f8a03e4a41144ec2a9
Paid $22.00 of the $259.71M Roundhouse has indexed across 715,210 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (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% | $22.00 | 2 | 2 |
$22.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.
- 0x257e…2d21 · last paid 115d ago$11.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xedfe…6675 · last paid 115d ago$11.001 call
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 | |
|---|---|---|---|---|---|
| 0x257e…2d21 | $11.00 | $0.00 | 1 | 115d ago | Graph |
| v3.linkdrop.eth | $11.00 | $0.00 | 1 | 115d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
50% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xcf2b…c2a90x257e…2d21 | Base | $11.00 | 100% | 0x4029…e306 | 115d ago | 0x2b59a4…c385d0 |
| 0xcf2b…c2a9v3.linkdrop.eth | Base | $11.00 | 100% | 0x5f34…bdc0 | 115d ago | 0xa5f655…950b63 |
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 0xcf2b3c8aecca567dcbf4d9f8a03e4a41144ec2a9 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xcf2b3c8aecca567dcbf4d9f8a03e4a41144ec2a9
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: 0xcf2b3c8aecca567dcbf4d9f8a03e4a41144ec2a9 curl -s 'https://api.roundhouseai.io/v0/agents/0xcf2b3c8aecca567dcbf4d9f8a03e4a41144ec2a9' curl -s 'https://api.roundhouseai.io/v0/entities/0xcf2b3c8aecca567dcbf4d9f8a03e4a41144ec2a9/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.