Platform
Billing
Prepaid credits
You pay in advance. Requests draw down a USD credit balance held by the organization.
- Top up from the dashboard's Billing page, in whole dollars from $10 to $10,000. Checkout is handled by Dodo Payments.
- The balance is credited when the payment succeeds. We credit the amount you chose; any tax is added on top at checkout and is not credited.
- Credit is valid for 12 months from purchase. It is used oldest first, and any part of a top-up still unused after 12 months expires.
- Each top-up sends an email and a
credits.addedwebhook.
When the balance reaches zero, requests fail with insufficient_credits (402). The check runs before each request, so the request that crosses zero completes, and the balance can end slightly below zero.
Invoice mode
Enterprise organizations can be billed by invoice. In invoice mode the balance may go negative, down to an agreed credit limit; requests fail with insufficient_credits only past that limit. GET /v1/credits shows billing_mode: "invoice" and the credit_limit. Contact sales to set it up.
Pricing rules
Each request is billed on the model that served it:
cost = (input_tokens − cached_tokens) × input_price
+ cached_tokens × cached_input_price
+ output_tokens × output_pricePrices are USD per 1M tokens, listed in GET /v1/models and on the Models page. Costs are rounded up to the nearest $0.000001.
| Rule | Detail |
|---|---|
| Abliterated models | Priced 10–20% above the standard sibling. Every launch pair is +15%. |
| Cached input | Billed at cached_input, usually about 10% of the input price. See Caching. |
| Reasoning tokens | Billed as output tokens. |
| Batches | 50% off the whole request. See Batches. |
| Auto router | No surcharge. You pay for the model that served the request. The router's own classification calls are free. |
| Refusal retry | The refused attempt is free. You pay for the retried answer. |
| Errors | Non-streaming requests that fail are free. A stream that fails or is closed part-way is billed for what it generated. |
| Estimated usage | If a backend reports no token counts, we estimate them (about 4 characters per token) and bill the estimate. The response says so with x-utmost-usage-estimated: true. |
| Bring your own model | A monthly serving fee plus per-token usage. See Bring your own model. |
Seeing cost per request
| Where | Field |
|---|---|
| Response headers (non-streaming) | x-utmost-cost-usd, x-utmost-input-tokens, x-utmost-cached-tokens, x-utmost-output-tokens |
| Chat completions body | usage.cost_usd |
| Chat completions stream | usage.cost_usd in the final chunk, with stream_options.include_usage |
| Responses | usage.cost_usd (in response.completed when streaming) |
| Messages | x-utmost-cost-usd header only, and not on streams |
| Batches | cost_usd on the batch, and usage.cost_usd on each result |
| Workflows | cost.total_usd and cost.per_pass |
The dashboard shows usage and cost for every request, including streams.
GET /v1/credits
Balance and spend for the calling key, its project and its organization.
curl https://api.utmost.site/v1/credits -H "Authorization: Bearer $UTMOST_API_KEY"{
"object": "credits",
"currency": "USD",
"balance": 24.998717,
"billing_mode": "prepaid",
"credit_limit": null,
"organization": { "id": "org_eOjrhwjgTiiam2oNlJVD", "tier": "verified", "month_to_date_spend": 0.001283 },
"project": { "id": "prj_Y9aTKhJIrBpYi8ueVw1f", "month_to_date_spend": 0.001283, "spend_cap": null },
"key": { "id": "key_NUZl7evjxRIH60U0kR9a", "month_to_date_spend": 0.001283, "spend_cap": null },
"period": "2026-11"
}Amounts are USD. period is the current billing month in UTC. spend_cap is null when no cap is set.
Spend caps
Set a monthly cap on any key and on any project in the dashboard.
- Spend is counted per calendar month, UTC, and resets on the 1st.
- At 50%, 80% and 100% of a cap we send one email and one webhook each:
spend.thresholdfor 50% and 80%,spend.cap_reachedfor 100%. - Once spend reaches the cap, requests on that key, or on any key in that project, fail with
spend_cap_reached(402) until you raise the cap or the month ends. - As with the balance, the check runs before each request. The request that crosses the cap completes, so spend can end slightly above it.
- BYO serving fees are charged to the organization's balance, not to key or project caps.
Low-balance alert
When the balance falls below your low-balance threshold (default $5, set on the Billing page), we send an email and a credits.low webhook, at most once a day. You can also set an alert email address there. When it is set, all account emails, including spend alerts, key suspensions and BYO updates, go to that address instead of the organization's members.
Refunds and chargebacks
Refunds are issued through Dodo Payments. A refund removes the refunded amount from your balance. A lost chargeback removes the disputed amount. Either can take the balance below zero, and requests then fail with insufficient_credits until you top up.