0x6422…2ea1
Paid $50.00 of the $3059.45M Roundhouse has indexed across 1,397,282 wallets — less than 0.0001% of it.
Chains (from the recent scan): Ethereum (3)
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% | $50.00 | 3 | 2 |
$32.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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xa4b6…e950 · last paid 114d ago$32.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x5138…c14d · last paid 135d ago$18.002 calls
▸1 catalogued endpoints, none priced at an amount this agent paid
- /user-management-api/x402/api-keys$5.00 listed
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 | |
|---|---|---|---|---|---|
| 0xa4b6…e950 | $32.00 | $0.00 | 1 | 114d ago | Graph |
| 0x5138…c14d | $18.00 | $0.00 | 2 | 135d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
64% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x6422…2ea10xa4b6…e950 | Ethereum | $32.00 | 70% | 0x027d…f07d | 114d ago | 0x4eba4a…e7cf55 |
| 0x6422…2ea10x5138…c14d | Ethereum | $9.00 | 70% | 0x027d…f07d | 135d ago | 0x7dac35…69f3d1 |
| 0x6422…2ea10x5138…c14d | Ethereum | $9.00 | 70% | 0x027d…f07d | 164d ago | 0x10353a…47215b |
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 0x6422…2ea1 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x64221a7f1f3de33d6d84ef61557deb637c742ea1
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: 0x6422…2ea1 curl -s 'https://api.roundhouseai.io/v0/agents/0x64221a7f1f3de33d6d84ef61557deb637c742ea1' curl -s 'https://api.roundhouseai.io/v0/entities/0x64221a7f1f3de33d6d84ef61557deb637c742ea1/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.