0x9369…d392
Paid $6.54 of the $847.14M Roundhouse has indexed across 1,330,737 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (776)
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% | $6.54 | 776 | 2 |
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 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x8324…fd0e · last paid 335d ago$6.06606 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /x402/tools/analyze_tokenPrice match$0.01 listed
- 0x0495…eed9 · last paid 347d ago$0.48170 calls
▸12 of 13 catalogued endpoints list a price this agent paid
- /x402/tools/get_onchain_trustPrice match$0.01 listed
- /x402/tools/get_social_trustPrice match$0.01 listed
- /x402/tools/get_webpage_trustPrice match$0.01 listed
- /x402/tools/get_available_resourcesPrice match$0.01 listed
- /x402/tools/get_overall_scorePrice match$0.01 listed
- /x402/tools/get_webpage_trustPrice match$0.01 listed
- /x402/tools/get_social_trustPrice match$0.01 listed
- /x402/tools/evaluate_agent_payment$0.10 listed
5 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 | |
|---|---|---|---|---|---|
| 0x8324…fd0e | $6.06 | $0.00 | 606 | 335d ago | Graph |
| 0x0495…eed9 | $0.48 | $0.00 | 170 | 347d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
93% of observed volume is with a single counterparty, in all 776 observed settlements.
Organic volume $6.54 of $6.54 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 0x9369…d392 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x936900f356cddea206d5a28e1ccc8023d713d392
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: 0x9369…d392 curl -s 'https://api.roundhouseai.io/v0/agents/0x936900f356cddea206d5a28e1ccc8023d713d392' curl -s 'https://api.roundhouseai.io/v0/entities/0x936900f356cddea206d5a28e1ccc8023d713d392/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.