0xf50b…1351
Paid $2.75 of the $260.74M Roundhouse has indexed across 716,479 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (170)
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 | 58% | $1.59 | 112 | 1 |
| Web & Content | 42% | $1.16 | 58 | 1 |
$1.59 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.
- 0x1e54…0353 · last paid 237d ago$1.59112 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x325b…d430 · last paid 225d ago$1.1658 calls
▸6 of 68 catalogued endpoints list a price this agent paid
- /api/exa/searchWeb 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/fullenrich/people-searchPeople search$0.15 listed
- /api/whitepages/person-search$0.22 listed
- /api/pdl/people-enrichPeople search$0.28 listed
- /api/clado/contacts-enrichPeople search$0.20 listed
60 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 | |
|---|---|---|---|---|---|
| 0x1e54…0353 | $1.59 | $0.00 | 112 | 237d ago | Graph |
| 0x325b…d430 | $1.16 | $0.00 | 58 | 225d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
58% of observed volume is with a single counterparty, in all 170 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 0xf50b…1351 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf50ba48d47dc8efe42a21b662b2e73121fa11351
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: 0xf50b…1351 curl -s 'https://api.roundhouseai.io/v0/agents/0xf50ba48d47dc8efe42a21b662b2e73121fa11351' curl -s 'https://api.roundhouseai.io/v0/entities/0xf50ba48d47dc8efe42a21b662b2e73121fa11351/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.