0x7406…db83
Paid $2.05 of the $258.25M Roundhouse has indexed across 712,699 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1488)
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 |
|---|---|---|---|---|
| Web & Content | 55% | $0.62 | 492 | 1 |
| Not in any catalogue | 45% | $0.51 | 508 | 1 |
$0.51 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.
- 0x2880…4e5e · last paid 39m ago$0.62492 calls
▸194 of 200 catalogued endpoints list a price this agent paid
- /feiertagePrice match$0.001 listed
- /demo/paid-samplePrice match$0.001 listed
- /stackPrice match$0.003 listed
- /v1/anti-cheat-scanPrice match$0.004 listed
- /predict/negative-pricePrice match$0.001 listed
- /v1/sms-receivePrice match$0.006 listed
- /v1/pathogen-r0Price match$0.003 listed
- /product/compare$0.01 listed
192 further catalogued endpoints not listed.
- 0x617d…cc9f · last paid 19d ago$0.51508 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Folded from this wallet's 1,488 most recent settlements of 2,330 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. 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 | |
|---|---|---|---|---|---|
| 0x617d…cc9f | $0.51 | $0.49 | 996 | 19d ago | Graph |
| 0x2880…4e5e | $0.62 | $0.00 | 492 | 39m ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
62% of observed volume is with a single counterparty, in the 1488 most recent settlements scanned (its history is longer than the 2000-row scan cap).
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 0x7406…db83 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7406ca907cf8fd39a6ecfffa8e1be71c103fdb83
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: 0x7406…db83 curl -s 'https://api.roundhouseai.io/v0/agents/0x7406ca907cf8fd39a6ecfffa8e1be71c103fdb83' curl -s 'https://api.roundhouseai.io/v0/entities/0x7406ca907cf8fd39a6ecfffa8e1be71c103fdb83/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.