0x7d20…64c8
Paid $7,495.61 of the $3059.84M Roundhouse has indexed across 1,397,384 wallets — 0.0002% of it.
Chains (from the recent scan): Base (1397)
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% | $56.46 | 1,000 | 2 |
$41.42 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.
- 0x8977…bab8 · last paid 311d ago$41.422 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x66fa…2ec8 · last paid 312d ago$15.04998 calls
Folded from this wallet's 1,397 most recent settlements of 494,920 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.
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 | |
|---|---|---|---|---|---|
| 0x8977…bab8 | $41.42 | $2,990.00 | 130 | 311d ago | Graph |
| 0x4451…42db | $0.00 | $155.00 | 10 | 315d ago | Graph |
| 0x9603…c714 | $0.00 | $124.00 | 8 | 320d ago | Graph |
| 0x5f65…60db | $0.00 | $109.00 | 7 | 314d ago | Graph |
| 0x0b79…b32e | $0.00 | $102.00 | 6 | 325d ago | Graph |
| 0xf859…3172 | $0.00 | $92.00 | 6 | 314d ago | Graph |
| 0x5729…531b | $0.00 | $88.00 | 6 | 317d ago | Graph |
| 0xd997…66cb | $0.00 | $87.00 | 6 | 312d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
Not enough of this address's history was examined to assess it: self_dealing and counterparty_concentration and single_counterparty were computed over the 1397 most recent settlements scanned (its history is longer than the 2000-row scan cap), so nothing found there rules anything out. This is an incomplete check, not a clean record.
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 0x7d20…64c8 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7d20c5e7bd892aabee66bf8fbbc50534bccb64c8
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: 0x7d20…64c8 curl -s 'https://api.roundhouseai.io/v0/agents/0x7d20c5e7bd892aabee66bf8fbbc50534bccb64c8' curl -s 'https://api.roundhouseai.io/v0/entities/0x7d20c5e7bd892aabee66bf8fbbc50534bccb64c8/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.