0xcc51…b86a
Paid $0.13 of the $261.41M Roundhouse has indexed across 717,464 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (20)
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 |
|---|---|---|---|---|
| AI & Media | 100% | $0.13 | 20 | 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 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xe903…1abf · last paid 5d ago$0.1011 calls
▸78 of 200 catalogued endpoints list a price this agent paid
- /api/v1/chat/completionsPrice matchText completion$0.002 listed
- /api/v1/messagesPrice match$0.01 listed
- /api/v1/exa/answerPrice matchText completion$0.01 listed
- /api/v1/exa/searchPrice matchWeb search$0.01 listed
- /api/v1/exa/contents$0.003 listed
- /api/v1/images/generations$0.04 listed
- /api/v1/searchWeb search$0.26 listed
- /api/v1/videos/generations$0.40 listed
192 further catalogued endpoints not listed.
- 0x8581…c402 · last paid 56d ago$0.039 calls
▸16 catalogued endpoints, none priced at an amount this agent paid
- /x402/api/twitter/v2/tweets/search/recent$0.05 listed
- /x402/api/inference/v1/chat/completionsText completion$0.003302 listed
- /x402/api/twitter/v2/tweets/search/all$0.05 listed
- /min30/v1/chat/completionsText completion$0.003301 listed
- /x402/api/twitter/v2/tweets/counts/all$0.01 listed
- /x402/api/twitter/v2/tweets$0.0079 listed
- /x402/api/twitter/v2/users/:userId/tweets$0.05 listed
- /x402/api/twitter/v2/tweets/:tweetId$0.0079 listed
8 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 | |
|---|---|---|---|---|---|
| 0xe903…1abf | $0.10 | $0.00 | 11 | 5d ago | Graph |
| 0x8581…c402 | $0.03 | $0.00 | 9 | 56d 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 20 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 0xcc51…b86a has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xcc51b36c7416971b4bba39b5151b2493566db86a
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: 0xcc51…b86a curl -s 'https://api.roundhouseai.io/v0/agents/0xcc51b36c7416971b4bba39b5151b2493566db86a' curl -s 'https://api.roundhouseai.io/v0/entities/0xcc51b36c7416971b4bba39b5151b2493566db86a/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.