0xfebf…d32d
Paid $0.30 of the $259.14M Roundhouse has indexed across 714,236 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (28)
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 |
|---|---|---|---|---|
| Reference Data | 99% | $0.30 | 26 | 1 |
| Not in any catalogue | <1% | $0.002 | 1 | 1 |
$0.002 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; for 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x2880…4e5e · last paid 49d ago$0.3026 calls
▸135 of 200 catalogued endpoints list a price this agent paid
- /feiertagePrice match$0.001 listed
- /demo/paid-samplePrice match$0.001 listed
- /product/comparePrice match$0.01 listed
- /predict/negative-pricePrice match$0.001 listed
- /stackPrice match$0.003 listed
- /v1/pathogen-r0Price match$0.003 listed
- /v1/currency/normalizePrice match$0.001 listed
- /v1/anti-cheat-scan$0.004 listed
192 further catalogued endpoints not listed.
- 0x3562…4620 · last paid 52d ago$0.0021 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Funds flow over time
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x3562…4620 | $0.002 | $0.30 | 2 | 52d ago | Graph |
| 0x2880…4e5e | $0.30 | $0.00 | 26 | 49d 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 28 observed settlements.
Recent activity
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 0xfebf…d32d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xfebf0139ea549ef35b20c704d2124f52bb2fd32d
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: 0xfebf…d32d curl -s 'https://api.roundhouseai.io/v0/agents/0xfebf0139ea549ef35b20c704d2124f52bb2fd32d' curl -s 'https://api.roundhouseai.io/v0/entities/0xfebf0139ea549ef35b20c704d2124f52bb2fd32d/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.