Adjust input and output cost per token for mistral-small-2503

[jinskjoy]

Cost per million for mistral-small-2503 is not correct.

In Azure Documentation:
https://ai.azure.com/explore/models/mistral-small-2503/version/1/registry/azureml-mistral?tid=61386482-660c-45b0-9b6b-7b1e9c868281
Pay-as-you-go (per 1,000 tokens)
$0.0001
Model input
$0.0003
Model output

Relevant issues

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🐛 Bug Fix

Changes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Feb 25, 2026 1:06pm

[greptile-apps]

Greptile Summary

This PR corrects the pricing for azure_ai/mistral-small-2503 in the backup pricing JSON, reducing both input and output cost per token by 10x to match Azure's documented rates ($0.0001/1K input, $0.0003/1K output).

• The price correction (1e-06 → 1e-07 input, 3e-06 → 3e-07 output) is mathematically correct and consistent with the same model's pricing on other providers (e.g., mistral/mistral-small, openrouter/mistralai/mistral-small-3.1-24b-instruct, watsonx/mistralai/mistral-small-2503).
• Issue: Only model_prices_and_context_window_backup.json was updated. The primary file model_prices_and_context_window.json still has the old incorrect prices and should also be updated.
• No tests are included, though this is a data-only change to a JSON configuration file.

Confidence Score: 3/5

• The pricing correction itself is valid, but the primary pricing file was not updated, which may leave the bug unfixed.
• Score of 3 reflects that the change is correct in isolation but incomplete — only the backup pricing JSON was updated while the primary model_prices_and_context_window.json still has the old incorrect values. This means the fix may not actually take effect at runtime.
• model_prices_and_context_window.json needs the same price update applied to azure_ai/mistral-small-2503.

Important Files Changed

Filename	Overview
litellm/model_prices_and_context_window_backup.json	Corrects azure_ai/mistral-small-2503 pricing from 1e-06/3e-06 to 1e-07/3e-07 per token (input/output), matching Azure documentation. The math is correct and consistent with other mistral-small model entries in the file.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["azure_ai/mistral-small-2503 pricing lookup"] --> B{"Which file is loaded?"}
    B -->|"model_prices_and_context_window.json<br/>(primary)"| C["input: 1e-06 ❌<br/>output: 3e-06 ❌<br/>(NOT updated by this PR)"]
    B -->|"model_prices_and_context_window_backup.json<br/>(backup)"| D["input: 1e-07 ✅<br/>output: 3e-07 ✅<br/>(updated by this PR)"]
    C --> E["Costs reported 10x too high"]
    D --> F["Costs match Azure documentation"]

Loading

_{Last reviewed commit: 939fe80}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[ghost]

Review

1. Does this PR fix the issue it describes?
Yes. The PR correctly updates mistral-small-2503 pricing to match Azure's documented rates:

• Input: $0.0001/1K tokens → $0.1/1M tokens
• Output: $0.0003/1K tokens → $0.3/1M tokens

The changes in both model_prices_and_context_window.json and the backup file are consistent.

2. Has this issue already been solved elsewhere?
No. Checked the pricing files — this is the only place where mistral-small-2503 costs are defined. No duplicate entries.

✅ Ready to merge — straightforward pricing fix with clear Azure documentation as source.