What affects cost
- Selected Mistral model and service
- Input and output token volume
- Cached versus uncached repeated context
- Synchronous versus Batch processing
- OCR, audio, fine-tuning, or dedicated deployment units
Mistral API pricing separates standard input and output tokens from cached-input and Batch processing discounts.
Usage-based per-model token pricing with documented Batch and cached-input discounts; other products and deployment modes use separate terms.
Example cost uses 1,000,000 input tokens and 300,000 output tokens at each model's default tracked rate, with no cache discount.
| Model | Input price | Cached input | Output price | Context | Example cost |
|---|---|---|---|---|---|
| Mistral Medium 3.5 Stable | $1.50 / 1M | $0.15 / 1M | $7.50 / 1M | 256K tokens | $3.75 |
Cost boundary: this example compares token charges only. It does not assume equal output quality, latency, retry rates, or output length across models.
Text-model usage is generally billed per million input and output tokens, with separate discounts or units for caching, Batch, OCR, audio, fine-tuning, and deployment products.
No. Batch is intended for asynchronous processing. Real-time requests should be budgeted using the applicable standard model rate.