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

LongCat-2.5 vs MiniMax-M2.5

MiniMax-M2.5 scores 59 (C) on agent readiness against LongCat-2.5's 50.5 (D), and leads in 1 of 4 scored categories. LongCat-2.5 leads on risk and documentation and upkeep. 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

LongCat-2.5 D

Best for Operators with NPU clusters, and anyone tracking what the open flagships can do

Ahead on

  • Risk, 60 against 30
  • Documentation and upkeep, 46 against 37

Watch for

3,562 GB in BF16 and 1,336 GB at 4 bits

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

  • Reach, 65 against 35

Watch for

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

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.

Reach MiniMax-M2.5 +30

LongCat-2.5 35

Memory 0, the smallest build is Meituan's W4A4 repository, 1,336 GB, and 1,336 GB × 1.2 = 1,603 GB, far above 256 GB. The BF16 files are 3,562 GB. Runtimes 0, none of the six runs it in a released version: vLLM 0.33.0, SGLang 0.5.23, Transformers 5.22.2 and llama.cpp b12242 have no LongcatCausalLM or pro_v code, and the model code config.json names isn't in the repository. Builds 10, one quantised build from Meituan, the W4A4 repository (4-bit experts, 1,336 GB). Terms 15, MIT in the metadata, the LICENSE file and the card, with nothing added. Download 10, the Hub API reports gated false for both 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. 0 + 0 + 10 + 15 + 10 + 0 = 35.

MiniMax-M2.5 65

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 MLX 4-bit at 128.7 GB, about 154 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 v0.33.0, SGLang v0.5.23, llama.cpp and Transformers, an LM Studio catalogue entry, and Ollama 0.40.14, whose pinned llama.cpp b11963 has the minimax-m2 architecture, though Ollama's library lists no build. Builds earn 10 for one publisher precision, the FP8 release. Terms earn 10 for a custom licence that allows free commercial use under a use policy. Download earns 10, with no gate or account. Hosted earns 5, since Novita and Featherless AI serve it through Hugging Face, while MiniMax's own API is closed to new users and retires it on 18 November 2026. 5+25+10+10+10+5 = 65.

Risk LongCat-2.5 +30

LongCat-2.5 60

File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in the meituan-longcat organisation, the name of Meituan's GitHub organisation that the card links for deployment, and the card's licence names Meituan (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions under Usage Considerations: not evaluated for every use, assess accuracy, safety and fairness before sensitive use, and follow the law. Licence risk 15, MIT with no use policy, no threshold and no right to change the terms. Security programme 0, no way to report a flaw on the card beyond a general contact, and Meituan's own security pages weren't looked up, so this scores as absent and is an open question. 25 + 15 + 0 + 5 + 15 + 0 = 60.

MiniMax-M2.5 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 Policy goes beyond the law, MiniMax can end the licence for any breach and replaced its terms three weeks after release, and that change on 6 March 2026 came with no dated note while the card still links to a deleted file. The security programme earns nothing, with no security.txt, disclosure policy, SECURITY.md or advisories, and only a general contact address on the card.

Documentation and upkeep LongCat-2.5 +9

LongCat-2.5 46

Model card 11, Intended use, limitations (the usage considerations), the architecture and the parameter counts are on the card. Training data 5, A general description of the training stages and where the reinforcement learning tasks came from, with no sources, sizes or cut-off. Last change 20, the last commit, on 10 November 2026, updated the card, on the day of this check. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (9 and 10 November 2026) has a reply from a meituan-longcat member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, LongCat-2.0 stays in its own repositories and 2.5 came out in new ones, with no dated note on the older ones that we read. File health 5, the template is in both places and agrees, but config.json's auto_map names configuration_longcat_oe and modeling_longcat_oe, which aren't in the repository, and the tokenizer config's 131,072-token length is a quarter of the config's 524,288 positions. 11 + 5 + 20 + 0 + 5 + 5 = 46.

MiniMax-M2.5 37

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 5 for a general description with no cut-off. The last change earns 20, a card edit on 26 October 2026 (commit 2515a3ea, a link renamed from MiniMax Agent to MiniMax Code), 9 days before this check; the files, template and code are unchanged since February. Responsiveness earns 5, with a MiniMax reply in 2 of the 40 most recent discussions and none since April. Version policy earns 5, since earlier and later models sit in their own repositories without dated notes. File health earns nothing, because the card's licence metadata still contradicts the licence in the files and an FP8 output report still waits without a reply. 2+5+20+5+5+0 = 37.

Score by category

CategoryWeight this runLongCat-2.5MiniMax-M2.5Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%253565MiniMax-M2.5 +30
Risk20%206030LongCat-2.5 +30
Agent interface10%107575even
Documentation and upkeep10%104637LongCat-2.5 +9
Negative events≤1500
TotalD 50.5/100C 59/100

Facts side by side

FactLongCat-2.5MiniMax-M2.5
KindOpen-weight modelOpen-weight model
VendorMeituan (LongCat)MiniMax
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITMiniMax Model License (model) and modified MIT (code)
Read-only variant documentednono
llms.txtnono
Last release2026-11-102026-02-12
Terms last updatednot read yetno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone1.8/5 (4)

How the scores have moved

LongCat-2.5

No score change since it was listed.

MiniMax-M2.5

Verdicts

LongCat-2.5

Meituan's flagship is MIT-licensed and documented for tool calling and switchable reasoning, with strong numbers of its own on agentic coding. Almost nobody can run it: 3,562 GB of weights, a 1,336 GB 4-bit build for NPU accelerators, and no released runtime with its architecture. A model to watch until a runtime or a provider picks it up.

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

LongCat-2.5

  1. You can't run this on a workstation or a single GPU server. Plan for a provider, and none serves it yet
  2. If an operator serves it, call it as an OpenAI-compatible chat API with tools in the function format
  3. Pass chat_template_kwargs with enable_thinking true or false
  4. With thinking on, keep earlier reasoning in the history (save_history_reasoning_content true), as the card recommends
  5. The card's results use temperature 1.0 and top_p 0.95
  6. Its benchmark table is Meituan's own. The unmarked scores are in-house

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, LongCat-2.5 or MiniMax-M2.5?

MiniMax-M2.5 scores 59 (C) on agent readiness against LongCat-2.5's 50.5 (D), and leads in 1 of 4 scored categories. LongCat-2.5 leads on risk and documentation and upkeep.

Other comparisons with LongCat-2.5 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.