DeepSeek vs MiniMax: Which Open-Weight MoE Wins in 2026?

If you are picking between two Chinese AI labs’ open-weight models for a coding agent or a high-volume API workload, the deepseek vs minimax decision usually comes down to four things: cost per million tokens, coding benchmarks, context window, and licence terms. Both lineups have moved on since the spring. DeepSeek’s API now serves deepseek-flash (DeepSeek-V4.1-Flash-1017, released 17 October 2026) and deepseek-v4-pro (DeepSeek-V4-Pro-0813, released 13 August 2026). MiniMax’s API platform now lists two language models, MiniMax-M3.1-Flash and MiniMax-M3, and says its M2.5 and M2.7 families stopped accepting new users on 19 October 2026 and will be retired on 18 November 2026. This article gives you the numbers, a worked cost example and a pick for each scenario.
The verdict up front

At the budget tier the two are now neck and neck. MiniMax-M3.1-Flash lists $0.15 input / $0.60 output per 1M tokens at all hours; deepseek-flash lists $0.30 / $1.20 at peak and exactly $0.15 / $0.60 off-peak, with much cheaper cache hits ($0.006 peak / $0.003 off-peak against MiniMax’s $0.015). So MiniMax is cheaper if your traffic runs in DeepSeek’s peak hours; DeepSeek is slightly cheaper off-peak and on cache-heavy prompts. Both have a 1M-token context and accept images; MiniMax-M3.1-Flash also accepts video.
The bigger differences are elsewhere. Pick DeepSeek if you want MIT-licensed weights with no commercial conditions, a non-thinking mode for latency-sensitive calls, and a second, larger model (DeepSeek V4-Pro) on the same API. Pick MiniMax if you want video input, MiniMax’s coding-tool plans (it documents setups for Claude Code, Codex, Cursor, OpenCode and others), or a platform whose privacy policy says personal data is stored in the United States rather than China.
At-a-glance comparison
Figures from DeepSeek’s pricing page, MiniMax’s pricing overview and model list, and the model cards, checked 26 October 2026. Prices are USD per 1M tokens.
| Feature | deepseek-flash |
deepseek-v4-pro |
MiniMax-M3.1-Flash | MiniMax-M3 |
|---|---|---|---|---|
| Model | DeepSeek-V4.1-Flash-1017 | DeepSeek-V4-Pro-0813 | ~428B total / 23B active, per its card | ~428B / ~23B active, per its card |
| Context window | 1,000,000 | 1,000,000 | 1,000,000 | 1,000,000 |
| Inputs | Text, images | Text | Text, images, video | Text, images, video |
| Input (cache miss) $/M | $0.30 peak / $0.15 off-peak | $1.32 peak / $0.66 off-peak | $0.15 | $0.30 (up to 512K input) |
| Input (cache hit) $/M | $0.006 peak / $0.003 off-peak | $0.044 peak / $0.022 off-peak | $0.015 | $0.06 |
| Output $/M | $1.20 peak / $0.60 off-peak | $3.96 peak / $1.98 off-peak | $0.60 | $1.20 |
| Weights licence | MIT | MIT | MiniMax Community License | MiniMax Community License |
MiniMax shows its MiniMax-M3 standard prices as a “Permanent 50% off” the original $0.60 / $2.40, and charges double ($0.60 / $2.40) for requests over 512K input tokens; a Priority tier costs 1.5× standard. DeepSeek’s rates do not change with prompt length. DeepSeek’s maximum output is 384,000 tokens on both models.
Coding
This is where the comparison gets interesting, and MiniMax publishes the head-to-head. The MiniMax-M3.1-Flash model card compares it directly with DeepSeek-V4.1-Flash-1017 (MiniMax-reported; the DeepSeek coding figures match DeepSeek’s own V4.1-Flash-1017 card):
| Benchmark (M3.1-Flash card, MiniMax-reported) | MiniMax-M3.1-Flash | DeepSeek-V4.1-Flash-1017 |
|---|---|---|
| DeepSWE v1.1 | 73.7 | 77.0 |
| Terminal Bench 4.0 | 38.1 | 42.3 |
| NL2Repo-Bench | 61.2 | 68.2 |
| Automation-Bench v1.0.6 | 62.8 | 60.5 |
| HLE (without tools, text-only) | 43.4 | 42.6 |
On MiniMax’s own table, DeepSeek-V4.1-Flash-1017 leads the three coding benchmarks and MiniMax-M3.1-Flash leads Automation-Bench and, narrowly, HLE. DeepSeek’s own card lists 42.6 on full HLE without tools and 44.0 on the text-only subset, so that row is not like-for-like. MiniMax also reports results where it gives no DeepSeek figure, such as 82.2 on CyberGym and 76.2 on BankerToolBench. MiniMax lists mini-SWE-agent for DeepSWE v1.1 and Codex for Terminal Bench 4.0, while DeepSeek’s card says its figures used the Mini-SWE-V2 and Claude Code harnesses; scores in other harnesses will differ.
For coding workflows, see the DeepSeek for coding walkthrough or the DeepSeek Coder vs Copilot comparison.
Practical coding pick
- Coding benchmarks on the budget tier:
deepseek-flash, which leads MiniMax-M3.1-Flash on DeepSWE v1.1, Terminal Bench 4.0 and NL2Repo-Bench in MiniMax’s own table. - Agentic loops in coding tools: either. DeepSeek’s API docs list integration guides for tools such as Claude Code, OpenCode and GitHub Copilot; MiniMax documents its M Plan for MiniMax Code, Claude Code, Codex, Cursor, OpenCode and others. MiniMax recommends
temperature=1.0andtop_p=0.95for M3.1-Flash. - Cost-sensitive bulk code review: MiniMax-M3.1-Flash during DeepSeek’s peak hours;
deepseek-flashoff-peak, especially with long cached prefixes.
Reasoning and thinking modes
Both labs ship reasoning capability, and the API ergonomics are now similar.
DeepSeek puts thinking behind request parameters on both models: it is on by default (effort high), you can set reasoning_effort to "low", "high" or "max", and you can opt out with extra_body={"thinking": {"type": "disabled"}}. The response returns reasoning_content alongside the final content. No separate model ID, no version juggling.
MiniMax’s model-invocation guide says MiniMax-M3.1-Flash thinks before it answers by default, with an effort setting of low, medium, high, xhigh or max (default max). On its OpenAI-compatible protocol, thinking comes back in reasoning_content and content holds only the final answer; on its Anthropic-compatible protocol it comes back as thinking content blocks. MiniMax’s guide says thinking cannot be turned off on MiniMax-M3.1-Flash (sending thinking: {"type": "disabled"} returns a 400 error) and suggests lowering effort instead; its API reference says MiniMax-M3 skips thinking when it is disabled.
For more on DeepSeek’s reasoning lineage, the DeepSeek R1 page covers the original step-by-step reasoning release.
Writing and general chat
For long-form writing, customer support, summarisation and translation, the deciding factors are price, context and output length:
- Cost. MiniMax-M3.1-Flash’s $0.15 / $0.60 matches
deepseek-flash’s off-peak rate at all hours; at peak DeepSeek costs twice as much. - Context. Both now accept 1M tokens, enough for whole-document summarisation or long RAG passes; see building a DeepSeek RAG pipeline for setup.
- Output ceiling. DeepSeek allows up to 384K output tokens in one call, which helps with very long drafts.
If you skip thinking for short chat replies, DeepSeek’s non-thinking mode keeps output tokens, and so cost, down. If your team runs content creation workflows, test both on your own prompts.
Pricing — worked example
Cost comparisons fail when articles quote a single rate. The honest version enumerates all three token buckets. Here is a representative workload: 1,000,000 API calls, each with a 2,000-token system prompt (cached across calls), a 200-token user message (uncached) and a 300-token response, which is 2,000M cached input tokens, 200M uncached input tokens and 300M output tokens.
DeepSeek deepseek-flash
PEAK OFF-PEAK
Cached input : 2,000M × $0.006/M = $12.00 × $0.003/M = $6.00
Uncached input : 200M × $0.30/M = $60.00 × $0.15/M = $30.00
Output : 300M × $1.20/M = $360.00 × $0.60/M = $180.00
------- -------
Total $432.00 $216.00
MiniMax-M3.1-Flash and MiniMax-M3 (MiniMax pricing page)
MiniMax-M3.1-Flash
Cached input : 2,000M × $0.015/M = $30.00
Uncached input : 200M × $0.15/M = $30.00
Output : 300M × $0.60/M = $180.00
-------
Total $240.00
MiniMax-M3 (standard, up to 512K input)
Cached input : 2,000M × $0.06/M = $120.00
Uncached input : 200M × $0.30/M = $60.00
Output : 300M × $1.20/M = $360.00
-------
Total $540.00
DeepSeek deepseek-v4-pro
PEAK OFF-PEAK
Cached input : 2,000M × $0.044/M = $88.00 × $0.022/M = $44.00
Uncached input : 200M × $1.32/M = $264.00 × $0.66/M = $132.00
Output : 300M × $3.96/M = $1,188.00 × $1.98/M = $594.00
--------- -------
Total $1,540.00 $770.00
For this workload, deepseek-flash run entirely at peak ($432) costs 1.8× MiniMax-M3.1-Flash ($240), while deepseek-flash run entirely off-peak ($216) is about 10% cheaper than MiniMax-M3.1-Flash. deepseek-v4-pro costs about 2.9× MiniMax-M3 at peak ($1,540 vs $540) and about 1.4× off-peak ($770). A real workload usually straddles DeepSeek’s two periods, so your DeepSeek bill lands between those totals. Use the DeepSeek pricing calculator to plug in your own ratios.
API access and developer ergonomics
Both providers expose OpenAI-compatible HTTP APIs. DeepSeek’s chat requests go to POST /chat/completions at https://api.deepseek.com; DeepSeek also accepts the Anthropic API format at https://api.deepseek.com/anthropic and the OpenAI Responses API format. The API is stateless: clients must resend the full conversation history with every request.
A minimal DeepSeek call in Python:
import os
from openai import OpenAI
client = OpenAI(
api_key=os.environ.get("DEEPSEEK_API_KEY"),
base_url="https://api.deepseek.com",
)
resp = client.chat.completions.create(
model="deepseek-flash",
messages=[{"role": "user", "content": "Summarise the migration plan."}],
reasoning_effort="high",
extra_body={"thinking": {"type": "enabled"}},
max_tokens=1024,
)
print(resp.choices[0].message.reasoning_content) # reasoning_content
print(resp.choices[0].message.content) # the final answer
To skip thinking for a quick reply, pass extra_body={"thinking": {"type": "disabled"}} instead. See the DeepSeek OpenAI SDK compatibility notes for the full surface.
MiniMax’s API docs give an OpenAI-compatible base URL of https://api.minimax.io/v1 and an Anthropic-compatible one of https://api.minimax.io/anthropic, and also document an OpenAI Responses-compatible endpoint. For self-hosting, the MiniMax-M3.1-Flash card recommends SGLang, vLLM and TokenSpeed, and includes a DSpark speculative-decoding draft head. DeepSeek’s current weights are large too: about 893 GB for DeepSeek-V4-Pro-0813 and about 510 GB for DeepSeek-V4.1-Flash-1017 on Hugging Face.
Developer features worth comparing:
- JSON mode: DeepSeek supports it; it is designed (not guaranteed) to return valid JSON, with the documented caveat that prompts include the word “json” plus an example schema and that
max_tokensis set high enough to avoid truncation. - Tool calling / function calling: both providers support it in OpenAI-compatible format.
- Streaming: both support SSE, and both return thinking in a separate
reasoning_contentfield on the OpenAI-compatible protocol. - Context caching: both bill cache hits at a lower rate. On
deepseek-flasha cache hit costs 2% of the cache-miss rate; on MiniMax-M3.1-Flash a cache read costs 10% of the input rate. - FIM completion (Beta): DeepSeek supports it in non-thinking mode only.
Privacy and ecosystem
The two platforms handle data differently. DeepSeek’s Privacy Policy (last updated 10 February 2026) says it collects, processes and stores personal data in the People’s Republic of China; see the DeepSeek privacy guide for a longer treatment. MiniMax’s API platform privacy policy names Nanonoble Pte. Ltd. in Singapore as the operator and says personal data is stored in a data centre in the United States. The strongest mitigation is the same for both: self-host the open weights.
Licences differ more than the old “MIT vs Modified-MIT” framing suggests. DeepSeek-V4.1-Flash-1017 and DeepSeek-V4-Pro-0813 ship under MIT for both code and weights. MiniMax-M3.1-Flash and MiniMax-M3 ship under the MiniMax Community License, which grants rights for non-commercial use; commercial use requires displaying “Built with MiniMax M3.1-Flash” (“Built with MiniMax M3” for M3) and notifying MiniMax, with prior written authorisation above US$20 million in yearly revenue, and the licence lists prohibited uses, including military purposes. Read the licence before you commit.
Ecosystem-wise, both lean on coding tools. DeepSeek’s API docs list guides for tools such as Claude Code, Codex, OpenCode and GitHub Copilot. MiniMax sells subscription plans (M Plan and Token Plan) with setup guides for MiniMax Code, Claude Code, Codex, Cursor, OpenCode, OpenClaw and others, and says M Plan and Token Plan requests to the retiring M2.5 and M2.7 names are now routed to M3.1-Flash.
When to pick which

