0xe16c…64e0
Paid $148.61 of the $3066.17M Roundhouse has indexed across 1,400,092 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 |
|---|---|---|---|---|
| Web & Content | 100% | $148.61 | 3 | 1 |
Every merchant paid publishes at least one catalogued endpoint.
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.
- 0x480c…846a · last paid 47d ago$148.613 calls
▸8 catalogued endpoints, none priced at an amount this agent paid
- /x402/gift-cards/searchWeb search$0.002 listed
- /x402/checkout/info$0.001 listed
- /x402/invoice/create$0.002 listed
- /x402/invoice/pay$1,000.00 listed
- /x402/topups/searchWeb search$0.002 listed
- /x402/esims/searchWeb search$0.002 listed
- /x402/products/detail$0.001 listed
- /x402/invoice/status$0.001 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 | |
|---|---|---|---|---|---|
| 0x480c…846a | $148.61 | $0.00 | 3 | 47d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 3 observed settlements.
Organic volume $148.61 of $148.61 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xe16c…64e00x480c…846a | Ethereum | $25.71 | 70% | 0x480c…846a | 47d ago | 0x9069a9…56cd2b |
| 0xe16c…64e00x480c…846a | Ethereum | $100.00 | 70% | 0x480c…846a | 47d ago | 0xd7c99a…92a572 |
| 0xe16c…64e00x480c…846a | Ethereum | $22.90 | 70% | 0x480c…846a | 48d ago | 0x97e356…f67851 |
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 0xe16c…64e0 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xe16c343129100b14fdeb30be213d13f65e2d64e0
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: 0xe16c…64e0 curl -s 'https://api.roundhouseai.io/v0/agents/0xe16c343129100b14fdeb30be213d13f65e2d64e0' curl -s 'https://api.roundhouseai.io/v0/entities/0xe16c343129100b14fdeb30be213d13f65e2d64e0/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.