0xf9d1…d5f1
Paid $92.48 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (234)
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% | $92.48 | 1 | 1 |
$92.48 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.
- 0x09ae…ec64 · last paid 2d ago$92.481 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
ERC-8004 registration
- Declares 6 endpoints, none of them in any catalogue we crawl
- Ethereum · #9382
- Base · #1380
Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1
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 | |
|---|---|---|---|---|---|
| 0x09ae…ec64 | $92.48 | $0.00 | 1 | 2d ago | Graph |
| 0x22cf…2c79 | $0.00 | $4.34 | 33 | 327d ago | Graph |
| 0x831a…d02c | $0.00 | $3.50 | 8 | 329d ago | Graph |
| 0x9d3d…d837 | $0.00 | $0.58 | 58 | 1d ago | Graph |
| 0xfe2d…97fb | $0.00 | $0.50 | 1 | 373d ago | Graph |
| 0x8d2a…7d37 | $0.00 | $0.25 | 25 | 63d ago | Graph |
| 0xec2a…d034 | $0.00 | $0.24 | 24 | 18d ago | Graph |
| 0xc85f…0604 | $0.00 | $0.22 | 22 | 72d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
90% of observed volume is with a single counterparty, in all 234 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 0xf9d1…d5f1 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf9d1d63f362bbf1ee08ab9acb36fe74afc48d5f1
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: 0xf9d1…d5f1 curl -s 'https://api.roundhouseai.io/v0/agents/0xf9d1d63f362bbf1ee08ab9acb36fe74afc48d5f1' curl -s 'https://api.roundhouseai.io/v0/entities/0xf9d1d63f362bbf1ee08ab9acb36fe74afc48d5f1/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.