0x6e64…ca4d
Paid $2.00 of the $258.35M Roundhouse has indexed across 712,918 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (15)
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.00 | 14 | 3 |
$0.30 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 3 the amount paid narrows the list to the ones listed at that price.
- 0x4e9b…5edb · last paid 327d ago$1.206 calls
▸7 catalogued endpoints, none priced at an amount this agent paid
- /token/gems-list$0.01 listed
- /token/leaderboard$0.01 listed
- /twitter/@canza_io$0.10 listed
- /token/gems-list$0.01 listed
- /token/leaderboard$0.01 listed
- /twitter/@canza_io$1.00 listed
- /token/address$0.10 listed
- 0xf7b1…9d57 · last paid 327d ago$0.505 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /touchPrice match$0.10 listed
- 0x45a3…44a7 · last paid 327d ago$0.303 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 | |
|---|---|---|---|---|---|
| 0x4e9b…5edb | $1.20 | $2.00 | 7 | 327d ago | Graph |
| 0xf7b1…9d57 | $0.50 | $0.00 | 5 | 327d ago | Graph |
| 0x45a3…44a7 | $0.30 | $0.00 | 3 | 327d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
80% of observed volume is with a single counterparty, in all 15 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 0x6e64…ca4d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x6e647743e97473286a3c5f166d919b59ca5aca4d
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: 0x6e64…ca4d curl -s 'https://api.roundhouseai.io/v0/agents/0x6e647743e97473286a3c5f166d919b59ca5aca4d' curl -s 'https://api.roundhouseai.io/v0/entities/0x6e647743e97473286a3c5f166d919b59ca5aca4d/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.