0x98e3…e917
Paid $0.48 of the $846.65M Roundhouse has indexed across 1,329,967 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (15)
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 | 52% | $0.25 | 1 | 1 |
| Web & Content | 48% | $0.23 | 14 | 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 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x07f0…a045 · last paid 226d ago$0.251 call
▸3 catalogued endpoints, none priced at an amount this agent paid
- /api/upload$0.01 listed
- /api/upload$0.01 listed
- /pay/agent_stablestudio_dev$0.01 listed
- 0x325b…d430 · last paid 226d ago$0.2314 calls
▸29 of 68 catalogued endpoints list a price this agent paid
- /api/exa/searchPrice matchWeb search$0.01 listed
- /api/exa/contentsPrice match$0.002 listed
- /api/reddit/searchPrice matchWeb search$0.02 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/fullenrich/people-searchPeople search$0.15 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 | |
|---|---|---|---|---|---|
| 0x07f0…a045 | $0.25 | $0.00 | 1 | 226d ago | Graph |
| 0x325b…d430 | $0.23 | $0.00 | 14 | 226d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
52% of observed volume is with a single counterparty, in all 15 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 0x98e3…e917 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x98e3e6c5f02b9d57a6cca3613c0315e28c10e917
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: 0x98e3…e917 curl -s 'https://api.roundhouseai.io/v0/agents/0x98e3e6c5f02b9d57a6cca3613c0315e28c10e917' curl -s 'https://api.roundhouseai.io/v0/entities/0x98e3e6c5f02b9d57a6cca3613c0315e28c10e917/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.