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

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

  • 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

CategoryWeight this runHy3MiniMax-M2.5Edge
Capability35%355773MiniMax-M2.5 +16
Reach25%257065Hy3 +5
Risk20%206030Hy3 +30
Agent interface10%107575even
Documentation and upkeep10%105622Hy3 +34
Negative events≤1500
TotalB 62.6/100C 57.5/100

Facts side by side

FactHy3MiniMax-M2.5
KindOpen-weight modelOpen-weight model
VendorTencent (Hy team)MiniMax
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MiniMax Model License (model) and modified MIT (code)
Read-only variant documentednono
llms.txtnono
Last release2026-07-202026-02-12
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.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

  1. 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
  2. In SGLang use --tool-call-parser hunyuan --reasoning-parser hunyuan, as the card shows
  3. 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
  4. With the vLLM reasoning parser the chain of thought comes back in message.reasoning and the answer in message.content
  5. 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
  6. Use temperature 0.9 and top_p 1.0, the card's recommended sampling
  7. 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
  8. Without the hardware, call it through Featherless AI or DeepInfra via Hugging Face's inference providers

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, 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

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.