0xdbee…a885
Paid $536.18 of the $258.54M Roundhouse has indexed across 713,171 wallets — 0.0002% of it.
Chains (from the recent scan): Base (1)
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% | $536.18 | 1 | 1 |
$536.18 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.
- 0xcf3d…b9fc · last paid 51d ago$536.181 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 | |
|---|---|---|---|---|---|
| 0xcf3d…b9fc | $536.18 | $0.00 | 1 | 51d 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 all 1 observed settlement.
Organic volume $536.18 of $536.18 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xdbee…a8850xcf3d…b9fc | Base | $536.18 | 100% | 0xe528…c028 | 51d ago | 0x631ac0…a319a6 |
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 0xdbee…a885 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xdbee9f717b50ae1c556a6eaa427ce932feb2a885
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: 0xdbee…a885 curl -s 'https://api.roundhouseai.io/v0/agents/0xdbee9f717b50ae1c556a6eaa427ce932feb2a885' curl -s 'https://api.roundhouseai.io/v0/entities/0xdbee9f717b50ae1c556a6eaa427ce932feb2a885/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.