LTX-2.5 Pro · Quote

Select a provider to see its effective parameter limits. Automatic routing chooses a provider that supports your input. Examples include defaults and required inputs; replace example media URLs with accessible files.

Before calculating: prepare inputs and select a price

Prepare input: billing.version=1 is the current calculation contract; a nonempty billing.unavailableReason prevents quoting. Validate model input against billing.modelParams, then validate and apply defaults using the channel’s params types, required, default, options and min/max constraints. If billing.upstreamParams exists, its validated input and defaults are final. Ignore a field unsupported by the channel or upstream only when its value equals the model default; otherwise reject it. Derive mode as image or text from whether image/images fields in the final parameter definitions have a value; do not trust a user-supplied mode.

For request, second, image and character billing, match every prices[].conditions entry against the final input, comparing values as strings. Choose the matching rule with the most conditions; keep response order for ties. For tokens, use the input-length tiers below.

Per request (request)

Quantity is 1 per request. Total micro-USD = round(priceMicros × 1), independent of duration or image count. Example: a unit price of 20,000 micro-USD costs $0.02 per request.

Per second (second)

Use input.duration after applying defaults, with a minimum of 1. If neither the input nor the model provides a value, use 1. Total micro-USD = round(priceMicros × seconds). Example: 50,000 micro-USD per second for 8 seconds costs $0.40. Duration must still satisfy the model’s constraints.

Per image (image)

Use input.num_images after applying defaults, with a minimum of 1. If neither the input nor the model provides a value, use 1. Total micro-USD = round(priceMicros × image count). Example: 30,000 micro-USD per image for 4 images costs $0.12. The count must still satisfy the model’s constraints.

Per character count (kchar)

The unit price covers 1,000 characters. By default, count input.prompt using JavaScript string length, not bytes; some emoji count as 2. With billing.characterBilling, sum the string lengths of fields, round up to a multiple of block when configured, then apply minimum. The final count is at least 1 character.

Quantity = billable characters / 1,000; total micro-USD = round(priceMicros × quantity). Example: 1,200 characters with block=1,000 and minimum=1,000 bills 2,000 characters. At 100,000 micro-USD per thousand, the total is $0.20. Without block, do not round up to whole thousands.

Per token (input_token / output_token)

Input and output have separate prices, each per 1,000,000 tokens. For each unit, choose the highest min_input_tokens threshold reached by the input token count; an omitted threshold is 0, and ties keep response order. The output price tier also depends on the input count.

Total micro-USD = ceil(input price × input tokens / 1,000,000 + output price × output tokens / 1,000,000). Add both costs before rounding up. Example: input price 1,000,000 and output price 2,000,000 micro-USD, with 1,000 input and 500 output tokens, costs $0.002. Token counts are not character counts; unknown output usage is only an estimate.

Audio reservation: when billing.metering exists, estimate input tokens as the UTF-8 byte length of prompt concatenated with style_instructions plus 256, and use outputTokenHold for output tokens. Apply the token formula to reserve funds. Final settlement uses actual usage; providerCost=true requires the provider’s cost report.

Convert totals to dollars and credits

Above, round means rounding to integer micro-USD with Math.round; ceil means rounding up with Math.ceil. Dollars = total micro-USD / 1,000,000. When billing.creditsPerUsd is non-null, credits = max(1, ceil(dollars × creditsPerUsd - 1e-9)). The minimum is 1 credit; subtracting 1e-9 avoids extra credits from floating-point error. Example: $0.40 at 250 credits per dollar is 100 credits.

Project prices and estimate validity

Project prices: billing.priceScope=project means unit prices already include the resale ratio; do not apply it again. billing.creditsPerUsd=null, so these prices cannot determine gateway credits. POST /quote returns gateway prices and credits even with project supplied; it excludes project resale markup.

Consistency: these rules match backend calculations for the same price configuration, pinned provider and input. Catalogs are cached for 60 seconds; refresh after price changes. Frontend estimates do not lock prices. Routing also considers availability, priority and circuit breakers, so a local minimum is not a guaranteed charge. Invalid input, unsupported versions or missing prices must show an unavailable quote, not a free price.