0x6408…6aaa
Paid $386.50 of the $3216.06M Roundhouse has indexed across 1,444,903 wallets — less than 0.0001% of it.
Chains (from the recent scan): Ethereum (2) · Base (2)
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% | $386.50 | 4 | 2 |
$262.50 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.
- 0x5c7b…35c5 · last paid 57d ago$262.502 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x2a83…9453 · last paid 90d ago$124.002 calls
▸1 catalogued endpoints, none priced at an amount this agent paid
- /api/base/paid-content$0.01 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 | |
|---|---|---|---|---|---|
| 0x5c7b…35c5 | $262.50 | $0.00 | 2 | 57d ago | Graph |
| 0x2a83…9453 | $124.00 | $0.00 | 2 | 90d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
68% of observed volume is with a single counterparty, in all 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x6408…6aaa0x5c7b…35c5 | Ethereum | $52.50 | 70% | 0xc10a…ae5d | 57d ago | 0x1bbf45…7e5894 |
| 0x6408…6aaa0x2a83…9453 | Base | $100.00 | 100% | payAI | 90d ago | 0xc83504…545dfc |
| 0x6408…6aaa0x2a83…9453 | Base | $24.00 | 100% | payAI | 90d ago | 0xd924c0…c40cfe |
| 0x6408…6aaa0x5c7b…35c5 | Ethereum | $210.00 | 70% | 0xd016…b67a | 96d ago | 0x6da550…7566ec |
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 0x6408…6aaa has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x64089a8e151eab71466d2c279e07bfc8e27d6aaa
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: 0x6408…6aaa curl -s 'https://api.roundhouseai.io/v0/agents/0x64089a8e151eab71466d2c279e07bfc8e27d6aaa' curl -s 'https://api.roundhouseai.io/v0/entities/0x64089a8e151eab71466d2c279e07bfc8e27d6aaa/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.