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

MiniMax-M2.7 vs Nanbeige4.2-3B

Nanbeige4.2-3B scores 61 (C) on agent readiness against MiniMax-M2.7's 57.6 (C), and leads in every scored category. Both do open-weight models you run yourself.

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

Which one, for what

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

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Nanbeige4.2-3B C

Best for Local agents that need tool calling and a long context on a laptop or a small GPU

Ahead on

  • Reach, 85 against 60
  • Risk, 55 against 30
  • Agent interface, 85 against 75
  • Documentation and upkeep, 72 against 42

Watch for

Its own architecture: Transformers loads it only with the repository's code

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Documentation and upkeep Nanbeige4.2-3B +30

MiniMax-M2.7 42

The model card earns 2, stating only intended use and leaving out limitations, architecture, parameters, context, natural languages and a cut-off. Training data earns nothing, since only the training process is described. The last change earns 20, a card commit on 26 October 2026 that renames a MiniMax Agent link to MiniMax Code, 9 days before this check; the files, template and code last changed on 20 April 2026. Responsiveness earns 10, with a MiniMax reply in 8 of 36 discussions, none since June. Version policy earns 5, since earlier and later models sit in their own repositories without dated notes. File health earns 5, because a report that it doesn't load in Transformers v5 waits without a reply.

Nanbeige4.2-3B 72

Model card 17, Intended use, limitations, the architecture, the parameters (3B outside the embeddings), the context and the languages (in the metadata) are on the card. Training data 5, A general description of how the fine-tuning and reinforcement learning data was built and filtered, with no sources, sizes or cut-off. Last change 15, the last commit, on 11 September 2026, updated modeling_nanbeige.py, 60 days before this check and within 90. Responsiveness 20, Of the 34 most recent discussions that aren't pull requests (21 July to 10 September 2026), 20 have a reply from a Nanbeige member, which is most. Version policy 5, Nanbeige's earlier models (Nanbeige4-3B, 4.1-3B) stay in their own repositories, as the Base, FP8, 8-bit and DSpark builds of this one do. File health 10, Config, tokenizer config, template and card agree on the architecture and the 262,144 tokens. 17 + 5 + 15 + 20 + 5 + 10 = 72.

Reach Nanbeige4.2-3B +25

MiniMax-M2.7 60

Memory earns 5. MiniMax only publishes its 230 GB FP8 release, and the smallest build of 4-bit or better from a runtime's own library is LM Studio's Q4_K_M GGUF at 138.3 GB, about 166 GB with the fifth added, so it needs more than our 107.4 GB machine and fits within 256 GB. Runtimes earn the full 25, with model code in released vLLM, SGLang, llama.cpp and Transformers, an LM Studio catalogue entry, and Ollama 0.40.14, whose pinned llama.cpp b11963 has the minimax-m2 architecture (capped at 25). Builds earn 10 for one publisher precision, the FP8 release. Terms earn 5, since the licence today allows only personal, research and non-profit use without MiniMax's written authorisation. Download earns 10, with no gate or account. Hosted earns 5, since Novita, Featherless AI and DeepInfra serve it through Hugging Face, while MiniMax's own API is closed to new users and retires it on 18 November 2026.

Nanbeige4.2-3B 85

Memory 30, the smallest build from Nanbeige is the FP8 repository (the 8-bit GPTQ one is the same size), 5.19 GB, and 5.19 GB × 1.2 = 6.2 GB, within 16 GB. bartowski's GGUF isn't read for this line. Runtimes 15, Released SGLang 0.5.23 has the model (srt/models/nanbeige.py) with its parsers, llama.cpp b12242 has the nanbeige architecture, and vLLM 0.33.0 names NanbeigeForCausalLM in its registry, served through its Transformers backend. Builds 15, Quantised builds from Nanbeige at two precisions, FP8 and 8-bit GPTQ, each in its own repository. Terms 15, Apache 2.0 in the card's metadata, an OSI licence, with no use policy or other terms on the card. Download 10, the Hub API reports gated false for the model and its FP8 and 8-bit repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it, and no Nanbeige or BOSS Zhipin API for it was found. 30 + 15 + 15 + 15 + 10 + 0 = 85.

Risk Nanbeige4.2-3B +25

MiniMax-M2.7 30

File safety earns 15, safetensors only with no pickle files, less 10 because every documented loading route passes trust_remote_code for the repository's Python. Provenance earns the full 15, files in the organisation MiniMax links to with a SHA-256 for each shard. Safety evaluation and agent guidance earn nothing, as MiniMax publishes neither. Licence risk earns nothing (read 21 October 2026). The Prohibited Uses appendix goes beyond the law, MiniMax swapped a commercial licence for a non-commercial one two days after release, and neither that swap nor the amendment three days later carries a dated note. The security programme earns nothing, with no security.txt, disclosure policy, SECURITY.md or advisories.

