FGQVbt…8eB2
Paid $7.42 of the $3105.10M Roundhouse has indexed across 1,405,259 wallets — less than 0.0001% of it.
Chains (from the recent scan): Solana (1000)
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% | $1.06 | 1,000 | 1 |
$1.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; no listed price matches an amount this agent paid, so nothing narrows them.
- BPz2u6…bMfD · last paid 85d ago$1.061,000 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Folded from this wallet's 1,000 most recent settlements of 7,290 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.
Wallet balance
Not read. Solana wallets are not supported by the balance and funding-history read yet. Nothing is shown here about this wallet's balance or funding, which is not the same as it holding none.
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 | |
|---|---|---|---|---|---|
| BPz2u6…bMfD | $1.06 | $0.00 | 1,000 | 85d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).
Organic volume $1.06 of $1.06 total.
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 FGQVbt…8eB2 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/FGQVbt7t7UKU5D9mcVK2aj7bD1QgwWRRmWEMfM8t8eB2
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: FGQVbt…8eB2 curl -s 'https://api.roundhouseai.io/v0/agents/FGQVbt7t7UKU5D9mcVK2aj7bD1QgwWRRmWEMfM8t8eB2' curl -s 'https://api.roundhouseai.io/v0/entities/FGQVbt7t7UKU5D9mcVK2aj7bD1QgwWRRmWEMfM8t8eB2/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.