Pricing

Every amount on the platform is an integer number of micro-USD: 1,000,000 micro-USD = $1.00. No floats, no rounding surprises, and safe to sum.

1 micro-USD   = $0.000001
1,000 µ$      = $0.001
1,000,000 µ$  = $1.00

Where prices come from

GET /v1/models returns, per model, the customer list price (pricing) and your discount (discount_bps). Prices are per unit of usage:

A model may combine several keys (e.g. per_request + per_image). The price sheet is versioned; the version in force when your request ran is recorded with the request.

How a charge is computed

list_price_micro   = Σ usage_i × price_i        (per_mtok rates ÷ 1,000,000, rounded half-up)
discount_bps       = the single best discount that applies to you
                     (api_key > organization > model > global — not stacked)
discount_micro     = round(list_price_micro × discount_bps / 10,000)
charged_micro      = list_price_micro − discount_micro

charged_micro is what you see in usage.x_llm_cost_micro, the X-LLM-Cost-Micro header, cost_micro on jobs, and what is debited from your balance and counted against budgets.

Worked example

openai/gpt-4o-mini with input_per_mtok: 150000, output_per_mtok: 600000, discount_bps: 1000 (10 %). A request uses 2,000 prompt tokens and 500 completion tokens:

input   = 2000 × 150000 / 1e6 = 300 µ$
output  =  500 × 600000 / 1e6 = 300 µ$
list    = 600 µ$
discount= round(600 × 1000 / 10000) = 60 µ$
charged = 540 µ$  →  usage.x_llm_cost_micro = 540   ($0.00054)

const microToUsd = (m: number) => m / 1_000_000;
const estimate = (promptTokens: number, completionTokens: number, p: { input_per_mtok: number; output_per_mtok: number }, discountBps: number) => {
  const list = Math.round((promptTokens * p.input_per_mtok) / 1e6) + Math.round((completionTokens * p.output_per_mtok) / 1e6);
  return list - Math.round((list * discountBps) / 10_000);
};

Savings

The dashboard reports savings per request and in aggregate:

savings_micro = max(list_price_micro, list price of the most expensive eligible route for the same usage) − charged_micro   (floor 0)

In words: what you would have paid at the most expensive route that could have served the request, minus what you actually paid. Discounts always count as savings; routing to a cheaper route adds to them.

Estimates, reservations and settlement

Before a request runs, the gateway estimates its cost using the most expensive eligible route (conservative) and the estimated usage: ceil(chars / 4) input tokens (+1,000 per image), max_tokens (or the model default) output tokens, n images, or duration_seconds for media. That estimate is:

• checked against your balance, key budgets and organization limits (→ 402 if it does not fit),
• reserved for the duration of the request, then settled to the actual charge when the response completes (or the job finishes). Partial streams are settled to the tokens actually generated.

Async jobs reserve 1.5 × estimate unless you pass max_cost_micro; the difference is released on completion.

Adding credits

Credits are prepaid US dollars, debited per request at the charged amount above, and they never expire. Add them in Billing; how you can pay depends on your organization's billing country, which you set once in the dashboard:

There is no platform fee on a top-up, no subscription and no per-seat charge. Checkout is hosted by the payment provider; card numbers never touch OSMEXO. New organizations may buy up to $500 a day and $1,000 a month; ask from the Billing page to raise that. Unused credits are refundable within 30 days, see the refund policy.

A request that does not fit the remaining balance is rejected with 402 insufficient_credits before it runs, so a low balance never leaves you with a half-served request. See API Keys for the difference between running out of money and running into a rate limit.

Reading pricing from /v1/models

curl -s "https://api.osmexo.com/v1/models" -H "Authorization: Bearer $OSMEXO_API_KEY" \
  | jq '.data[] | {id, pricing, discount_bps, providers}'

{
  "id": "openai/gpt-4o-mini",
  "pricing": { "input_per_mtok": 150000, "output_per_mtok": 600000, "currency": "USD", "unit": "micro" },
  "discount_bps": 1000,
  "providers": 2
}

pricing is the list price for your organization (operators may set organization-specific prices). discount_bps already reflects the best discount available to your key. To show dollars, divide by 1,000,000 and format with up to 6 decimals for small amounts.