0x3c3a85ad3d314f4331948686c94350ae83f10e7a
Paid $1.49 of the $258.54M Roundhouse has indexed across 713,171 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (43)
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 |
|---|---|---|---|---|
| Web & Content | 75% | $1.12 | 35 | 1 |
| Not in any catalogue | 25% | $0.37 | 8 | 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 2 the amount paid narrows the list to the ones listed at that price.
- 0x325b…d430 · last paid 111d ago$1.1235 calls
▸26 of 68 catalogued endpoints list a price this agent paid
- /api/exa/searchPrice matchWeb search$0.01 listed
- /api/firecrawl/searchPrice matchWeb search$0.03 listed
- /api/exa/contents$0.002 listed
- /api/apollo/people-enrichPeople search$0.05 listed
- /api/fullenrich/people-searchPeople search$0.15 listed
- /api/whitepages/person-search$0.22 listed
- /api/pdl/people-enrichPeople search$0.28 listed
- /api/clado/contacts-enrichPeople search$0.20 listed
60 further catalogued endpoints not listed.
- 0x07f0…a045 · last paid 111d ago$0.378 calls
▸3 catalogued endpoints, none priced at an amount this agent paid
- /api/upload$0.01 listed
- /pay/agent_stablestudio_dev$0.01 listed
- /api/upload$0.01 listed
Funds flow over time
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x325b…d430 | $1.12 | $0.00 | 35 | 111d ago | Graph |
| 0x07f0…a045 | $0.37 | $0.00 | 8 | 111d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
75% of observed volume is with a single counterparty, in all 43 observed settlements.
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 0x3c3a85ad3d314f4331948686c94350ae83f10e7a has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x3c3a85ad3d314f4331948686c94350ae83f10e7a
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: 0x3c3a85ad3d314f4331948686c94350ae83f10e7a curl -s 'https://api.roundhouseai.io/v0/agents/0x3c3a85ad3d314f4331948686c94350ae83f10e7a' curl -s 'https://api.roundhouseai.io/v0/entities/0x3c3a85ad3d314f4331948686c94350ae83f10e7a/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.