0x7a71…a369
Paid $1.00 of the $3061.41M Roundhouse has indexed across 1,398,256 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (114)
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 | 63% | $0.63 | 1 | 1 |
| Web & Content | 37% | $0.37 | 112 | 1 |
$0.63 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.
- 0xd926…fa3d · last paid 39d ago$0.631 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x1670…fd4d · last paid 42d ago$0.37112 calls
▸99 of 99 catalogued endpoints list a price this agent paid
- /api/checkPrice match$0.002 listed
- /api/statsPrice match$0.003 listed
- /api/searchPrice matchWeb search$0.005 listed
- /api/checkPrice match$0.002 listed
- /api/searchPrice matchWeb search$0.005 listed
- /api/statsPrice match$0.003 listed
- /api/statsPrice match$0.003 listed
- /api/searchPrice matchWeb search$0.005 listed
91 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| 0x1670…fd4d | $0.37 | $1.00 | 113 | 42d ago | Graph |
| 0xd926…fa3d | $0.63 | $0.00 | 1 | 39d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
68% of observed volume is with a single counterparty, in all 114 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 0x7a71…a369 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7a71dc7b67bb972765b94a0dc0d878e944d7a369
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: 0x7a71…a369 curl -s 'https://api.roundhouseai.io/v0/agents/0x7a71dc7b67bb972765b94a0dc0d878e944d7a369' curl -s 'https://api.roundhouseai.io/v0/entities/0x7a71dc7b67bb972765b94a0dc0d878e944d7a369/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.