Model limit probe

Mistral: Devstral Medium | max output limit

Mistral: Devstral Medium max output limit decides whether a key can enter a production route. TestKey reads model ID mistralai/devstral-medium, provider Mistral AI, catalog context, real-key headers, 429 errors, and region signals together.

Model

mistralai/devstral-medium

Mistral: Devstral Medium

Provider

Mistral AI

25 models in catalog

Limit dimension

max output limit

max-output

Visible signal

partial catalog signal

Context window: 131,072

Limit matrix summary

Model

mistralai/devstral-medium

Limit dimension

max-output

Visible signal

partial catalog signal

Read-only check. Detection data burns after 5 minutes.

Why this limit matters

Mistral: Devstral Medium max output limit decides whether a key can enter a production route. TestKey reads model ID mistralai/devstral-medium, provider Mistral AI, catalog context, real-key headers, 429 errors, and region signals together.

Model: mistralai/devstral-medium
Provider: Mistral AI
Limit dimension: max output limit

How to prove it

Read-only check. Detection data burns after 5 minutes.

Start with the visible signal: partial catalog signal, then read headers and error bodies with read-only requests.
max output limit must bind model ID mistralai/devstral-medium; limits from another model at the same provider cannot be reused.
max output limit · partial catalog signal · 131,072

Operator action

Mistral: Devstral Medium max output limit is not just a number. It should become route throttling, sale tags, headroom alerts, fallback model suggestions, and price protection.

Read-only check. Detection data burns after 5 minutes.
Visible signal: partial catalog signal
Context window: 131,072

Open key checker

Read-only check. Detection data burns after 5 minutes.

Open models

Mistral: Devstral Medium

Open providers

Mistral AI