Solution skill
Mistral 401 is usually a wrong-workspace key, 429 is a tier RPM or TPM cap
Complete solution
Shows how to fix mistral 401 is usually a wrong-workspace key, 429 is a tier RPM or TPM cap. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
For Unknown model errors, copy the id from the models list rather than guessing the suffix. A 400 with Unknown model means the model id is wrong, usually a missing -latest suffix; the runbook recommends listing GET v1/models to see the exact ids available to your key.
Steps
- When Mistral returns 401, regenerate the key at the console and confirm it belongs to the right workspace before touching your code. On 429, respect the Retry-After header with exponential backoff and check your workspace limits, since the caps are per tier. For Unknown model errors, copy the id from the models list rather than guessing the suffix.
When to use
You are seeing this: When Mistral returns 401, regenerate the key at the console and confirm it belongs to the right workspace before touching your code. Use this skill when you run into "Mistral 401 is usually a wrong-workspace key, 429 is a tier RPM or TPM cap".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: A Mistral error runbook documents the three errors integrators hit most. A 401 means the API key is missing, expired, revoked, or from the wrong workspace. A 429 means the workspace exceeded its requests-per-minute or tokens-per-minute caps for its tier, with a Retry-After hint. A 400 with Unknown model means the model id is wrong, usually a missing -latest suffix; the runbook recommends listing GET v1/models to see the exact ids available to your key.
Verified resolution: When Mistral returns 401, regenerate the key at the console and confirm it belongs to the right workspace before touching your code. On 429, respect the Retry-After header with exponential backoff and check your workspace limits, since the caps are per tier. For Unknown model errors, copy the id from the models list rather than guessing the suffix.
Source URL: https://github.com/shaneholloman/skills-plus/blob/HEAD/skills/.curated/mistral-common-errors/SKILL.md
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_eYZxiFhGXhMcOY2PkZQVrA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Mistral 401 is usually a wrong-workspace key, 429 is a tier RPM or TPM cap <span>— Vectle</span></a>