0xc0be…745e
Paid $1.00 of the $846.52M Roundhouse has indexed across 1,329,508 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (17)
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% | $1.00 | 17 | 2 |
$0.97 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; for 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xd1b1…2887 · last paid 19d ago$0.972 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xd494…2b71 · last paid 28d ago$0.0315 calls
▸10 of 16 catalogued endpoints list a price this agent paid
- /services/hash-integrityPrice match$0.001 listed
- /services/json-toolboxPrice match$0.001 listed
- /services/encoding-toolboxPrice match$0.001 listed
- /services/http-header-auditPrice match$0.001 listed
- /services/x402-lensPrice match$0.001 listed
- /services/environment-contractPrice match$0.001 listed
- /services/crypto-feed$0.003 listed
- /services/hacker-feed$0.003 listed
8 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 | |
|---|---|---|---|---|---|
| 0xd1b1…2887 | $0.97 | $0.00 | 2 | 19d ago | Graph |
| 0xd494…2b71 | $0.03 | $0.00 | 15 | 28d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
97% of observed volume is with a single counterparty, in all 17 observed settlements.
Organic volume $1.00 of $1.00 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 0xc0be…745e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xc0beb64c095d28f80e02474cbe528514cbf5745e
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: 0xc0be…745e curl -s 'https://api.roundhouseai.io/v0/agents/0xc0beb64c095d28f80e02474cbe528514cbf5745e' curl -s 'https://api.roundhouseai.io/v0/entities/0xc0beb64c095d28f80e02474cbe528514cbf5745e/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.