Conversation
Every one of the nine Mistral entries returned `400 invalid_model`, so the whole provider was dead for anyone with a Mistral key. The 2026-09-15 audit rewrote the working ids into a date-stamped form that La Plateforme does not accept (`mistral-medium-3-5` -> `mistral-medium-3-5-26-04`, `ministral-14b-2512` -> `ministral-3-14b-25-12`, and so on). Codestral was untouched by that audit, which is why it kept working on the same key. Re-verified every id against a live `GET https://api.mistral.ai/v1/models` on a real Experiment-plan key: Fixed (6): mistral-medium-3-5-26-04 -> mistral-medium-3-5 mistral-small-4-0-26-03 -> mistral-small-2603 ministral-3-14b-25-12 -> ministral-14b-2512 ministral-3-8b-25-12 -> ministral-8b-2512 ministral-3-3b-25-12 -> ministral-3b-2512 magistral-medium-1-2-25-09 -> magistral-medium-latest Removed (3): mistral-large-3-25-12 no `large` model exists in the live catalog zai-glm-5-2 absent from /v1/models; a direct call returns 403 tier_not_allowed (paid tier only), so it never belonged in a free catalog mistral-small-creative-25-12 absent from the live catalog Context windows now come from each model's `max_context_length` rather than a blanket 256k, which corrects ministral-3b-2512 from 256k to 128k (131072). After the fix, an FCM ping of the provider returns 200 for Ministral 3 14B/8B/3B and 429 (rate-limited free tier) for the rest - no 400s left. test/test.js: the temperature-clamp test pinned `mistral-large-3-25-12` with a comment saying it is a real catalog model; repointed at `mistral-medium-3-5`. npm test: 1154/1154 passing.
|
@Sy57em1 is attempting to deploy a commit to the vavanesssa Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
All nine Mistral entries in
sources.jsreturn400 invalid_model, so the whole provider is dead for anyone with a Mistral key.The 2026-09-15 audit rewrote the previously working ids into a date-stamped form that La Plateforme does not accept (
mistral-medium-3-5→mistral-medium-3-5-26-04,ministral-14b-2512→ministral-3-14b-25-12, and so on). Codestral was not touched by that audit, which is why it keeps working on the very same key — a useful signal that the key is fine and the ids are not.Fix
Every id re-verified against a live
GET https://api.mistral.ai/v1/modelson a real Experiment-plan key.Fixed (6):
mistral-medium-3-5-26-04mistral-medium-3-5mistral-small-4-0-26-03mistral-small-2603ministral-3-14b-25-12ministral-14b-2512ministral-3-8b-25-12ministral-8b-2512ministral-3-3b-25-12ministral-3b-2512magistral-medium-1-2-25-09magistral-medium-latestRemoved (3):
mistral-large-3-25-12— nolargemodel exists in the live catalog under any namezai-glm-5-2— absent from/v1/models; a direct call returns403 tier_not_allowed("This model is not available in your subscription tier"), so it does not belong in a free catalogmistral-small-creative-25-12— absent from the live catalogContext windows now come from each model's
max_context_lengthinstead of a blanket256k, which correctsministral-3b-2512from256kto128k(131072).Verification
Ping through FCM's own
ping()after the change — no400left:429means the id is valid and the model exists; the free tier was simply exhausted while verifying.npm test→ 1154/1154 passing.One test needed updating: the temperature-clamp test in
test/test.jspinnedmistral-large-3-25-12with a comment stating it is a real catalog model. Repointed atmistral-medium-3-5with a note explaining why.Notes
docs/providers.mdis generated byscripts/generate-provider-table.mjsand still shows the old counts — I left it alone so the regeneration stays a separate, reviewable change.