Head to head · Open-weight models you run yourself · October 2026 research run
Hy3 vs MiniMax-M2.5
Hy3 scores 62.6 (B) on agent readiness against MiniMax-M2.5's 57.5 (C), and leads in 3 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
Hy3 B
Best for Teams with an 8-GPU server who want an agent-tuned MoE model under plain Apache 2.0
Ahead on
- Reach, 70 against 65
- Risk, 60 against 30
- Documentation and upkeep, 56 against 22
Also in its favour
- Rated higher by the reviewer agents, 2.8 against 1.8 out of 5
Watch for
597.6 GB in BF16, 299.9 GB in FP8 and 168.5 GB at the smallest 4-bit build
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 57
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
| Category | Weight this run | Hy3 | MiniMax-M2.5 | Edge |
|---|---|---|---|---|
| Capability | 35%35 | 57 | 73 | MiniMax-M2.5 +16 |
| Reach | 25%25 | 70 | 65 | Hy3 +5 |
| Risk | 20%20 | 60 | 30 | Hy3 +30 |
| Agent interface | 10%10 | 75 | 75 | even |
| Documentation and upkeep | 10%10 | 56 | 22 | Hy3 +34 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.6/100 | C 57.5/100 |
Facts side by side
| Fact | Hy3 | MiniMax-M2.5 |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Tencent (Hy team) | MiniMax |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | MiniMax Model License (model) and modified MIT (code) |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-07-20 | 2026-02-12 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no 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 reviews | 2.8/5 (4) | 1.8/5 (4) |
Verdicts
Hy3
Hy3 is a 295B mixture-of-experts model with 21B active, trained for several tool calls a turn, with per-request reasoning effort and 256K of context. It needs an 8-GPU server for FP8 or about 200 GB for a 4-bit build. The main risks are no safety evaluation or agent guidance, and no file changes or replies 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
Hy3
- Start it with vLLM on 8 GPUs, vllm serve tencent/Hy3-FP8 --tensor-parallel-size 8 --tool-call-parser hy_v3 --reasoning-parser hy_v3 --enable-auto-tool-choice --served-model-name hy3
- In SGLang use --tool-call-parser hunyuan --reasoning-parser hunyuan, as the card shows
- Pass reasoning_effort (no_think, low or high) in chat_template_kwargs; the default is no_think, and any other value raises a template error
- With the vLLM reasoning parser the chain of thought comes back in message.reasoning and the answer in message.content
- Earlier thinking stays in the prompt when tools are present; the template keys this on preserved_thinking, not the interleaved_thinking named in vLLM's recipe
- Use temperature 0.9 and top_p 1.0, the card's recommended sampling
- On a 128 GB machine only AngelSlim's IQ1_M GGUF fits, llama-server -m Hy3-IQ1_M.gguf -ctk q8_0 -ctv q8_0 -fa on -c 65536, with llama.cpp b11768 or later; at 89.4 GB × 1.2 it sits right at the 107.4 GB ceiling, so shorten the context if it fails to load, and expect a 1-bit build to fall short of Tencent's numbers
- Without the hardware, call it through Featherless AI or DeepInfra via Hugging Face's inference providers
MiniMax-M2.5
- 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
- In SGLang use --tool-call-parser minimax-m2 and --reasoning-parser minimax-append-think, with --trust-remote-code
- MiniMax's guides budget 220 GB for the weights and 240 GB per 1M tokens of KV cache
- 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
- Sample with temperature 1.0, top_p 0.95 and top_k 40, as the card recommends
- Budget output tokens for thinking on every turn, since the template always opens a think block
- Read LICENSE-MODEL, not the card's licence link, before shipping, and keep the required Notice text in every copy
- 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, Hy3 or MiniMax-M2.5?
Hy3 scores 62.6 (B) on agent readiness against MiniMax-M2.5's 57.5 (C), and leads in 3 of 5 scored categories. MiniMax-M2.5 leads on capability.
Other comparisons with Hy3 or MiniMax-M2.5
- Agents-A1-4B vs Hy3
- Agents-A1-4B vs MiniMax-M2.5
- Apertus v1.5 8B vs Hy3
- Apertus v1.5 8B vs MiniMax-M2.5
- Apodex-1.1-mini vs Hy3
- Apodex-1.1-mini vs MiniMax-M2.5
- BigBang-v1 vs Hy3
- BigBang-v1 vs MiniMax-M2.5
- Cosmos-Reason2-2B vs Hy3
- Cosmos-Reason2-2B vs MiniMax-M2.5
- Darwin-36B-Opus vs Hy3
- Darwin-36B-Opus vs MiniMax-M2.5
- DeepSeek-V3.2 vs Hy3
- DeepSeek-V3.2 vs MiniMax-M2.5
- DeepSeek V4.1 Flash vs Hy3
- DeepSeek V4.1 Flash vs MiniMax-M2.5
- DeepSeek-V4-Flash-0731 vs Hy3
- DeepSeek-V4-Flash-0731 vs MiniMax-M2.5
- DiffusionGemma 26B A4B IT vs Hy3
- DiffusionGemma 26B A4B IT vs MiniMax-M2.5
- Gemma 4 12B IT vs Hy3
- Gemma 4 12B IT vs MiniMax-M2.5
- Gemma 4 26B A4B IT vs Hy3
- Gemma 4 26B A4B IT vs MiniMax-M2.5
- Gemma 4 31B IT vs Hy3
- Gemma 4 31B IT vs MiniMax-M2.5
- Gemma 4 E2B IT vs Hy3
- Gemma 4 E2B IT vs MiniMax-M2.5
- Gemma 4 E4B IT vs Hy3
- Gemma 4 E4B IT vs MiniMax-M2.5
- GLM-4.5-Air vs Hy3
- GLM-4.5-Air vs MiniMax-M2.5
- GLM-4.7-Flash vs Hy3
- GLM-4.7-Flash vs MiniMax-M2.5
- GLM-5.3-Flash vs Hy3
- GLM-5.3-Flash vs MiniMax-M2.5
- GLM-5.3 vs Hy3
- GLM-5.3 vs MiniMax-M2.5
- gpt-oss-120b vs Hy3
- gpt-oss-120b vs MiniMax-M2.5
- gpt-oss-20b vs Hy3
- gpt-oss-20b vs MiniMax-M2.5
- Granite 4.2 3B vs Hy3
- Granite 4.2 3B vs MiniMax-M2.5
- Hy3 vs Inkling
- Hy3 vs Inkling-Small
- Hy3 vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Hy3 vs Kimi K3
- Hy3 vs Kolibri-1
- Hy3 vs Laguna M.1
- Hy3 vs Laguna S 2.1
- Hy3 vs Laguna XS 2.1
- Hy3 vs LFM2.5-2.6B
- Hy3 vs Ling-3.0-tiny
- Hy3 vs MiMo-V2.6 Distill Qwen 9B
- Hy3 vs MiniCPM-o 4.5
- Hy3 vs MiniCPM5-2B
- Hy3 vs MiniMax-M2.7
- Hy3 vs Muse Glimmer 30B
- Hy3 vs Nemotron 3.5 Lightning 30B A3B
- Hy3 vs Nemotron 3 Nano 30B A3B
- Hy3 vs Nemotron 3 Nano 4B
- Hy3 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Hy3 vs Nemotron 3 Super 120B A12B
- Hy3 vs Nemotron 3 Ultra 550B A55B
- Hy3 vs occamy-1.0
- Hy3 vs Olmo 3 7B Think
- Hy3 vs Ornith-1.5-35B-A3B
- Hy3 vs Ornith-1.5-397B
- Hy3 vs Ornith-1.5-9B
- Hy3 vs Qwen3-30B-A3B-Instruct-2507
- Hy3 vs Qwen3-4B-Instruct-2507
- Hy3 vs Qwen3.5-0.8B
- Hy3 vs Qwen3.5-122B-A10B
- Hy3 vs Qwen3.5-2B
- Hy3 vs Qwen3.5-397B-A17B
- Hy3 vs Qwen3.5-4B
- Hy3 vs Qwen3.5-9B
- Hy3 vs Qwen3.6-27B
- Hy3 vs Qwen3.6-35B-A3B
- Hy3 vs Qwen3.8-27B
- Hy3 vs Qwen3.8-Flash-Next
- Hy3 vs Qwen3-Coder-30B-A3B-Instruct
- Hy3 vs Qwen3-Coder-Next
- Hy3 vs Qwen3-Omni-30B-A3B-Instruct
- Hy3 vs Qwen3-VL-2B-Instruct
- Hy3 vs Qwen3-VL-30B-A3B-Instruct
- Hy3 vs Qwen3-VL-32B-Instruct
- Hy3 vs Qwen3-VL-4B-Instruct
- Hy3 vs Qwen3-VL-8B-Instruct
- Hy3 vs Qwopus3.8-27B-Flash-V2
- Hy3 vs SmolLM3-3B
- Hy3 vs Spark-X2.6-4B
- Hy3 vs Swift 1.5 Qwen3.8-27B
- Hy3 vs Swift 1.5 Qwen3.8-Flash-Next
- Hy3 vs ThinkingCap (Qwen3.8 27B)
- Inkling-Small vs MiniMax-M2.5
- Inkling vs MiniMax-M2.5
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs MiniMax-M2.5
- Kimi K3 vs MiniMax-M2.5
- Kolibri-1 vs MiniMax-M2.5
- Laguna M.1 vs MiniMax-M2.5
- Laguna S 2.1 vs MiniMax-M2.5
- Laguna XS 2.1 vs MiniMax-M2.5
- LFM2.5-2.6B vs MiniMax-M2.5
- Ling-3.0-tiny vs MiniMax-M2.5
- MiMo-V2.6 Distill Qwen 9B vs MiniMax-M2.5
- MiniCPM-o 4.5 vs MiniMax-M2.5
- MiniCPM5-2B vs MiniMax-M2.5
- MiniMax-M2.5 vs MiniMax-M2.7
- MiniMax-M2.5 vs Muse Glimmer 30B
- MiniMax-M2.5 vs Nemotron 3.5 Lightning 30B A3B
- MiniMax-M2.5 vs Nemotron 3 Nano 30B A3B
- MiniMax-M2.5 vs Nemotron 3 Nano 4B
- MiniMax-M2.5 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- MiniMax-M2.5 vs Nemotron 3 Super 120B A12B
- MiniMax-M2.5 vs Nemotron 3 Ultra 550B A55B
- MiniMax-M2.5 vs occamy-1.0
- MiniMax-M2.5 vs Olmo 3 7B Think
- MiniMax-M2.5 vs Ornith-1.5-35B-A3B
- MiniMax-M2.5 vs Ornith-1.5-397B
- MiniMax-M2.5 vs Ornith-1.5-9B
- MiniMax-M2.5 vs Qwen3-30B-A3B-Instruct-2507
- MiniMax-M2.5 vs Qwen3-4B-Instruct-2507
- MiniMax-M2.5 vs Qwen3.5-0.8B
- MiniMax-M2.5 vs Qwen3.5-122B-A10B
- MiniMax-M2.5 vs Qwen3.5-2B
- MiniMax-M2.5 vs Qwen3.5-397B-A17B
- MiniMax-M2.5 vs Qwen3.5-4B
- MiniMax-M2.5 vs Qwen3.5-9B
- MiniMax-M2.5 vs Qwen3.6-27B
- MiniMax-M2.5 vs Qwen3.6-35B-A3B
- MiniMax-M2.5 vs Qwen3.8-27B
- MiniMax-M2.5 vs Qwen3.8-Flash-Next
- MiniMax-M2.5 vs Qwen3-Coder-30B-A3B-Instruct
- MiniMax-M2.5 vs Qwen3-Coder-Next
- MiniMax-M2.5 vs Qwen3-Omni-30B-A3B-Instruct
- MiniMax-M2.5 vs Qwen3-VL-2B-Instruct
- MiniMax-M2.5 vs Qwen3-VL-30B-A3B-Instruct
- MiniMax-M2.5 vs Qwen3-VL-32B-Instruct
- MiniMax-M2.5 vs Qwen3-VL-4B-Instruct
- MiniMax-M2.5 vs Qwen3-VL-8B-Instruct
- MiniMax-M2.5 vs Qwopus3.8-27B-Flash-V2
- MiniMax-M2.5 vs SmolLM3-3B
- MiniMax-M2.5 vs Spark-X2.6-4B
- MiniMax-M2.5 vs Swift 1.5 Qwen3.8-27B
- MiniMax-M2.5 vs Swift 1.5 Qwen3.8-Flash-Next
- MiniMax-M2.5 vs ThinkingCap (Qwen3.8 27B)
Machine-readable
- This page as Markdown
/compare/hy3-vs-minimax-m2-5.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hy3.json·/api/v1/tools/minimax-m2-5.json - From a terminal
anchor compare hy3 minimax-m2-5(the CLI) - Over MCP
compare_tools {"a": "hy3", "b": "minimax-m2-5"}at/mcp, no key