0x1069…3e83
Paid $5.40 of the $3064.22M Roundhouse has indexed across 1,399,483 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 (54)
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 |
|---|---|---|---|---|
| Crypto Markets | 100% | $5.40 | 54 | 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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0xdb5c…10fd · last paid 104d ago$5.4054 calls
▸40 of 41 catalogued endpoints list a price this agent paid
- /api/v1/macro/:var1Price match$0.10 listed
- /api/v1/analytics/:var1Price match$0.10 listed
- /api/v1/futures/snapshotPrice match$0.10 listed
- /api/v1/perpetuals/volumePrice match$0.10 listed
- /api/v1/perpetuals/liquidationsPrice match$0.10 listed
- /api/v1/options/ticker-historyPrice match$0.10 listed
- /api/v1/perpetuals/reference-pricePrice match$0.10 listed
- /api/v1/perpetuals/level1Price match$0.10 listed
33 further catalogued endpoints not 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 | |
|---|---|---|---|---|---|
| 0xdb5c…10fd | $5.40 | $0.00 | 54 | 104d 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 54 observed settlements.
Organic volume $5.40 of $5.40 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x1069…3e830xdb5c…10fd | Base | $0.10 | 100% | payAI | 104d ago | 0x562cda…a5a9d6 |
| 0x1069…3e830xdb5c…10fd | Base | $0.10 | 100% | payAI | 104d ago | 0xca4fd0…37c8c9 |
| 0x1069…3e830xdb5c…10fd | Base | $0.10 | 100% | payAI | 111d ago | 0x135fc5…746539 |
| 0x1069…3e830xdb5c…10fd | Base | $0.10 | 100% | payAI | 134d ago | 0x8840fe…cfbd93 |
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 0x1069…3e83 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x10694fb6349c0a873c546a7067dc8c90b8083e83
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: 0x1069…3e83 curl -s 'https://api.roundhouseai.io/v0/agents/0x10694fb6349c0a873c546a7067dc8c90b8083e83' curl -s 'https://api.roundhouseai.io/v0/entities/0x10694fb6349c0a873c546a7067dc8c90b8083e83/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.