What the family record covers
Mistral's official model catalog lists Mistral Large 3 among its generalist models and labels it as open weight and multimodal. The catalog also contains separate coding, reasoning, small, audio, and other specialized models.
The model name alone does not resolve whether a team uses Mistral-hosted access, a cloud partner, or a self-managed checkpoint. Those deployment choices should remain visible in every evaluation record.
Documented access paths
- Mistral's documented platform and API surfaces
- Open-weight deployment under the model's applicable license and release materials
- Third-party hosting should be recorded as a distinct operating condition
Capabilities to verify
- Text and visual input handling for the selected endpoint or checkpoint
- Structured output and tool integration on representative business tasks
- Serving cost, latency, and failure recovery on the chosen infrastructure
- Operational differences between hosted and self-managed access
Decision questions
- Is hosted access or open-weight deployment the primary requirement?
- Which exact version, endpoint, and serving configuration will be pinned?
- Would a specialized Mistral model be a better fit than the general-purpose family?
Evaluation cautions
- Open-weight availability does not make hosted and self-hosted results equivalent.
- The live catalog can change; confirm identifiers, lifecycle, license, and limits before adoption.
- Provider descriptions must be validated on the team's own task distribution.
Related decisions
Move from a family name to the product, provider, workflow, comparison, or protocol that defines the real choice.
Sources checked
Open the original pages before relying on a time-sensitive product decision.