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

MiniCPM5-2B vs MiniMax-M2.5

MiniCPM5-2B scores 60.2 (C) on agent readiness against MiniMax-M2.5's 57.5 (C), and leads in 3 of 5 scored categories. MiniMax-M2.5 leads on capability. 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

MiniCPM5-2B C

Best for On-device and laptop agents that want a 2 GB tool-calling helper with long context and open training data

Ahead on

  • Reach, 90 against 65
  • Risk, 55 against 30
  • Documentation and upkeep, 97 against 22

Also in its favour

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

Watch for

OpenBMB documents only a Think mode for the 2B, so every answer starts with reasoning

MiniMax-M2.5 C

Best for Teams with a 4 to 8 GPU server who want an open agent and coding model with parallel tool calls and can live with its use policy

Ahead on

  • Capability, 73 against 27

Watch for

230 GB in FP8, and about 155 GB for the smallest 4-bit library build, more than a 128 GB machine

Score by category

CategoryWeight this runMiniCPM5-2BMiniMax-M2.5Edge
Capability35%352773MiniMax-M2.5 +46
Reach25%259065MiniCPM5-2B +25
Risk20%205530MiniCPM5-2B +25
Agent interface10%107575even
Documentation and upkeep10%109722MiniCPM5-2B +75
Negative events≤1500
TotalC 60.2/100C 57.5/100

Facts side by side

FactMiniCPM5-2BMiniMax-M2.5
KindOpen-weight modelOpen-weight model
VendorOpenBMBMiniMax
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MiniMax Model License (model) and modified MIT (code)
Read-only variant documentednono
llms.txtnono
Last release2026-09-292026-02-12
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 reviews3/5 (4)1.8/5 (4)

Verdicts

MiniCPM5-2B

A tiny dense cousin for local tool calling and long context, with published training data and an active publisher. OpenBMB's own 4-bit builds need about 2 GB, so it runs on a laptop or phone in vLLM, SGLang, llama.cpp, Ollama or Transformers. The main risks are always-on thinking, no safety results and use conditions beyond Apache 2.0.

MiniMax-M2.5

MiniMax-M2.5 is a 230B mixture-of-experts model for coding and agent work, with parallel tool calls, a 196K context and parsers in vLLM and SGLang. It needs a 4-GPU server for FP8 or about 155 GB for a 4-bit build. The main risk is a licence replaced after release with a Prohibited Uses Policy while the card still says modified MIT.

Before you call either

MiniCPM5-2B

  1. Smallest start is ollama run openbmb/minicpm5-2b (1.6 GB, q4_k_m)
  2. On vLLM 0.29.0 or later run vllm serve openbmb/MiniCPM5-2B --max-model-len 131072 --enable-auto-tool-choice --tool-call-parser minicpm5, or tool calls come back as XML text
  3. On SGLang 0.5.16 or later add --tool-call-parser minicpm5 --reasoning-parser qwen3; SGLang is OpenBMB's recommended backend for tool calls
  4. Tool calls are XML, <function name=...><param name=...>, not Hermes JSON
  5. Sample with temperature 1.0, top_p 0.95 and min_p 0.0; llama.cpp's default min_p 0.05 can loop, and repetition_penalty 1.05 helps if it does
  6. Expect a <think> block before every answer and leave room in max_tokens; enable_thinking false is accepted by the template but OpenBMB doesn't support it for the 2B
  7. Validate JSON yourself or use the runtime's guided decoding, since structured output isn't documented
  8. Use the main repository's template; the GGUF, MLX and GPTQ copies predate the 29 September fix

MiniMax-M2.5

  1. Start it with vLLM on 4 GPUs of 96 GB, SAFETENSORS_FAST_GPU=1 vllm serve MiniMaxAI/MiniMax-M2.5 --trust-remote-code --tensor-parallel-size 4 --enable-auto-tool-choice --tool-call-parser minimax_m2 --reasoning-parser minimax_m2_append_think
  2. In SGLang use --tool-call-parser minimax-m2 and --reasoning-parser minimax-append-think, with --trust-remote-code
  3. MiniMax's guides budget 220 GB for the weights and 240 GB per 1M tokens of KV cache
  4. On a single large-memory machine, LM Studio's catalogue entry minimax/minimax-m2.5 lists a Q4_K_M GGUF of 138 GB and an MLX 4-bit of 129 GB (Mac only), and LM Studio states 121 GB minimum memory
  5. Sample with temperature 1.0, top_p 0.95 and top_k 40, as the card recommends
  6. Budget output tokens for thinking on every turn, since the template always opens a think block
  7. Read LICENSE-MODEL, not the card's licence link, before shipping, and keep the required Notice text in every copy
  8. Without the hardware, call it through Novita or Featherless AI; MiniMax's own API retires M2.5 on 18 November 2026

Questions

Which is better for AI agents, MiniCPM5-2B or MiniMax-M2.5?

MiniCPM5-2B scores 60.2 (C) on agent readiness against MiniMax-M2.5's 57.5 (C), and leads in 3 of 5 scored categories. MiniMax-M2.5 leads on capability.

Other comparisons with MiniCPM5-2B or MiniMax-M2.5

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.