0x4683…910d
Paid $0.01 of the $3053.48M Roundhouse has indexed across 1,395,044 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (4)
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 |
|---|---|---|---|---|
| Onchain Data | 100% | $0.01 | 4 | 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.
- 0x64eb…3169 · last paid 4d ago$0.014 calls
▸5 of 8 catalogued endpoints list a price this agent paid
- /v1/allowancesPrice match$0.003 listed
- /v1/tokenPrice matchToken metadata$0.001 listed
- /v1/calldataPrice match$0.001 listed
- /v1/x402-validatePrice match$0.003 listed
- /v1/gasPrice matchGas price$0.001 listed
- /markdownPage to markdown$0.10 listed
- /v1/address$0.002 listed
- /verify$0.01 listed
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x64eb…3169 | $0.01 | $0.00 | 4 | 4d 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 4 observed settlements.
Organic volume $0.01 of $0.01 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x4683…910d0x64eb…3169 | Base | $0.003 | 100% | payAI | 4d ago | 0x953af3…61dc25 |
| 0x4683…910d0x64eb…3169 | Base | $0.003 | 100% | payAI | 4d ago | 0x151886…77f6a9 |
| 0x4683…910d0x64eb…3169 | Base | $0.005 | 100% | payAI | 4d ago | 0xab2b20…67378d |
| 0x4683…910d0x64eb…3169 | Base | $0.001 | 100% | payAI | 4d ago | 0x370c3c…f528c8 |
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 0x4683…910d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x4683706f0622aa5e94a8bb5d8275cc70ed64910d
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: 0x4683…910d curl -s 'https://api.roundhouseai.io/v0/agents/0x4683706f0622aa5e94a8bb5d8275cc70ed64910d' curl -s 'https://api.roundhouseai.io/v0/entities/0x4683706f0622aa5e94a8bb5d8275cc70ed64910d/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.