Purchased, reserved, available
Payment orders record USD and the number of credits issued. Model consumption is recorded in Credits. Purchased credits are not API usage. Your available balance is the ledger balance minus outstanding reservations.
Pricing shown during preview is illustrative. The production exchange rate, payment channel, and active channel prices must be published before paid execution is enabled.
Read your balance
GET /v1/balance requires usage:read. It returns balance_credits, reserved_credits, and available_credits. A new account may correctly return zero. The endpoint never creates trial credits or runs a payment.
Example balance
{
"balance_credits": 0,
"reserved_credits": 0,
"available_credits": 0
}Four results, one clear total
| Result | Charge | Released |
|---|---|---|
| Low-cost success | 20 Credits | 40 Credits |
| Low-cost success | 20 Credits | 40 Credits |
| Official success | 60 Credits | 0 Credits |
| Both attempts failed | 0 Credits | 60 Credits |
| Total / 240 initially reserved | 100 Credits | 140 Credits |
Example only. Failed attempts are platform costs; they are not added to the user’s bill. Each result item has at most one final consumption entry.
Prices are locked at acceptance
- Each channel has its own parameter-based price, including rounding, minimum units, and applicable surcharges.
- Official success uses the disclosed official rate; low-cost success uses the low-cost rate. A later price edit cannot increase an accepted request’s cap.
- Unknown items retain only their own reservation. Known successful and failed siblings can settle or release independently.
- LLM stream interruption and native music bundles use their own published metering rules, not the image/video rule by assumption.