Nanbeige4.2-3B 55

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the Nanbeige organisation (Nanbeige LLM Lab), which the lab's arXiv report for this model links, so the publisher's own account, although the Hub hasn't verified it (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions: the limitations section says outputs may be inaccurate, biased or harmful. Licence risk 15, Apache 2.0 has no use policy, no threshold and no clause letting the licensor change or revoke it. Security programme 5, BOSS Zhipin runs a security response centre for reporting flaws in its products, as read for the Nanbeige4.3-33B listing (5), though nothing links it to the model. 15 + 15 + 0 + 5 + 15 + 5 = 55.

Agent interface Nanbeige4.2-3B +10

MiniMax-M2.7 75

The chat template earns 20 for chat_template.jinja in the repository. The tool-calling format earns 25, as MiniMax's own guide documents how tools go in and how calls come back, gives a parsing function, and its deployment guides name the vLLM and SGLang parsers. Trained tool calling earns 20, with several invoke blocks in one call. Structured output earns nothing, since JSON output isn't documented or claimed. Reasoning control earns nothing, because thinking is always on with no documented way to turn it off or budget it. Context earns 10 for 204,800 tokens in the config with no position scaling.

Nanbeige4.2-3B 85

Chat template 20, A Jinja chat template in tokenizer_config.json (7,961 characters), with enable_thinking, preserve_thinking, tools and tool_call_format switches. Tool-calling format 25, the card says passing tools switches on the tool template and recommends tool_call_format xml, with json for compatibility, and its SGLang and vLLM commands name the nanbeige tool-call parser, which released SGLang 0.5.23 has. Trained tool calling 20, the card describes fine-tuning on tool-use environments and agent scaffolds and reinforcement learning on agent tasks, and the template tells the model it may call one or more functions and renders every call in a turn. Structured output 0, Neither the card nor the files mention JSON or JSON Schema output, beyond json as a tool-call format. Reasoning control 10, the card documents enable_thinking, on by default and False per request, and preserve_thinking for earlier turns, and names the nanbeige reasoning parser, which returns the reasoning apart from the answer. Context 10, 262,144 tokens, which the card says the model supports and config.json gives as max_position_embeddings. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Score by category

CategoryWeight this runMiniMax-M2.7Nanbeige4.2-3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256085Nanbeige4.2-3B +25
Risk20%203055Nanbeige4.2-3B +25
Agent interface10%107585Nanbeige4.2-3B +10
Documentation and upkeep10%104272Nanbeige4.2-3B +30
Negative events≤1500
TotalC 57.6/100C 61/100

Facts side by side

FactMiniMax-M2.7Nanbeige4.2-3B
KindOpen-weight modelOpen-weight model
VendorMiniMaxNanbeige LLM Lab (BOSS Zhipin)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMiniMax M2.7 non-commercial licence (MIT-style terms, commercial use needs MiniMax's written authorisation)Apache-2.0 (Hub metadata only; the repository has no LICENSE file)
Read-only variant documentednono
llms.txtnono
Last release2026-04-202026-09-11
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews1.8/5 (4)none

How the scores have moved

Verdicts

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.

Nanbeige4.2-3B

A small model built for agent work, with tool calling it was trained for, a thinking switch and a 256K context in about 5 GB, under Apache 2.0, from a lab that answers most questions. Its architecture is its own, so check your runtime: SGLang and llama.cpp have it, Transformers needs the repository's code, and Nanbeige ships no GGUF.

Before you call either

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

Nanbeige4.2-3B

  1. Serve it with SGLang 0.5.23 or later and pass --tool-call-parser nanbeige --reasoning-parser nanbeige
  2. Pass tools in the request. The card recommends tool_call_format="xml"
  3. Set preserve_thinking true for multi-turn tool use and coding, false for plain chat
  4. Use temperature 1.0 for agent and tool work and 0.6 for reasoning and chat, per the card
  5. For llama.cpp use b12242 or later. The GGUF files on the Hub are bartowski's, not Nanbeige's
  6. If you load it with Transformers, read modeling_nanbeige.py first: trust_remote_code runs it

Questions

Which is better for AI agents, MiniMax-M2.7 or Nanbeige4.2-3B?

Nanbeige4.2-3B scores 61 (C) on agent readiness against MiniMax-M2.7's 57.6 (C), and leads in every scored category.

Other comparisons with MiniMax-M2.7 or Nanbeige4.2-3B

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.