0x4094…f5d2
Paid $0.10 of the $3061.41M Roundhouse has indexed across 1,398,817 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (30)
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% | $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.
- 0x30a5…47e0 · last paid 58d ago$0.102 calls
▸4 of 41 catalogued endpoints list a price this agent paid
- /paid/ping$0.001 listed
- /paid/steam/deals$0.005 listed
- /paid/steam/top-sellers$0.005 listed
- /x402/kh7ce632kypmbvwy9ewcq04c998b8wb8$0.001 listed
- /paid/twitch/hype$0.02 listed
- /paid/game/metadataToken metadata$0.005 listed
- /paid/util/email-verify$0.003 listed
- /paid/util/site-intel$0.005 listed
33 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
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x30a5…47e0 | $0.10 | $0.00 | 2 | 58d ago | Graph |
| 0x6eb1…7dc3 | $0.00 | $0.01 | 2 | 20d ago | Graph |
| 0x7e57…2f09 | $0.00 | $0.008 | 4 | 59d ago | Graph |
| 0xa19f…accc | $0.00 | $0.004 | 4 | 12d ago | Graph |
| 0xc9c7…1670 | $0.00 | $0.003 | 3 | 20d ago | Graph |
| 0xa1d1…1978 | $0.00 | $0.002 | 2 | 11d ago | Graph |
| 0xfb4d…1753 | $0.00 | $0.002 | 2 | 18d ago | Graph |
| 0xc498…254a | $0.00 | $0.001 | 1 | 11d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
71% of observed volume is with a single counterparty, in all 30 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 0x4094…f5d2 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x4094383033c1861e2686eac4d4bbae6f0031f5d2
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: 0x4094…f5d2 curl -s 'https://api.roundhouseai.io/v0/agents/0x4094383033c1861e2686eac4d4bbae6f0031f5d2' curl -s 'https://api.roundhouseai.io/v0/entities/0x4094383033c1861e2686eac4d4bbae6f0031f5d2/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.