0xf78bb431901219ef5f866e1b64d0045a921f0d68
Paid $0.38 of the $3064.22M Roundhouse has indexed across 1,399,289 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (50)
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 |
|---|---|---|---|---|
| Web & Content | 75% | $0.29 | 28 | 1 |
| Not in any catalogue | 25% | $0.09 | 22 | 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 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x325b…d430 · last paid 164d ago$0.2928 calls
▸19 of 70 catalogued endpoints list a price this agent paid
- /api/exa/searchPrice matchWeb search$0.01 listed
- /api/exa/contents$0.002 listed
- /api/firecrawl/searchWeb search$0.03 listed
- /api/apollo/people-enrichPeople search$0.05 listed
- /api/pdl/people-enrichPeople search$0.28 listed
- /api/clado/contacts-enrichPeople search$0.20 listed
- /api/fullenrich/people-searchPeople search$0.15 listed
- /api/reddit/searchWeb search$0.02 listed
62 further catalogued endpoints not listed.
- 0x48f8…d503 · last paid 155d ago$0.0922 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
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 | |
|---|---|---|---|---|---|
| 0x325b…d430 | $0.29 | $0.00 | 28 | 164d ago | Graph |
| 0x48f8…d503 | $0.09 | $0.00 | 22 | 155d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
75% of observed volume is with a single counterparty, in all 50 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 0xf78bb431901219ef5f866e1b64d0045a921f0d68 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf78bb431901219ef5f866e1b64d0045a921f0d68
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: 0xf78bb431901219ef5f866e1b64d0045a921f0d68 curl -s 'https://api.roundhouseai.io/v0/agents/0xf78bb431901219ef5f866e1b64d0045a921f0d68' curl -s 'https://api.roundhouseai.io/v0/entities/0xf78bb431901219ef5f866e1b64d0045a921f0d68/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.