0x366c…b37f
Paid $11,751.00 of the $3059.84M Roundhouse has indexed across 1,397,496 wallets — 0.0004% of it.
Chains (from the recent scan): Ethereum (70)
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% | $11,751.00 | 70 | 2 |
$11,751.00 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.
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.
- 0x23d7…a9b3 · last paid 3d ago$9,351.0053 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x427b…c8d3 · last paid 133d ago$2,400.0017 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
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 | |
|---|---|---|---|---|---|
| 0x23d7…a9b3 | $9,351.00 | $0.00 | 53 | 3d ago | Graph |
| 0x427b…c8d3 | $2,400.00 | $0.00 | 17 | 133d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
80% of observed volume is with a single counterparty, in all 70 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 0x366c…b37f has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x366cb0c7e906664d94cf4c5abf16d68d3e19b37f
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: 0x366c…b37f curl -s 'https://api.roundhouseai.io/v0/agents/0x366cb0c7e906664d94cf4c5abf16d68d3e19b37f' curl -s 'https://api.roundhouseai.io/v0/entities/0x366cb0c7e906664d94cf4c5abf16d68d3e19b37f/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.