0xc43fd2c8fad82006055b19a6d2b94067676bfa2a
Paid $0.50 of the $3151.43M Roundhouse has indexed across 1,426,153 wallets — less than 0.0001% of it.
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 |
|---|---|---|---|---|
| Risk & Compliance | 100% | $0.50 | 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xf121…431b · last paid 152d ago$0.501 call
▸141 catalogued endpoints, none priced at an amount this agent paid
- /api/locus-parcel-lookup$0.01 listed
- /api/locus-wikipedia-place-context$0.01 listed
- /api/locus-pfas-occurrence$0.01 listed
- /api/locus-storm-events$0.01 listed
- /api/locus-appeal-window$0.01 listed
- /api/locus-wildfire-history$0.01 listed
- /api/locus-nfip-claims$0.01 listed
- /api/locus-zoning$0.01 listed
133 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 | |
|---|---|---|---|---|---|
| 0x5239…f64c | $0.00 | $3.00 | 1 | 152d ago | Graph |
| velinus.eth | $0.50 | $0.00 | 1 | 152d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
86% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xc43f…fa2avelinus.eth | Base | $0.50 | 100% | coinbase | 152d ago | 0xe2055c…def23b |
| 0x5239…f64c0xc43f…fa2a | Base | $3.00 | 70% | 0xa923…c9ac | 152d ago | 0x145836…7aa584 |
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 0xc43fd2c8fad82006055b19a6d2b94067676bfa2a has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xc43fd2c8fad82006055b19a6d2b94067676bfa2a
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: 0xc43fd2c8fad82006055b19a6d2b94067676bfa2a curl -s 'https://api.roundhouseai.io/v0/agents/0xc43fd2c8fad82006055b19a6d2b94067676bfa2a' curl -s 'https://api.roundhouseai.io/v0/entities/0xc43fd2c8fad82006055b19a6d2b94067676bfa2a/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.