0xf943…5d68
Paid $3.33 of the $259.22M Roundhouse has indexed across 714,420 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (78)
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% | $3.33 | 43 | 3 |
$2.23 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 3 the amount paid narrows the list to the ones listed at that price.
- 0xcc19…930e · last paid 5d ago$2.2022 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x159b…4908 · last paid 10h ago$1.1020 calls
▸4 of 4 catalogued endpoints list a price this agent paid
- /goPrice match$0.10 listed
- /payPrice match$0.01 listed
- /nftPrice match$0.10 listed
- /x402/nft-mint/api/verify-and-mintPrice match$0.10 listed
- 0x8736…2aab · last paid 14d ago$0.031 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
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 | |
|---|---|---|---|---|---|
| 0x0a84…2d12 | $0.00 | $3.33 | 35 | 11h ago | Graph |
| 0xcc19…930e | $2.20 | $0.00 | 22 | 5d ago | Graph |
| 0x159b…4908 | $1.10 | $0.00 | 20 | 10h ago | Graph |
| 0x8736…2aab | $0.03 | $0.00 | 1 | 14d 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 all 78 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 0xf943…5d68 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf9433ea53d9955e6af8d7d6ae4e9c74c18a75d68
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: 0xf943…5d68 curl -s 'https://api.roundhouseai.io/v0/agents/0xf9433ea53d9955e6af8d7d6ae4e9c74c18a75d68' curl -s 'https://api.roundhouseai.io/v0/entities/0xf9433ea53d9955e6af8d7d6ae4e9c74c18a75d68/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.