0xf222…fbd8
Paid $0.12 of the $3126.72M Roundhouse has indexed across 1,422,890 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (20)
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 | 74% | $0.09 | 17 | 1 |
| Crypto Markets | 17% | $0.02 | 2 | 1 |
| Web & Content | 9% | $0.01 | 1 | 1 |
$0.09 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 2 of 3 the amount paid narrows the list to the ones listed at that price.
- 0xc3b6…c06b · last paid 6h ago$0.0917 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x13e0…f707 · last paid 86d ago$0.022 calls
▸36 of 65 catalogued endpoints list a price this agent paid
- /api/:namePrice match$0.01 listed
- /api/:name/followersPrice match$0.01 listed
- /api/:name/followers_webPrice match$0.01 listed
- /api/search/tweetsPrice match$0.01 listed
- /api/trendsPrice match$0.01 listed
- /api/:name/affiliatesPrice match$0.01 listed
- /api/tools/get_user_idPrice match$0.01 listed
- /api/lists/:idPrice match$0.01 listed
57 further catalogued endpoints not listed.
- 0x9dba…0df8 · last paid 86d ago$0.011 call
▸20 of 32 catalogued endpoints list a price this agent paid
- /tweets/userPrice match$0.01 listed
- /lists/tweetsPrice match$0.01 listed
- /tweets/searchWeb search$0.006 listed
- /tweets/mentions$0.006 listed
- /users/by/username$0.005 listed
- /tweets/by/id$0.0025 listed
- /users/by/id$0.005 listed
- /tweets/mediaUpload$0.006 listed
24 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| 0xc3b6…c06b | $0.09 | $0.00 | 17 | 6h ago | Graph |
| 0x13e0…f707 | $0.02 | $0.00 | 2 | 86d ago | Graph |
| 0x9dba…0df8 | $0.01 | $0.00 | 1 | 86d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
74% of observed volume is with a single counterparty, in all 20 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 0xf222…fbd8 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf22220d8cdd2178a434c532c521a8aadd92efbd8
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: 0xf222…fbd8 curl -s 'https://api.roundhouseai.io/v0/agents/0xf22220d8cdd2178a434c532c521a8aadd92efbd8' curl -s 'https://api.roundhouseai.io/v0/entities/0xf22220d8cdd2178a434c532c521a8aadd92efbd8/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.