Know the limits

Data and verification

Read-only reserve and wallet-position APIs, finalized funding and payout evidence.

Read-only Float data#

The public API reports verified reserves and holder positions. All lamport and raw-token amounts are decimal strings so callers can use integer arithmetic.

Endpoint

Returns

GET /api/float

Aggregate reserve status and per-token summaries.

GET /api/float/:mint

Reserve, reserved obligations, covered loss, paid rebates and index status.

GET /api/float/:mint/wallet/:wallet

Current holdings, verified basis, uncovered loss, pending and paid rebates.

GET /api/float/wallet/:wallet

Recorded positions for a wallet, with index status.

Keep uncertainty intact#

Summary index status is syncing, ready or blocked. Wallet positions can be eligible, no-loss, excluded or history-incomplete.

When history or price is incomplete, do not interpret a zero unsupported loss as verified no-loss. The position reason and index reason explain the limitation. Eligible loss can be null until the required evidence is complete.

Finalized evidence comes first#

Reserve credits require verified finalized funding. A payout moves to paid only after finalized payment evidence. Reconciliation distinguishes allocated, submitted and completed operations.

Frontend displays refresh on a bounded 15-second polling loop for reserve and wallet status. Market and board updates also use the live socket feed.