0xf587…04f4
Paid $5.67 of the $3063.39M Roundhouse has indexed across 1,398,970 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (219)
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 | 71% | $4.00 | 88 | 2 |
| Web & Content | 29% | $1.67 | 131 | 1 |
$3.74 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.
- 0x9eec…9b72 · last paid 129d ago$3.7475 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x6d6e…9192 · last paid 125d ago$1.67131 calls
▸2 of 3 catalogued endpoints list a price this agent paid
- /searchPrice matchWeb search$0.007 listed
- /pay/agent_exa_aiPrice match$0.007 listed
- /contents$0.001 listed
- 0xdd25…2ec0 · last paid 132d ago$0.2613 calls
▸54 of 187 catalogued endpoints list a price this agent paid
- /api/seats-aero/searchPrice match$0.02 listed
- /api/google-flights/searchPrice match$0.02 listed
- /api/seats-aero/availability$0.04 listed
- /api/hotels/search$0.03 listed
- /api/flights/search$0.05 listed
- /api/reference/locations$0.0054 listed
- /api/hotels/list$0.03 listed
- /api/flights/availability$0.03 listed
179 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 | |
|---|---|---|---|---|---|
| 0x9eec…9b72 | $3.74 | $0.00 | 75 | 129d ago | Graph |
| 0x6d6e…9192 | $1.67 | $0.00 | 131 | 125d ago | Graph |
| 0xdd25…2ec0 | $0.26 | $0.00 | 13 | 132d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
66% of observed volume is with a single counterparty, in all 219 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 0xf587…04f4 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf5876a8bfad131cae4b047478222b2ff992604f4
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: 0xf587…04f4 curl -s 'https://api.roundhouseai.io/v0/agents/0xf5876a8bfad131cae4b047478222b2ff992604f4' curl -s 'https://api.roundhouseai.io/v0/entities/0xf5876a8bfad131cae4b047478222b2ff992604f4/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.