Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Mistral API has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 3 scoped observations for Mistral API. The baseline covers current model context range, organization rate dimensions, admin limit visibility. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| current model context rangeInput and output tokens together count toward the model context window. | 128K or 256K tokens for documented current models | Model specific | Mistral AIAug 22, 2026 |
| organization rate dimensionsThe two dimensions are enforced independently and 429 is returned when exceeded. | Requests/second and tokens/minute vary by tier and model | Per organization | Mistral AIAug 22, 2026 |
| admin limit visibilityAn admin API key is required to read organization rate and spend contexts. | RPS plus per-model TPM and monthly token limits | Admin API beta | Mistral AIAug 22, 2026 |
Tracked constraints and impact
Model context windows, independent request/token limits, and organization controls. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
Mistral API Context Windows by Model
Mistral API Context Windows by Model, verified against Mistral API's official documentation with scope, implementation impact, caveats, and a direct check.
Mistral API Rate Limits
Mistral API Rate Limits, verified against Mistral API's official documentation with scope, implementation impact, caveats, and a direct check.
Mistral Admin Rate & Spend Limit API
Mistral Admin Rate & Spend Limit API, verified against Mistral API's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Mistral API baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Context windows, rate-limit dimensions, and error behavior
Organization rate and spend limit API