0x6d01…bb3e
Paid $0.01 of the $3061.41M Roundhouse has indexed across 1,398,256 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (45)
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% | $0.01 | 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.
- 0xf732…b829 · last paid 24d ago$0.012 calls
▸122 of 122 catalogued endpoints list a price this agent paid
- /v1/meadowPrice match$0.005 listed
- /v1/meme-watchPrice match$0.005 listed
- /v1/prompt-injection-detectPrice match$0.005 listed
- /v1/pump-checkPrice match$0.005 listed
- /v1/agentsearch-web-search-v1Price match$0.005 listed
- /v1/taint-checkPrice match$0.005 listed
- /v1/dns-whois-rdapPrice match$0.005 listed
- /v1/kr-apt-trades-v1Price match$0.005 listed
114 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0xa19f…accc | $0.00 | $0.12 | 9 | 5d ago | Graph |
| 0x51aa…b559 | $0.00 | $0.09 | 9 | 64d ago | Graph |
| 0x8d2a…7d37 | $0.00 | $0.07 | 24 | 63d ago | Graph |
| 0xf732…b829 | $0.01 | $0.00 | 2 | 24d ago | Graph |
| 0x64db…c368 | $0.00 | $0.01 | 1 | 68d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
No concentration or self-dealing patterns detected in all 45 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 0x6d01…bb3e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x6d017c4bc13f640c4d598d01dfd0d2813c85bb3e
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: 0x6d01…bb3e curl -s 'https://api.roundhouseai.io/v0/agents/0x6d017c4bc13f640c4d598d01dfd0d2813c85bb3e' curl -s 'https://api.roundhouseai.io/v0/entities/0x6d017c4bc13f640c4d598d01dfd0d2813c85bb3e/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.