0x7d20…8eae
Paid $2.00 of the $843.76M Roundhouse has indexed across 1,323,340 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
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 | 70% | $1.40 | 1 | 1 |
| AI & Media | 30% | $0.60 | 1 | 1 |
$1.40 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.
- 0x37a5…a312 · last paid 22d ago$1.401 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xabf4…a9d0 · last paid 23d ago$0.601 call
▸200 catalogued endpoints, none priced at an amount this agent paid
- /api/perp-fundingPerp funding and open interest$0.002 listed
- /api/perp-basis$0.002 listed
- /v1/metered/chat/completionsText completion$0.001 listed
- /api/searchWeb search$0.01 listed
- /api/decide$0.02 listed
- /api/sol-token-safety$0.005 listed
- /api/weather-historyWeather forecast$0.002 listed
- /api/hash$0.001 listed
192 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0x37a5…a312 | $1.40 | $0.00 | 1 | 22d ago | Graph |
| 0xabf4…a9d0 | $0.60 | $0.00 | 1 | 23d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
70% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x7d20…8eae0x37a5…a312 | Base | $1.40 | 100% | primer | 22d ago | 0xfc0297…b47ad7 |
| 0x7d20…8eae0xabf4…a9d0 | Base | $0.60 | 100% | coinbase | 23d ago | 0x7d767f…30c39e |
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…8eae has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7d2084b69ea3cd19b29da2c86bf3615351da8eae
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…8eae curl -s 'https://api.roundhouseai.io/v0/agents/0x7d2084b69ea3cd19b29da2c86bf3615351da8eae' curl -s 'https://api.roundhouseai.io/v0/entities/0x7d2084b69ea3cd19b29da2c86bf3615351da8eae/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.