0x416c…50c2
Paid $0.003 of the $260.88M Roundhouse has indexed across 716,644 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1)
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 |
|---|---|---|---|---|
| Location & Weather | 100% | $0.003 | 1 | 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.
- 0xdadc…b9df · last paid 14d ago$0.0031 call
▸7 of 184 catalogued endpoints list a price this agent paid
- /web/extractPrice matchPage to markdown$0.003 listed
- /openai/gpt-4o$0.10 listed
- /domain-availability/check$0.05 listed
- /crypto/market$0.005 listed
- /dns/lookup$0.002 listed
- /api/v1/chat/completionsText completion$0.005 listed
- /exa/searchWeb search$0.01 listed
- /schema-parse/extractDocument extraction$0.10 listed
176 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xdadc…b9df | $0.003 | $0.00 | 1 | 14d 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 1 observed settlement.
Organic volume $0.003 of $0.003 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x416c…50c20xdadc…b9df | Base | $0.003 | 100% | coinbase | 14d ago | 0x6877ff…ed9007 |
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 0x416c…50c2 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x416c2fbb3cd7e0e0ecdd0e0d58ab8491b57150c2
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: 0x416c…50c2 curl -s 'https://api.roundhouseai.io/v0/agents/0x416c2fbb3cd7e0e0ecdd0e0d58ab8491b57150c2' curl -s 'https://api.roundhouseai.io/v0/entities/0x416c2fbb3cd7e0e0ecdd0e0d58ab8491b57150c2/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.