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

Cosmos-Reason2-2B vs MiniMax-M2.7

Cosmos-Reason2-2B scores 59.5 (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

Cosmos-Reason2-2B C

Best for Agents that need a small local model to reason over camera footage and images for robotics, driving or smart spaces

Ahead on

  • Reach, 65 against 60
  • Risk, 60 against 30
  • Documentation and upkeep, 39 against 27

Also in its favour

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

Watch for

Gated behind a click-through licence that needs a Hugging Face account

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 65

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 runCosmos-Reason2-2BMiniMax-M2.7Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256560Cosmos-Reason2-2B +5
Risk20%206030Cosmos-Reason2-2B +30
Agent interface10%106575MiniMax-M2.7 +10
Documentation and upkeep10%103927Cosmos-Reason2-2B +12
Negative events≤1500
TotalC 59.5/100C 56.1/100

Facts side by side

FactCosmos-Reason2-2BMiniMax-M2.7
KindOpen-weight modelOpen-weight model
VendorNVIDIAMiniMax
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceNVIDIA Open Model License (custom, commercial use allowed, not an OSI licence); built on Qwen3-VL-2B-Instruct under Apache 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-03-102026-04-20
Terms last updatedno 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

Cosmos-Reason2-2B

A small local cousin for reasoning over video and images in robotics, driving and warehouse scenes, returning points, boxes and timed events as JSON. The 4.9 GB file runs in Transformers or vLLM, though NVIDIA asks for 24 GB of GPU memory. Development has moved to Cosmos 3, and the gated licence is revocable.

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

Cosmos-Reason2-2B

  1. Accept the licence on the Hugging Face card with a signed-in account and set HF_TOKEN before downloading
  2. Serve it with vllm serve nvidia/Cosmos-Reason2-2B --max-model-len 16384 --media-io-kwargs '{"video": {"num_frames": -1}}' --reasoning-parser qwen3, keeping max-model-len between 8,192 and 16,384 as NVIDIA advises
  3. For local video or images, make a folder for them (mkdir -p media) and pass --allowed-local-media-path "$(pwd)/media", so the server can read only that folder, not everything under the directory you start it from
  4. Sample video at 4 fps and allow at least 4,096 output tokens so the reasoning isn't cut off
  5. For reasoning, add the card's instruction to answer with a think block and then the answer; leave it out for a direct reply
  6. Use NVIDIA's prompt files (prompts/*.yaml in nvidia-cosmos/cosmos-reason2) when you want JSON boxes, events or trajectories, and validate the JSON yourself
  7. Check its plans before a robot acts on them, since NVIDIA's own safety card warns of collision and manipulation risks

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, Cosmos-Reason2-2B or MiniMax-M2.7?

Cosmos-Reason2-2B scores 59.5 (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 Cosmos-Reason2-2B 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.