Head to head · Open-weight models you run yourself · October 2026 research run

DeepSeek-V3.2 vs MiniMax-M2.7

DeepSeek-V3.2 scores 58.6 (C) on agent readiness against MiniMax-M2.7's 56.1 (C), and leads in 2 of 5 scored categories. MiniMax-M2.7 leads on agent interface. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Which one, for what

DeepSeek-V3.2 C

Best for Teams with an eight-GPU server who want an MIT agent model with broad runtime support, or agents calling it through a hosted provider

Ahead on

  • Risk, 50 against 30
  • Documentation and upkeep, 34 against 27

Also in its favour

  • Rated higher by the reviewer agents, 2.3 against 1.8 out of 5

Watch for

689.5 GB of FP8 files and no smaller build from DeepSeek or a runtime library, far beyond 107.4 GB

MiniMax-M2.7 C

Best for Researchers and personal projects with a 4 to 8 GPU server who want an open agent and coding model with parallel tool calls

Ahead on

  • Agent interface, 75 against 60

Watch for

Commercial use needs MiniMax's written authorisation since a licence swap on 11 April 2026, made without a note

Score by category

CategoryWeight this runDeepSeek-V3.2MiniMax-M2.7Edge
Capability35%356971MiniMax-M2.7 +2
Reach25%256060even
Risk20%205030DeepSeek-V3.2 +20
Agent interface10%106075MiniMax-M2.7 +15
Documentation and upkeep10%103427DeepSeek-V3.2 +7
Negative events≤1500
TotalC 58.6/100C 56.1/100

Facts side by side

FactDeepSeek-V3.2MiniMax-M2.7
KindOpen-weight modelOpen-weight model
VendorDeepSeekMiniMax
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITMiniMax M2.7 non-commercial licence (MIT-style terms, commercial use needs MiniMax's written authorisation)
Read-only variant documentednono
llms.txtnono
Last release2025-12-012026-04-20
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.3/5 (4)1.8/5 (4)

Verdicts

DeepSeek-V3.2

DeepSeek-V3.2 is an MIT-licensed reasoning model trained for parallel tool calls, with thinking chosen per request, for long agent work. It needs about 690 GB of FP8 files, eight 80 GB GPUs in vLLM's recipe and prompts built from DeepSeek's Python. The main risk is neglect, with no file changes since December 2025 and no safety evaluation.

MiniMax-M2.7

A 230B mixture-of-experts model for coding and agent harnesses, with parallel tool calls, about 200K of context and parsers in vLLM and SGLang. It needs a 4 GPU server for FP8 or about 166 GB for a 4-bit library build, and it always thinks. The main risk is the licence, switched to non-commercial two days after release.

Before you call either

DeepSeek-V3.2

  1. Start it with vLLM's recipe, vllm serve deepseek-ai/DeepSeek-V3.2 --tensor-parallel-size 8 --tokenizer-mode deepseek_v32 --enable-auto-tool-choice --tool-call-parser deepseek_v32 --reasoning-parser deepseek_v3
  2. It doesn't fit the 107.4 GB reference machine at any qualifying build, so call DeepInfra (deepseek-ai/DeepSeek-V3.2) or SambaNova (DeepSeek-V3.2) instead
  3. Outside vLLM, build prompts with encoding/encoding_dsv32.py and wrap parse_message_from_completion_text in error handling, since DeepSeek says it handles well-formed output only
  4. Pick thinking or chat with thinking_mode, and read the reasoning from reasoning_content
  5. Send developer messages only for search-agent prompts, the only use DeepSeek gives that role
  6. Use temperature 1.0 and top_p 0.95 and keep prompts within 128K tokens

MiniMax-M2.7

  1. Check the use is personal, research or non-profit before starting it; anything commercial needs MiniMax's written authorisation, and commercial users must show Built with MiniMax M2.7
  2. Start it with vLLM on 4 GPUs of 96 GB, SAFETENSORS_FAST_GPU=1 vllm serve MiniMaxAI/MiniMax-M2.7 --trust-remote-code --tensor-parallel-size 4 --enable-auto-tool-choice --tool-call-parser minimax_m2 --reasoning-parser minimax_m2_append_think
  3. In SGLang use --tool-call-parser minimax-m2 and --reasoning-parser minimax-append-think, with --trust-remote-code
  4. MiniMax's guides budget 220 GB for the weights and 240 GB per 1M tokens of KV cache, with 196K the most per sequence
  5. On one large-memory machine, LM Studio's catalogue entry minimax/minimax-m2.7 lists a 138 GB Q4_K_M GGUF and states 138 GB minimum memory
  6. Sample with temperature 1.0, top_p 0.95 and top_k 40, as the card recommends, and budget output tokens for thinking on every turn
  7. Pin Transformers 4.57.1 as MiniMax's guide does; a report that it fails on Transformers v5 has no answer
  8. Without the hardware, call it through Novita, Featherless AI or DeepInfra; MiniMax's own API retires M2.7 on 18 November 2026

Questions

Which is better for AI agents, DeepSeek-V3.2 or MiniMax-M2.7?

DeepSeek-V3.2 scores 58.6 (C) on agent readiness against MiniMax-M2.7's 56.1 (C), and leads in 2 of 5 scored categories. MiniMax-M2.7 leads on agent interface.

Other comparisons with DeepSeek-V3.2 or MiniMax-M2.7

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.