What this error usually means
Diagnose Mistral AI revoked key (401) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
- Provider: Mistral AI
- Error type: revoked key
- Status code: 401
Key error diagnosis
Mistral AI | revoked key
Diagnose Mistral AI revoked key (401) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
Provider
Mistral AI
global provider route
Error type
revoked key
high
Status code
401
revoked-key
Sample models
25
Codestral 2508 · Devstral 2 2512 · Devstral Medium
Error route summary
Error type
revoked-key
high
Provider
Mistral AI
Status code
401
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.
How to prove it during checking
Read-only check. Detection data burns after 5 minutes.
- Run read-only identity first: confirm whether the key really belongs to Mistral AI, not just a compatible protocol.
- Then list models or run a lightweight probe: check whether models like Codestral 2508 · Devstral 2 2512 · Devstral Medium are visible and return stable evidence.
- Finally record 401, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.
Next action
revoked key should not only show failed. The console should return the next move: refill balance, change Base URL, switch model, add permission, change egress IP, hold listing, or monitor.
- Read-only check. Detection data burns after 5 minutes.
- global provider route
- Codestral 2508 · Devstral 2 2512 · Devstral Medium
Open key check
Read-only check. Detection data burns after 5 minutes.
Open providers
Mistral AI
Open models
Codestral 2508 · Devstral 2 2512 · Devstral Medium
Return to Codestral 2508
After clarifying this error, jump back to the newest model and decide whether the failure changes how far you keep following it.