0xfa8c…6f6d
Paid $656.00 of the $3058.83M Roundhouse has indexed across 1,396,904 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (23)
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 | 99% | $647.60 | 22 | 2 |
| Web & Content | 1% | $8.40 | 1 | 1 |
$647.60 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.
- 0x47c5…4fc3 · last paid 5d ago$451.2515 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x0e3d…7757 · last paid 81d ago$196.357 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xff45…9f15 · last paid 94d ago$8.401 call
▸20 catalogued endpoints, none priced at an amount this agent paid
- /v1/network/request$0.01 listed
- /v1/ip/lookup$0.003 listed
- /v1/web/tls/deep$0.10 listed
- /v1/bgp/lookup$0.005 listed
- /v1/ports/check$0.003 listed
- /v1/web/check$0.005 listed
- /v1/dns/propagation$0.001 listed
- /v1/vm/create$2.80 listed
12 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 | |
|---|---|---|---|---|---|
| 0x47c5…4fc3 | $451.25 | $0.00 | 15 | 5d ago | Graph |
| 0x0e3d…7757 | $196.35 | $0.00 | 7 | 81d ago | Graph |
| 0xff45…9f15 | $8.40 | $0.00 | 1 | 94d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
69% of observed volume is with a single counterparty, in all 23 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 0xfa8c…6f6d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xfa8ccb4d824eb22d478eb22cbbf3881ac2d06f6d
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: 0xfa8c…6f6d curl -s 'https://api.roundhouseai.io/v0/agents/0xfa8ccb4d824eb22d478eb22cbbf3881ac2d06f6d' curl -s 'https://api.roundhouseai.io/v0/entities/0xfa8ccb4d824eb22d478eb22cbbf3881ac2d06f6d/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.