Route to high-throughput provider instances by appending the :nitro suffix for maximum token generation speed.
Not yet available.
The :nitro variant routes your request to provider instances reserved for high-throughput workloads — dedicated capacity with lower queuing and faster token generation. Use it when speed matters more than cost: real-time applications, latency-sensitive pipelines, or interactive experiences where a slow response breaks the user experience.
Appending :nitro to a model slug tells OpenDunes to route exclusively to providers and instances flagged for high throughput. In practice this means:
The model itself is unchanged — you get the same weights, capabilities, and context limits as the standard variant. Only the infrastructure running it is different.
| Use case | Use nitro? |
|---|---|
| Interactive chat UI with real-time response | Yes |
| Batch processing overnight | No — standard or :free is cheaper |
| Time-sensitive pipelines (< 2s SLA) | Yes |
| Background summarization or classification | No |
| Demos and live presentations | Yes |
Nitro requests are billed at a higher per-token DA rate than the standard variant. The premium varies by model — check the catalog:
The response includes pricing.nitro as a separate input/output rate in DA per million tokens. For cost-sensitive workloads, compare the nitro premium against the value of the latency improvement before adopting it at scale.
The :nitro variant prioritizes your request, but does not guarantee a specific tokens/second SLA — provider capacity fluctuates. For strict SLA requirements, contact support about reserved capacity arrangements.
Note. Combining
:nitrowith other variants (e.g.,model:nitro:thinking) is not supported. Each request uses one variant suffix. If you need both high throughput and extended reasoning, contact support.