A clear decision rule beats a benchmark table:
- Pick
deepseek-flashif your workload can run off-peak or reuses long cached prefixes, you want the stronger coding scores in MiniMax’s own comparison, or you need MIT-licensed weights. - Pick
deepseek-v4-proif you want DeepSeek’s second current model with the 1M context and up to 384K output, at $3.96 / $1.98 per 1M output tokens (peak / off-peak). - Pick MiniMax-M3.1-Flash if your traffic is concentrated in DeepSeek’s peak hours, you need video input, or you want MiniMax’s coding-tool plans.
- Pick MiniMax-M3 if you need a MiniMax model with a non-thinking mode or the Priority tier, or have a reason to stay on the earlier M3 release; at $0.30 / $1.20 it costs more than M3.1-Flash, which MiniMax builds on M3.
Alternatives worth considering
Neither model is the only Chinese open-weight option. DeepSeek vs Qwen covers Alibaba’s family; DeepSeek vs Kimi compares against Moonshot AI’s Kimi K3 line. For a wider survey, see our best Chinese AI models roundup and the broader AI comparison hub.
Is DeepSeek cheaper than MiniMax?
It depends on the hour. deepseek-flash lists $0.30 input (cache miss) / $1.20 output per 1M tokens at peak and $0.15 / $0.60 off-peak; MiniMax-M3.1-Flash lists $0.15 / $0.60 at all hours. So MiniMax is cheaper at peak, the two match off-peak, and DeepSeek’s cheaper cache hits tip cache-heavy workloads its way: in our worked example, $432 (peak) or $216 (off-peak) for deepseek-flash against $240 for MiniMax-M3.1-Flash. See the DeepSeek API pricing guide for the full rate card.
Which is better for coding agents, DeepSeek or MiniMax?
On MiniMax’s own MiniMax-M3.1-Flash model card, DeepSeek-V4.1-Flash-1017 scores higher on DeepSWE v1.1 (77.0 vs 73.7), Terminal Bench 4.0 (42.3 vs 38.1) and NL2Repo-Bench (68.2 vs 61.2), while M3.1-Flash leads Automation-Bench v1.0.6 (62.8 vs 60.5). Both work with common coding tools through OpenAI- and Anthropic-compatible APIs. Price, licence and data location are likely to decide it. Compare against DeepSeek vs Claude.
How do DeepSeek and MiniMax differ on context window?
Not at all on input any more: deepseek-flash, deepseek-v4-pro, MiniMax-M3.1-Flash and MiniMax-M3 all support up to 1,000,000 tokens. DeepSeek documents up to 384,000 output tokens. MiniMax-M3 charges double for requests over 512K input tokens, while DeepSeek’s rates do not depend on prompt length. The earlier MiniMax-M2.5, now being retired, had a 196,608-token context. For sizing, see DeepSeek token limits.
Are both DeepSeek and MiniMax open source?
Both ship open weights, but under very different licences. DeepSeek-V4.1-Flash-1017 and DeepSeek-V4-Pro-0813 release code and weights under MIT. MiniMax-M3.1-Flash and MiniMax-M3 use the MiniMax Community License, which covers non-commercial use and adds attribution, notice and (above US$20 million in yearly revenue) authorisation requirements for commercial use. Both can be self-hosted; DeepSeek’s V4-Pro-0813 card and MiniMax’s M3.1-Flash card both link vLLM recipes. More on the topic in is DeepSeek open source.
Can I use the OpenAI SDK with both DeepSeek and MiniMax?
Yes. DeepSeek’s API is OpenAI-compatible at https://api.deepseek.com and accepts the Anthropic SDK at https://api.deepseek.com/anthropic. MiniMax documents an OpenAI-compatible base URL of https://api.minimax.io/v1 and an Anthropic-compatible one of https://api.minimax.io/anthropic. In both cases, switching providers is mostly a base_url, api_key and model change; check each provider’s reasoning fields. Step-by-step setup is in the DeepSeek API getting started tutorial.
Sources & Methodology
Primary sources
- OfficialDeepSeek API documentationEndpoints, request/response shape, model IDsLast checked: October 26, 2026
- Model cardDeepSeek on Hugging FaceWeights, license, usage notes per modelLast checked: October 26, 2026
- RepositoryDeepSeek-AI on GitHubOpen-weight release details, training/inference notesLast checked: October 26, 2026
- PricingAnthropic Claude pricingClaude API rates for cross-vendor comparisonsLast checked: October 26, 2026
- PricingOpenAI API pricingOpenAI API rates for cross-vendor comparisonsLast checked: October 26, 2026
- PricingDeepSeek pricing pagedeepseek-flash / deepseek-v4-pro peak and off-peak rates, context, max outputLast checked: October 26, 2026
- PricingMiniMax pricing overviewMiniMax-M3.1-Flash and MiniMax-M3 rates, 512K tier, Priority tier (checked 26 Oct 2026)Last checked: October 26, 2026
- Official documentationMiniMax model listCurrent LLMs; M2.5/M2.7 closed to new users 19 Oct 2026, retired 18 Nov 2026Last checked: October 26, 2026
- Model cardMiniMax-M3.1-Flash model card~428B / 23B, text/image/video, 1M context, MiniMax-reported benchmarks vs DeepSeek-V4.1-Flash-1017, licenceLast checked: October 26, 2026
Technical references
- Technical reportDeepSeek-R1 paper (arXiv:2501.12948)R1 reasoning approach, distillation resultsLast checked: October 26, 2026
- Official documentationMiniMax docs: Model invocationThinking on by default, effort levels, reasoning_content on the OpenAI protocolLast checked: October 26, 2026
- Official documentationMiniMax docs: OpenAI SDKBase URLs https://api.minimax.io/v1 and /anthropicLast checked: October 26, 2026
- Model cardDeepSeek-V4.1-Flash-1017 model cardDeepSeek-reported benchmark figures (match MiniMax's table)Last checked: October 26, 2026
Context sources
- PolicyMiniMax platform privacy policyNanonoble Pte. Ltd. (Singapore); data stored in a US data centreLast checked: October 26, 2026
- PolicyDeepSeek Privacy PolicyData stored in the PRC (updated 10 Feb 2026)Last checked: October 26, 2026
Methodology
Pricing was normalised per 1 million input and output tokens against each vendor's official pricing page on the review date. Benchmark scores were treated as directional indicators, not guarantees of real-world performance. Practical comparisons also weighed coding, reasoning, summarisation, and developer-workflow scenarios.
Data confidence
High for official pricing and feature presence; medium for cross-vendor benchmark comparisons; low for subjective workflow verdicts.
Editorial note
Pricing and model line-ups change frequently in this market. The verdicts here are calibrated for the date shown above and should be re-checked before final purchasing decisions.
