0x9e84…719d
Paid $0.54 of the $3061.41M Roundhouse has indexed across 1,398,667 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (527)
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 | 97% | $0.53 | 525 | 2 |
| Crypto Markets | 3% | $0.02 | 2 | 1 |
$0.53 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 3 the amount paid narrows the list to the ones listed at that price.
- 0xb98f…fa91 · last paid 2d ago$0.34336 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x8aee…01a0 · last paid 82d ago$0.19189 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xff0e…16a5 · last paid 26d ago$0.022 calls
▸3 of 5 catalogued endpoints list a price this agent paid
- /v1/eventsPrice match$0.005 listed
- /v1/market-statePrice matchPerp funding and open interest$0.01 listed
- /v1/bsc-alertsPrice match$0.005 listed
- /v1/bsc-pool-autopsy$0.02 listed
- /v1/bsc-verdict$0.02 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 | |
|---|---|---|---|---|---|
| 0xb98f…fa91 | $0.34 | $0.00 | 336 | 2d ago | Graph |
| 0x8aee…01a0 | $0.19 | $0.00 | 189 | 82d ago | Graph |
| 0xff0e…16a5 | $0.02 | $0.00 | 2 | 26d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
62% of observed volume is with a single counterparty, in all 527 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 0x9e84…719d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9e8415109a718de3a4653e4da37c5906df7c719d
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: 0x9e84…719d curl -s 'https://api.roundhouseai.io/v0/agents/0x9e8415109a718de3a4653e4da37c5906df7c719d' curl -s 'https://api.roundhouseai.io/v0/entities/0x9e8415109a718de3a4653e4da37c5906df7c719d/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.