0xc22a…9afb
Paid $3.75 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.
Whole-history totals from the index rollup, which can be up to 30 minutes behind.
Chains (from the recent scan): Base (343)
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% | $3.75 | 343 | 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.
- 0xecb6…ee4d · last paid 45d ago$2.75342 calls
▸8 of 8 catalogued endpoints list a price this agent paid
- /api/execute_swapPrice match$0.02 listed
- /api/get_swap_quotePrice match$0.01 listed
- /api/get_token_pricePrice match$0.002 listed
- /api/get_portfolioPrice match$0.01 listed
- /api/submit_transaction_hashPrice match$0.005 listed
- /api/get_transaction_statusPrice match$0.001 listed
- /api/get_balancesPrice match$0.005 listed
- /api/search_tokenPrice match$0.001 listed
- 0x4cd0…bc31 · last paid 48d 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.
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 | |
|---|---|---|---|---|---|
| 0xecb6…ee4d | $2.75 | $0.00 | 342 | 45d ago | Graph |
| 0x4cd0…bc31 | $1.00 | $0.00 | 1 | 48d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
73% of observed volume is with a single counterparty, in all 343 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 0xc22a…9afb has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xc22a2a3d9a40eea9484be876e17579bcaa159afb
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: 0xc22a…9afb curl -s 'https://api.roundhouseai.io/v0/agents/0xc22a2a3d9a40eea9484be876e17579bcaa159afb' curl -s 'https://api.roundhouseai.io/v0/entities/0xc22a2a3d9a40eea9484be876e17579bcaa159afb/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.