0x34a4…3fea
Paid $1.74 of the $834.02M Roundhouse has indexed across 1,300,437 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (122)
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% | $1.73 | 122 | 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.
- 0xb58d…2075 · last paid 4d ago$1.73122 calls
▸39 of 39 catalogued endpoints list a price this agent paid
- /v1/sanctions/walletPrice matchSanctions screening$0.003 listed
- /v1/home/reportPrice match$0.04 listed
- /v1/sanctions/screenPrice matchSanctions screening$0.005 listed
- /v1/vehicle/apkPrice match$0.001 listed
- /v1/email/verifyPrice matchEmail verification$0.002 listed
- /v1/phone/verifyPrice match$0.003 listed
- /v1/address/reversePrice matchGeocoding$0.002 listed
- /v1/postcode/addressesPrice match$0.005 listed
31 further catalogued endpoints not listed.
Funds flow over time
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 122 observed settlements.
Organic volume $1.74 of $1.74 total.
Recent activity
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 0x34a4…3fea has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x34a478a1dade7a8c26dfa6f24e200677742d3fea
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: 0x34a4…3fea curl -s 'https://api.roundhouseai.io/v0/agents/0x34a478a1dade7a8c26dfa6f24e200677742d3fea' curl -s 'https://api.roundhouseai.io/v0/entities/0x34a478a1dade7a8c26dfa6f24e200677742d3fea/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.