0xf891…eb8f
Paid $0.11 of the $843.78M Roundhouse has indexed across 1,323,817 wallets — less than 0.0001% 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% | $0.11 | 1 | 1 |
$0.11 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.
- 0x3577…ca8d · last paid 20d ago$0.111 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 | |
|---|---|---|---|---|---|
| 0x3577…ca8d | $0.11 | $0.00 | 1 | 20d 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 $0.11 of $0.11 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xf891…eb8f0x3577…ca8d | Base | $0.11 | 70% | 0x642b…6c75 | 20d ago | 0x21f85f…7eab21 |
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 0xf891…eb8f has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf891e3df937a23e36ee5c833e0bec3e1e05feb8f
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: 0xf891…eb8f curl -s 'https://api.roundhouseai.io/v0/agents/0xf891e3df937a23e36ee5c833e0bec3e1e05feb8f' curl -s 'https://api.roundhouseai.io/v0/entities/0xf891e3df937a23e36ee5c833e0bec3e1e05feb8f/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.