Org balance + recent transactions

Raw ledger balance (deposits + credits − settled debits).

Spendable balance = balanceCents − accruedUsageCents. This is what every control-plane billing gate checks. It includes pending compute and inference usage, can be below balanceCents while usage is running, and can be slightly negative between auto-recharge ticks.

Usage cost not yet settled into a transaction: current-month compute, pending inference, plus any recently ended compute month whose settlement debit has not been written yet. This is the amount netted from balanceCents to produce availableCents.

Total compute plus inference usage in the current UTC calendar month, including inference already drained into the ledger and the live pending inference accrual. Use this for "spend this month" displays; use accruedUsageCents for balance math.

Compute usage accrued in the current UTC calendar month.

Inference usage in the current UTC calendar month: settled whole-cent inference debits plus whole pending inference cents. A fractional pending cent is intentionally omitted instead of inflating displayed spend.

Whole inference cents not yet drained into the ledger. Fractional cents remain in nanoUSD in the accrual and are omitted from this integer display value.

Pending inference reserved by balance enforcement, rounded up to the next cent. This can be one cent higher than pendingInferenceCents.

Compute usage from recently ended months that is marked billable but whose settlement transaction has not been written yet.

The org's monthly spend cap, or null if no limit is set. Drives the "used of limit" budget gauge in the dashboard.

Smallest deposit the org can make right now, in cents: the flat $25 floor, raised to one hour of usage at the current burn while the org has open usage running, clamped to the org's per-deposit cap. This is the exact minimum the deposit endpoint enforces (INSUFFICIENT_RUNWAY on a lower amount), so clients should render it rather than re-derive it.