0xc314…4c3d
Paid $0.10 of the $834.02M Roundhouse has indexed across 1,300,437 wallets — less than 0.0001% of it.
Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.
Chains (from the recent scan): Base (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 |
|---|---|---|---|---|
| Crypto Markets | 100% | $0.10 | 2 | 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.
- 0x3f60…bf2c · last paid 2d ago$0.102 calls
▸7 of 29 catalogued endpoints list a price this agent paid
- /v1/tokens/historyPrice matchCrypto price history$0.05 listed
- /v1/index/historyPrice match$0.05 listed
- /v1/index/fixing$0.01 listed
- /v1/tokens/quotes$0.01 listed
- /v1/capacity/stress$0.01 listed
- /v1/reserved$0.01 listed
- /v1/term/instance$0.01 listed
- /v1/spot/export/history$3.00 listed
21 further catalogued endpoints not listed.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x3f60…bf2c | $0.10 | $0.00 | 2 | 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 2 observed settlements.
Organic volume $0.10 of $0.10 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xc314…4c3d0x3f60…bf2c | Base | $0.05 | 100% | coinbase | 2d ago | 0xa5ba23…040ef6 |
| 0xc314…4c3d0x3f60…bf2c | Base | $0.05 | 100% | coinbase | 2d ago | 0xb6f997…38b107 |
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 0xc314…4c3d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xc31486065471b8efc2d6cb216e5b03763cd54c3d
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: 0xc314…4c3d curl -s 'https://api.roundhouseai.io/v0/agents/0xc31486065471b8efc2d6cb216e5b03763cd54c3d' curl -s 'https://api.roundhouseai.io/v0/entities/0xc31486065471b8efc2d6cb216e5b03763cd54c3d/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.