0x3e19…e240
Paid $279.32 of the $3061.41M Roundhouse has indexed across 1,398,817 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1000)
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 |
|---|---|---|---|---|
| Crypto Markets | 53% | $99.80 | 998 | 1 |
| Not in any catalogue | 47% | $86.92 | 2 | 1 |
$86.92 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.
- 0xdb5c…10fd · last paid 2m ago$99.80998 calls
▸40 of 41 catalogued endpoints list a price this agent paid
- /api/v1/macro/:var1Price match$0.10 listed
- /api/v1/analytics/:var1Price match$0.10 listed
- /api/v1/futures/snapshotPrice match$0.10 listed
- /api/v1/perpetuals/volumePrice match$0.10 listed
- /api/v1/perpetuals/liquidationsPrice match$0.10 listed
- /api/v1/options/ticker-historyPrice match$0.10 listed
- /api/v1/perpetuals/reference-pricePrice match$0.10 listed
- /api/v1/perpetuals/level1Price match$0.10 listed
33 further catalogued endpoints not listed.
- 0x47c5…4fc3 · last paid 10d ago$86.922 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Folded from this wallet's 1,000 most recent settlements of 1,926 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.
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 | |
|---|---|---|---|---|---|
| 0xdb5c…10fd | $99.80 | $0.00 | 998 | 2m ago | Graph |
| 0x47c5…4fc3 | $86.92 | $0.00 | 2 | 10d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
53% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).
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 0x3e19…e240 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x3e191ed75244c6393e41af9717ac3e957bc0e240
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: 0x3e19…e240 curl -s 'https://api.roundhouseai.io/v0/agents/0x3e191ed75244c6393e41af9717ac3e957bc0e240' curl -s 'https://api.roundhouseai.io/v0/entities/0x3e191ed75244c6393e41af9717ac3e957bc0e240/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.