0xf9e3…6e53
Paid $2.48 of the $3061.41M Roundhouse has indexed across 1,398,256 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (138)
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 |
|---|---|---|---|---|
| Risk & Compliance | 81% | $2.02 | 137 | 1 |
| Not in any catalogue | 19% | $0.47 | 1 | 1 |
$0.47 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.
- 0x94f7…4873 · last paid 45d ago$2.02137 calls
▸39 of 119 catalogued endpoints list a price this agent paid
- /x402/v1/value/trx-usdPrice match$0.001 listed
- /v1/x402/x402/resource-comparePrice match$0.01 listed
- /x402/v1/policy/merchant-check$0.05 listed
- /v1/x402/agent/mcp-server-risk-check$0.02 listed
- /v1/x402/quicknode/wallet-execution-readiness$0.05 listed
- /v1/x402/agent/capability-security-preflight$0.10 listed
- /v1/x402/agent/buyer-identity-preflight$0.05 listed
- /v1/x402/software/pypi-package-preflight$0.005011 listed
111 further catalogued endpoints not listed.
- 0x5bf9…06d3 · last paid 45d ago$0.471 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
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 | |
|---|---|---|---|---|---|
| 0x94f7…4873 | $2.02 | $0.00 | 137 | 45d ago | Graph |
| 0x5bf9…06d3 | $0.47 | $0.00 | 1 | 45d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
81% of observed volume is with a single counterparty, in all 138 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 0xf9e3…6e53 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf9e3917727b0c22a8d684b01fe07867188eb6e53
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: 0xf9e3…6e53 curl -s 'https://api.roundhouseai.io/v0/agents/0xf9e3917727b0c22a8d684b01fe07867188eb6e53' curl -s 'https://api.roundhouseai.io/v0/entities/0xf9e3917727b0c22a8d684b01fe07867188eb6e53/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.