0x969a…f290
Paid $1.53 of the $846.56M Roundhouse has indexed across 1,329,848 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (54)
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 | 100% | $1.53 | 54 | 2 |
$1.00 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.
- 0x0fe8…9393 · last paid 349d ago$1.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x48eb…9a3a · last paid 365d ago$0.5353 calls
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 | |
|---|---|---|---|---|---|
| 0x0fe8…9393 | $1.00 | $0.00 | 1 | 349d ago | Graph |
| 0x48eb…9a3a | $0.53 | $0.00 | 53 | 365d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
65% of observed volume is with a single counterparty, in all 54 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 0x969a…f290 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x969a73c4b54aae7b077f51f6ee07f3380f2af290
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: 0x969a…f290 curl -s 'https://api.roundhouseai.io/v0/agents/0x969a73c4b54aae7b077f51f6ee07f3380f2af290' curl -s 'https://api.roundhouseai.io/v0/entities/0x969a73c4b54aae7b077f51f6ee07f3380f2af290/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.