0xee1e…6f3d
Paid $0.60 of the $3064.22M Roundhouse has indexed across 1,399,289 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (4)
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.60 | 1 | 1 |
$0.60 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.
- 0x8e0a…130f · last paid 111d ago$0.601 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 | |
|---|---|---|---|---|---|
| 0x8e0a…130f | $0.60 | $0.00 | 1 | 111d ago | Graph |
| 0xf07f…60e3 | $0.00 | $0.20 | 1 | 111d ago | Graph |
| 0xf2d2…3208 | $0.00 | $0.20 | 1 | 111d ago | Graph |
| 0xd1ae…8133 | $0.00 | $0.20 | 1 | 111d 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 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xee1e…6f3d0x8e0a…130f | Base | $0.60 | 100% | fluxa | 111d ago | 0x1ed393…c2b706 |
| 0xf07f…60e30xee1e…6f3d | Base | $0.20 | 100% | fluxa | 111d ago | 0xb629fc…315c2c |
| 0xf2d2…32080xee1e…6f3d | Base | $0.20 | 100% | fluxa | 111d ago | 0xc4221a…f826e4 |
| 0xd1ae…81330xee1e…6f3d | Base | $0.20 | 100% | fluxa | 111d ago | 0x3147e2…b3a41a |
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 0xee1e…6f3d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xee1e757276e26866fbaf1f18725ab25d121b6f3d
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: 0xee1e…6f3d curl -s 'https://api.roundhouseai.io/v0/agents/0xee1e757276e26866fbaf1f18725ab25d121b6f3d' curl -s 'https://api.roundhouseai.io/v0/entities/0xee1e757276e26866fbaf1f18725ab25d121b6f3d/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.