Get Account Balance

Choose the scope and credential first

• One key's usage/budget: call GET /v1/key with that inference API key. Read usage, limit_remaining, and limit_reset. This is a key spending budget, not the enterprise wallet or credit balance.
• Enterprise wallet and credit: call GET /enterprise/v1/billing/balance with a MANAGEMENT key scoped only to tenant:billing:read. Inference and PROVISIONING keys cannot use it.
• Account charges/request reconciliation: existing GET /v1/billing and GET /v1/billing/requests/{request_id} use an inference key or signed-in JWT. Management keys cannot call these /v1 endpoints. Recorded charges and remaining balance are different metrics.
• Legacy account balance: GET /v1/billing/balance remains compatible and reports account funds, not the calling key's remaining budget. Prefer the Enterprise endpoint for new enterprise balance monitoring.

Enterprise API guide · Get enterprise balance

Postpaid funding semantics

All amounts are USD. Under POSTPAY, positive wallet top-up funds are spent first and the remainder uses enterprise credit. Promotional Credit/vouchers are neither spent nor included in the total.

• credit_limit_usd: approved credit limit.
• current_exposure_usd: credit used in the current open billing period.
• credit_remaining_usd: max(credit_limit_usd - current_exposure_usd, 0).
• credit_available: remaining enterprise credit under POSTPAY; available vouchers under PREPAY. These meanings are different.
• total_spendable: max(wallet_available, 0) + credit_remaining_usd for POSTPAY; the existing wallet_available + credit_available for PREPAY.

Historical unpaid invoices are not deducted from remaining credit a second time. Balances are snapshots of recorded billing data, not real-time reservations. Exhausted credit, key limits, account spend protection or other policies can still reject requests. Exhausted credit blocks new POSTPAY calls even if wallet funds remain, so the total is not a guarantee of callable capacity.

Authentication

Use an inference API key or signed-in JWT. MANAGEMENT / PROVISIONING keys cannot use this path. Enterprise members resolve both wallet and credit to the enterprise billing owner.

Response