0x2c68…a4d3
Paid $2,589.89 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.
Chains (from the recent scan): Ethereum (6)
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% | $2,589.89 | 3 | 1 |
$2,589.89 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.
- 0xa817…95e8 · last paid 404d ago$2,589.893 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x7c4d…4994 | $0.00 | $2,595.08 | 3 | 404d ago | Graph |
| 0xa817…95e8 | $2,589.89 | $0.00 | 3 | 404d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
50% of observed volume is with a single counterparty, in all 6 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x2c68…a4d30xa817…95e8 | Ethereum | $1,087.12 | 70% | 0xf9e1…77b9 | 404d ago | 0x65a0dc…70d1b0 |
| 0x7c4d…49940x2c68…a4d3 | Ethereum | $1,089.30 | 70% | 0xf9e1…77b9 | 404d ago | 0x8a6680…9ac2f8 |
| 0x2c68…a4d30xa817…95e8 | Ethereum | $501.19 | 70% | 0xf9e1…77b9 | 404d ago | 0xa76a07…380950 |
| 0x7c4d…49940x2c68…a4d3 | Ethereum | $502.19 | 70% | 0xf9e1…77b9 | 404d ago | 0xc1f065…e040b0 |
| 0x2c68…a4d30xa817…95e8 | Ethereum | $1,001.59 | 70% | 0xf9e1…77b9 | 404d ago | 0x97766a…abd84d |
| 0x7c4d…49940x2c68…a4d3 | Ethereum | $1,003.59 | 70% | 0xf9e1…77b9 | 404d ago | 0x6aa0fb…e4e444 |
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 0x2c68…a4d3 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x2c68e982cc16dde17ccc897cb5cc2646ee1fa4d3
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: 0x2c68…a4d3 curl -s 'https://api.roundhouseai.io/v0/agents/0x2c68e982cc16dde17ccc897cb5cc2646ee1fa4d3' curl -s 'https://api.roundhouseai.io/v0/entities/0x2c68e982cc16dde17ccc897cb5cc2646ee1fa4d3/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.