0x5e64…75f5
Paid $0.003827 of the $847.09M Roundhouse has indexed across 1,330,621 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
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 | 74% | $0.002827 | 1 | 1 |
| Crypto Markets | 26% | $0.001 | 1 | 1 |
$0.002827 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.
- 0xa37f…3efb · last paid 21d ago$0.0028271 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x0e84…b808 · last paid 110d ago$0.0011 call
▸33 of 80 catalogued endpoints list a price this agent paid
- /crypto-newsPrice match$0.001 listed
- /meta-intelligencePrice match$0.001 listed
- /filtered-newsPrice match$0.001 listed
- /token-detailsPrice match$0.001 listed
- /pay/agent_ottoai_crypto_newsPrice match$0.001 listed
- /funding-ratesPrice matchPerp funding and open interest$0.001 listed
- /tweet-search$0.005 listed
- /tradfi-data$0.003 listed
72 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 | |
|---|---|---|---|---|---|
| 0xa37f…3efb | $0.002827 | $0.00 | 1 | 21d ago | Graph |
| 0x0e84…b808 | $0.001 | $0.00 | 1 | 110d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
74% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x5e64…75f50xa37f…3efb | Base | $0.002827 | 70% | 0xa37f…3efb | 21d ago | 0x568dca…74de62 |
| 0x5e64…75f50x0e84…b808 | Base | $0.001 | 100% | coinbase | 110d ago | 0x9f2c1d…765095 |
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 0x5e64…75f5 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x5e645329ea23a84d6fb6006376f0b2b5e3b575f5
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: 0x5e64…75f5 curl -s 'https://api.roundhouseai.io/v0/agents/0x5e645329ea23a84d6fb6006376f0b2b5e3b575f5' curl -s 'https://api.roundhouseai.io/v0/entities/0x5e645329ea23a84d6fb6006376f0b2b5e3b575f5/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.