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

Gemma 4 31B IT vs MiniMax-M2.5

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against MiniMax-M2.5's 57.5 (C), and leads in 4 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

Gemma 4 31B IT BB

Best for An agent with a 24 GB GPU or more that wants a dense multimodal cousin with tool calling under a plain licence

Ahead on

  • Reach, 95 against 65
  • Risk, 70 against 30
  • Agent interface, 85 against 75
  • Documentation and upkeep, 65 against 22

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.8 against 1.8 out of 5

Watch for

No safety evaluation results published

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 61

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 runGemma 4 31B ITMiniMax-M2.5Edge
Capability35%356173MiniMax-M2.5 +12
Reach25%259565Gemma 4 31B IT +30
Risk20%207030Gemma 4 31B IT +40
Agent interface10%108575Gemma 4 31B IT +10
Documentation and upkeep10%106522Gemma 4 31B IT +43
Negative events≤1500
TotalBB 74.1/100C 57.5/100

Facts side by side

FactGemma 4 31B ITMiniMax-M2.5
KindOpen-weight modelOpen-weight model
VendorGoogle DeepMindMiniMax
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.txtyesno
Last release2026-07-202026-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.8/5 (4)1.8/5 (4)

Verdicts

Gemma 4 31B IT

A dense multimodal cousin with documented tool calling, optional thinking and a 256K context, for general agent work and image reading on one 24 GB GPU through Google's 4-bit build. It runs in every major runtime under plain Apache 2.0. The main risk is that Google publishes no safety results and has gone quiet on the repository since July.

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

Gemma 4 31B IT

  1. On the reference machine run llama-server -hf google/gemma-4-31B-it-qat-q4_0-gguf --hf-file gemma-4-31B_q4_0-it.gguf --jinja -c 32768, adding gemma-4-31B-it-mmproj.gguf for images
  2. Or ollama run gemma4:31b for the 20 GB Q4_K_M build
  3. In vLLM serve with --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4, as vLLM's recipe does
  4. Thinking is off by default, so pass enable_thinking: true in chat_template_kwargs to turn it on, and expect the reasoning in the thought channel block
  5. Drop earlier thoughts from the history except on tool-call turns, as the card asks
  6. Use the card's sampling, temperature 1.0, top_p 0.95, top_k 64
  7. Validate function names and arguments before running a call, and check JSON output yourself or use the runtime's guided decoding
  8. The w4a16 build relies on Marlin INT4 kernels that vLLM marks unsupported on AMD, so use the GGUF on the reference machine

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, Gemma 4 31B IT or MiniMax-M2.5?

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against MiniMax-M2.5's 57.5 (C), and leads in 4 of 5 scored categories. MiniMax-M2.5 leads on capability.

Other comparisons with Gemma 4 31B IT 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.