0x05fd…a7d6
Paid $0.06 of the $3059.45M Roundhouse has indexed across 1,397,282 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1002)
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 | 98% | $0.06 | 1 | 1 |
| Crypto Markets | 2% | $0.001 | 1 | 1 |
$0.06 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.
- 0xb075…59d8 · last paid 68d ago$0.061 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 69d ago$0.0011 call
▸62 of 200 catalogued endpoints list a price this agent paid
- /v1/metered/chat/completionsPrice matchText completion$0.001 listed
- /api/hashPrice match$0.001 listed
- /api/onchain-sql$0.04 listed
- /api/perp-basis$0.002 listed
- /api/perp-fundingPerp funding and open interest$0.002 listed
- /api/weather-historyWeather forecast$0.002 listed
- /api/searchWeb search$0.01 listed
- /v1/nano/chat/completionsText completion$0.003 listed
192 further catalogued endpoints not listed.
Folded from this wallet's 1,002 most recent settlements of 1,118 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 | |
|---|---|---|---|---|---|
| 0x4aa7…0477 | $0.00 | $61.13 | 351 | 63d ago | Graph |
| 0x3a84…561e | $0.00 | $4.00 | 27 | 68d ago | Graph |
| 0xb9d9…2bb7 | $0.00 | $4.00 | 27 | 68d ago | Graph |
| 0xd5f6…80f5 | $0.00 | $4.00 | 27 | 68d ago | Graph |
| 0xe25c…143f | $0.00 | $4.00 | 27 | 68d ago | Graph |
| 0x3949…8de2 | $0.00 | $2.00 | 37 | 68d ago | Graph |
| 0xe9c4…09e9 | $0.00 | $2.00 | 37 | 68d ago | Graph |
| 0xc548…eb43 | $0.00 | $2.00 | 25 | 68d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
50% of observed volume is with a single counterparty, in the 1002 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 0x05fd…a7d6 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x05fdaf598d420e7caf649928c1893764ddf8a7d6
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: 0x05fd…a7d6 curl -s 'https://api.roundhouseai.io/v0/agents/0x05fdaf598d420e7caf649928c1893764ddf8a7d6' curl -s 'https://api.roundhouseai.io/v0/entities/0x05fdaf598d420e7caf649928c1893764ddf8a7d6/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.