Add support for MiniMax-M2.1 and MiniMax-M2.1-lightining

[Sameerlite]

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

🆕 New Feature

Changes

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
litellm	Error		Feb 12, 2026 4:22pm

[greptile-apps]

Greptile Overview

Greptile Summary

Adds model pricing entries for MiniMax-M2.5 and MiniMax-M2.5-lightning to the model registry, along with a new blog post documenting Day 0 support. The JSON model entries follow the existing MiniMax-M2 pattern and look correct.

• PR title mismatch: The PR title references "M2.1" and "M2.1-lightining" (with a typo), but the actual models added are MiniMax-M2.5 and MiniMax-M2.5-lightning. The title should be corrected.
• No tests included: The pre-submission checklist requires at least 1 test in tests/litellm/, but no tests were added in this PR.
• Blog post formatting bug: The Docker pull code block has a broken closing fence (line 48) that will cause rendering issues.
• The model pricing JSON changes are straightforward additions and both the primary and backup files are kept in sync.

Confidence Score: 3/5

• Low-risk config and docs changes, but missing required tests and the PR title is incorrect.
• The JSON model entries are straightforward additions that follow established patterns and are unlikely to break anything. However, the PR has no tests (required by contribution guidelines), the PR title references wrong model names ("M2.1" vs "M2.5"), and the blog post has a broken markdown code block. These issues prevent a higher confidence score.
• docs/my-website/blog/minimax_m2_5/index.md has a broken code block that needs fixing.

Important Files Changed

Filename	Overview
docs/my-website/blog/minimax_m2_5/index.md	New blog post for MiniMax-M2.5 Day 0 support. Contains a broken markdown code block (closing fence on same line as command). PR title says "M2.1" but content references "M2.5".
model_prices_and_context_window.json	Adds MiniMax-M2.5 and MiniMax-M2.5-lightning model entries with pricing, context window, and feature flags. Entries are consistent with existing MiniMax-M2 pattern.
litellm/model_prices_and_context_window_backup.json	Backup copy of model_prices JSON with identical MiniMax-M2.5 and MiniMax-M2.5-lightning entries. Stays in sync with the primary file.

[greptile-apps]

_{3 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}