0x1cd3…96ed
Paid $18,798.62 of the $3068.58M Roundhouse has indexed across 1,402,563 wallets — 0.0006% of it.
Chains (from the recent scan): Ethereum (80)
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% | $18,798.62 | 80 | 1 |
$18,798.62 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.
- 0x7dbb…59e0 · last paid 1d ago$18,798.6280 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 | |
|---|---|---|---|---|---|
| 0x7dbb…59e0 | $18,798.62 | $0.00 | 80 | 1d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 80 observed settlements.
Organic volume $18,798.62 of $18,798.62 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x1cd3…96ed0x7dbb…59e0 | Ethereum | $47.08 | 70% | 0x323a…a4f2 | 279d ago | 0xbbe1a7…840011 |
| 0x1cd3…96ed0x7dbb…59e0 | Ethereum | $253.74 | 70% | 0x323a…a4f2 | 280d ago | 0x8b5b7c…4287a2 |
| 0x1cd3…96ed0x7dbb…59e0 | Ethereum | $138.45 | 70% | 0x323a…a4f2 | 286d ago | 0xd0a80d…34dbbf |
| 0x1cd3…96ed0x7dbb…59e0 | Ethereum | $307.78 | 70% | 0x323a…a4f2 | 286d ago | 0x556c35…b86600 |
| 0x1cd3…96ed0x7dbb…59e0 | Ethereum | $304.43 | 70% | 0x323a…a4f2 | 290d ago | 0xa3a67c…6bf7be |
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 0x1cd3…96ed has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1cd3278719718e26d25d5adfda028237952096ed
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: 0x1cd3…96ed curl -s 'https://api.roundhouseai.io/v0/agents/0x1cd3278719718e26d25d5adfda028237952096ed' curl -s 'https://api.roundhouseai.io/v0/entities/0x1cd3278719718e26d25d5adfda028237952096ed/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.