0xd02dc4aabc3109e8e2e1a8107d35135c36fc86de
Paid $2,123.90 of the $260.92M Roundhouse has indexed across 716,778 wallets — 0.0008% 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% | $2,123.90 | 2 | 2 |
$2,123.90 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.
- 0xbf80…e00b · last paid 121d ago$1,062.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x1167…6752 · last paid 121d ago$1,061.901 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 | |
|---|---|---|---|---|---|
| 0xbf80…e00b | $1,062.00 | $0.00 | 1 | 121d ago | Graph |
| 0x1167…6752 | $1,061.90 | $0.00 | 1 | 121d 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 |
|---|---|---|---|---|---|---|
| 0xd02d…86de0xbf80…e00b | Base | $1,062.00 | 100% | 0xa923…c9ac | 121d ago | 0xfeccc3…4128c6 |
| 0xd02d…86de0x1167…6752 | Base | $1,061.90 | 100% | 0xa923…c9ac | 121d ago | 0xeec2f6…d6a984 |
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 0xd02dc4aabc3109e8e2e1a8107d35135c36fc86de has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xd02dc4aabc3109e8e2e1a8107d35135c36fc86de
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: 0xd02dc4aabc3109e8e2e1a8107d35135c36fc86de curl -s 'https://api.roundhouseai.io/v0/agents/0xd02dc4aabc3109e8e2e1a8107d35135c36fc86de' curl -s 'https://api.roundhouseai.io/v0/entities/0xd02dc4aabc3109e8e2e1a8107d35135c36fc86de/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.