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

Darwin-36B-Opus vs MiniMax-M2.7

Darwin-36B-Opus scores 61 (C) on agent readiness against MiniMax-M2.7's 56.1 (C), and leads in 3 of 4 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

Darwin-36B-Opus C

Best for Reasoning-heavy text tasks on a 32 GB machine or a single 80 GB GPU, where a disclosed training method isn't required

Ahead on

  • Reach, 80 against 60
  • Risk, 55 against 30
  • Documentation and upkeep, 51 against 27

Also in its favour

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

Watch for

The merge method is proprietary and the current weights include an undescribed targeted refinement

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 70

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 runDarwin-36B-OpusMiniMax-M2.7Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258060Darwin-36B-Opus +20
Risk20%205530Darwin-36B-Opus +25
Agent interface10%107075MiniMax-M2.7 +5
Documentation and upkeep10%105127Darwin-36B-Opus +24
Negative events≤1500
TotalC 61/100C 56.1/100

Facts side by side

FactDarwin-36B-OpusMiniMax-M2.7
KindOpen-weight modelOpen-weight model
VendorFINAL-Bench (VIDRAFT)MiniMax
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MiniMax M2.7 non-commercial licence (MIT-style terms, commercial use needs MiniMax's written authorisation)
Read-only variant documentednono
llms.txtnono
Last release2026-04-232026-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.5/5 (4)1.8/5 (4)

Verdicts

Darwin-36B-Opus

A text-only reasoning cousin merged from Qwen3.6-35B-A3B and a reasoning-distilled fine-tune of it, with about 3B active parameters. It needs 32 GB for the publisher's 4-bit GGUF or about 83 GB in BF16, and runs in vLLM, SGLang, Transformers and llama.cpp. The main risks are an undisclosed merge method, a card that disagrees with its files, and no safety results.

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

Darwin-36B-Opus

  1. Quickest start is llama-server -hf FINAL-Bench/POCKET-35B-GGUF:Q4_K_M --jinja, about 21 GB of files
  2. On the reference machine BF16 fits, vllm serve FINAL-Bench/Darwin-36B-Opus --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, the parsers for Qwen3.6's format
  3. Thinking is on by default, send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  4. The card suggests temperature 0.6 to 0.7 and at least 5,120 new tokens for its think traces
  5. generation_config.json stops only on the end-of-text token, so add <|im_end|> as a stop token if a runtime keeps generating after the turn ends
  6. Text only, the vision encoder of Qwen3.6-35B-A3B isn't in these files
  7. Validate JSON output yourself, since structured output isn't documented

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, Darwin-36B-Opus or MiniMax-M2.7?

Darwin-36B-Opus scores 61 (C) on agent readiness against MiniMax-M2.7's 56.1 (C), and leads in 3 of 4 scored categories. MiniMax-M2.7 leads on agent interface.

Other comparisons with Darwin-36B-Opus 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.