[Alan-Billi]

Summary

Closes #16676. Opened as a draft until the issue is assigned.

mistral-large-2512 (Mistral Large 3) has no entry in tokenValues, so findMatchingPattern falls back to the generic mistral-large key and bills it at Mistral Large 2 rates ($2 / $6 per MTok). Mistral Large 3 is priced at $0.50 / $1.50, so its transactions — and any spend reporting built on them — are overstated 4x. mistral-large-latest now resolves to Large 3 as well.

Changes in packages/data-schemas/src/methods/tx.ts:

• Add mistral-large-2512 and mistral-large-3 at $0.50 / $1.50.
• Point the generic mistral-large fallback (used by mistral-large-latest) to the current model's price.
• Pin mistral-large-2411 (Large 2.1) to its $2 / $6 rate so it keeps its existing pricing.
• Remove the Sonnet 5 "introductory pricing through 2026-08-31; revert to $3 / $15 after" comments. Anthropic made $2 / $10 the standard price and the scheduled increase will not occur (pricing, footnote 3), so the comments would invite an incorrect revert. Rates are unchanged.

Pricing sources: Mistral Large 3 2512 on OpenRouter, Anthropic pricing.

Change Type

• Bug fix (non-breaking change which fixes an issue)

Testing

Added a Mistral Large Pricing suite to tx.spec.ts covering mistral-large-2512, mistral-large-3, mistral-large-latest and a provider-prefixed name ($0.50 / $1.50), mistral-large-2411 ($2 / $6), and the legacy 2402 / 2407 Bedrock rates.

cd packages/data-schemas && npx jest src/methods/tx.spec.ts

Test Configuration:

What was run, and what was not:

• Ran: npx jest src/methods/tx.spec.ts in packages/data-schemas, on Node v24, against a dependency install older than current upstream. Result: all 3 new tests pass. 9 pre-existing tests fail (getValueKey / getMultiplier GPT cases such as "should return "4k" for model name containing "gpt-3.5""). The same 9 fail on unmodified upstream with that install, so they come from the stale dependencies, not this change.
• Ran: npx prettier --check on both files: clean.
• Not run: npm run test:api, npm run lint, npm run static-checks, and a clean reinstall.

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes (only tx.spec.ts was run; see Testing)

🤖 Generated with Claude Code

[github-actions]

👋 Thanks for the contribution! LibreChat merges all changes into dev first — main only moves at release time — so this pull request's base branch was switched from main to dev automatically.

Nothing is needed from you; your commits, reviews and discussion are unchanged. If the diff now shows files you did not touch, rebase onto dev:

git remote add upstream https://github.com/LibreChat-AI/LibreChat.git
git fetch upstream dev
git rebase upstream/dev
git push --force-with-lease

Maintainers: apply the target: main label and restore the base branch if this one genuinely belongs on main.