0xf26a…15a6
Paid $10.70 of the $3149.47M Roundhouse has indexed across 1,425,637 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (204)
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 | 73% | $7.83 | 11 | 1 |
| AI & Media | 27% | $2.87 | 193 | 1 |
Every merchant paid publishes at least one catalogued endpoint.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x99ee…e039 · last paid 144d ago$7.8311 calls
▸5 of 5 catalogued endpoints list a price this agent paid
- /h3retik/api/x402/sessions/probePrice match$0.60 listed
- /h3retik/api/x402/sessions/microPrice match$0.19 listed
- /h3retik/api/x402/sessions/opsPrice match$2.70 listed
- /api/v1/skynet/investigatePrice match$0.25 listed
- /h3retik/api/x402/sessionsPrice match$0.19 listed
- 0xe903…1abf · last paid 9d ago$2.87193 calls
▸168 of 200 catalogued endpoints list a price this agent paid
- /api/v1/chat/completionsPrice matchText completion$0.002 listed
- /api/v1/exa/contentsPrice match$0.003 listed
- /api/v1/exa/answerText completion$0.01 listed
- /api/v1/messages$0.01 listed
- /api/v1/exa/searchWeb search$0.01 listed
- /api/v1/images/generations$0.04 listed
- /api/v1/images/image2image$0.02 listed
- /api/v1/videos/generations$0.40 listed
192 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| H3RETIK Cloud | $7.83 | $0.00 | 11 | 144d ago | Graph |
| 0xe903…1abf | $2.87 | $0.00 | 193 | 9d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
73% of observed volume is with a single counterparty, in all 204 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 0xf26a…15a6 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf26a8e70ac16626400556bd21c1de5ef46e415a6
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: 0xf26a…15a6 curl -s 'https://api.roundhouseai.io/v0/agents/0xf26a8e70ac16626400556bd21c1de5ef46e415a6' curl -s 'https://api.roundhouseai.io/v0/entities/0xf26a8e70ac16626400556bd21c1de5ef46e415a6/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.