0x316f…d1d1
Paid $1.25 of the $3058.83M Roundhouse has indexed across 1,396,716 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (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 |
|---|---|---|---|---|
| Not in any catalogue | 100% | $1.25 | 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.
- 0xc936…4775 · last paid 2d ago$1.253 calls
▸6 catalogued endpoints, none priced at an amount this agent paid
- /x402/bitquery/bagcheck/raw$0.40 listed
- /relay/1769629274857/x402/bitquery/latest-pairs$0.40 listed
- /x402/bitquery/latest-pairs$0.40 listed
- /x402/bitquery/rug-pull-scanner$1.15 listed
- /relay/1769629274857/x402/bitquery/mevdetection$1.15 listed
- /relay/1769629274857/x402/bitquery/top-tokens$0.55 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 | |
|---|---|---|---|---|---|
| 0xc936…4775 | $1.25 | $0.00 | 3 | 2d 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 $1.25 of $1.25 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x316f…d1d10xc936…4775 | Base | $0.50 | 100% | coinbase | 2d ago | 0xa3ed93…231f78 |
| 0x316f…d1d10xc936…4775 | Base | $0.25 | 100% | coinbase | 2d ago | 0xf9810d…c6b160 |
| 0x316f…d1d10xc936…4775 | Base | $0.50 | 100% | coinbase | 2d ago | 0xe4d261…cd63aa |
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 0x316f…d1d1 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x316f39c1b3de56dc551be4a75142c5d50671d1d1
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: 0x316f…d1d1 curl -s 'https://api.roundhouseai.io/v0/agents/0x316f39c1b3de56dc551be4a75142c5d50671d1d1' curl -s 'https://api.roundhouseai.io/v0/entities/0x316f39c1b3de56dc551be4a75142c5d50671d1d1/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.