0x6c16…64bc
Paid $1.75 of the $258.35M Roundhouse has indexed across 712,918 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (248)
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.75 | 248 | 4 |
$1.75 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.
- 0x136d…5312 · last paid 107d ago$1.503 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xfee0…2411 · last paid 47d ago$0.24243 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xf9ed…a234 · last paid 89d ago$0.011 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xecab…bf76 · last paid 89d ago$0.0011 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
ERC-8004 registration
- Declares 1 endpoint, none of them in any catalogue we crawl
Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1
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 | |
|---|---|---|---|---|---|
| web3gezgini.eth | $1.50 | $0.00 | 3 | 107d ago | Graph |
| 0xfee0…2411 | $0.24 | $0.00 | 243 | 47d ago | Graph |
| 0xf9ed…a234 | $0.01 | $0.00 | 1 | 89d ago | Graph |
| 0xecab…bf76 | $0.001 | $0.00 | 1 | 89d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
86% of observed volume is with a single counterparty, in all 248 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 0x6c16…64bc has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x6c169b4d43e93500849f06d1a058d6f105ab64bc
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: 0x6c16…64bc curl -s 'https://api.roundhouseai.io/v0/agents/0x6c169b4d43e93500849f06d1a058d6f105ab64bc' curl -s 'https://api.roundhouseai.io/v0/entities/0x6c169b4d43e93500849f06d1a058d6f105ab64bc/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.