0x3416…6592
Paid $0.002 of the $716.75K Roundhouse has indexed across 25,161 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base Sepolia (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% | $0.002 | 2 | 2 |
$0.001 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.
- [Staging] 17711 Extract Correctstaging.api.17711.xyz0x6a4b…c23b · last paid 26d ago$0.0011 call
▸1 of 1 catalogued endpoints list a price this agent paid
- /registry/extract-correct-service/v1/extract-correct/parse_jsonPrice match$0.001 listed
- 0xa1e9…96e5 · last paid 70d ago$0.0011 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 | |
|---|---|---|---|---|---|
| [Staging] 17711 Extract Correct | $0.001 | $0.00 | 1 | 26d ago | Graph |
| 0xa1e9…96e5 | $0.001 | $0.00 | 1 | 70d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
50% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x3416…6592[Staging] 17711 Extract Correct | Base Sepolia | $0.001 | 100% | payAI | 26d ago | 0x5f4307…9af582 |
| 0x3416…65920xa1e9…96e5 | Base Sepolia | $0.001 | 70% | 0xd407…f1bf | 70d ago | 0xf23532…0f5342 |
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 0x3416…6592 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x3416933ead830ac3491605fcd920b665114b6592
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: 0x3416…6592 curl -s 'https://api.roundhouseai.io/v0/agents/0x3416933ead830ac3491605fcd920b665114b6592' curl -s 'https://api.roundhouseai.io/v0/entities/0x3416933ead830ac3491605fcd920b665114b6592/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://preview.roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://preview.roundhouseai.io/skill.md first — it is the whole procedure.