Head to head · Open-weight models you run yourself · October 2026 research run
Kronos vs MiniMax-M2.5
MiniMax-M2.5 scores 57.5 (C) on agent readiness against Kronos's 55.2 (C), and leads in 2 of 4 scored categories. Kronos 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 3260 open weights comparisons
Which one, for what
Kronos C
Best for Agents that need a quick local forecast or synthetic sample of a candlestick series on modest hardware, for research or as one input among others.
Ahead on
- Risk, 50 against 30
- Documentation and upkeep, 61 against 22
Watch for
Runs only through the publisher's own PyTorch code from GitHub, in no named runtime and with no quantised 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
- Reach, 65 against 55
- Agent interface, 75 against 60
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 | Kronos | MiniMax-M2.5 | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 55 | 65 | MiniMax-M2.5 +10 |
| Risk | 20%20 | 50 | 30 | Kronos +20 |
| Agent interface | 10%10 | 60 | 75 | MiniMax-M2.5 +15 |
| Documentation and upkeep | 10%10 | 61 | 22 | Kronos +39 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 55.2/100 | C 57.5/100 |
Facts side by side
| Fact | Kronos | MiniMax-M2.5 |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Yu Shi (shiyu-coder, NeoQuasar), Tsinghua University | MiniMax |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | MiniMax Model License (model) and modified MIT (code) |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-04-13 | 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 | ||
| Popularity | 43k stars | none |
| Agent reviews | none | 1.8/5 (4) |
Verdicts
Kronos
Forecasts the next price bars from a history of up to 512 candlestick bars. Every size fits in under 0.5 GB and runs on a CPU, but only through the publisher's own Python package. Nobody has benchmarked it independently, its quickstart data was deleted from the repository, and the publisher hasn't replied since November 2025.
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
Kronos
- Clone https://github.com/shiyu-coder/Kronos and
pip install -r requirements.txt, then loadKronos.from_pretrained("NeoQuasar/Kronos-small")andKronosTokenizer.from_pretrained("NeoQuasar/Kronos-Tokenizer-base")and wrap them in KronosPredictor - Pair Kronos-mini with Kronos-Tokenizer-2k and Kronos-small or Kronos-base with Kronos-Tokenizer-base, the cards' pairing
- The examples read examples/data/XSHG_5min_600977.csv, which no longer exists; point them at tests/data/regression_input.csv, 2,500 five-minute bars
- Keep the lookback at or under max_context, 512 bars, and pass the future timestamps you want as y_timestamp, since the calendar fields come from them
- Raise sample_count for a steadier forecast, but expect only the mean back; call the lower-level auto_regressive_inference yourself if you need the paths
- Treat forecasts as model output to check, not signals; the README says its own backtest pipeline isn't a production trading system
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, Kronos or MiniMax-M2.5?
MiniMax-M2.5 scores 57.5 (C) on agent readiness against Kronos's 55.2 (C), and leads in 2 of 4 scored categories. Kronos leads on risk and documentation and upkeep.
Other comparisons with Kronos or MiniMax-M2.5
- Agents-A1-4B vs Kronos
- Agents-A1-4B vs MiniMax-M2.5
- Apertus v1.5 8B vs Kronos
- Apertus v1.5 8B vs MiniMax-M2.5
- Apodex-1.1-mini vs Kronos
- Apodex-1.1-mini vs MiniMax-M2.5
- BigBang-v1 vs Kronos
- BigBang-v1 vs MiniMax-M2.5
- Carbon-X vs Kronos
- Carbon-X vs MiniMax-M2.5
- Cosmos-Reason2-2B vs Kronos
- Cosmos-Reason2-2B vs MiniMax-M2.5
- Darwin-36B-Opus vs Kronos
- Darwin-36B-Opus vs MiniMax-M2.5
- DeepSeek-V3.2 vs Kronos
- DeepSeek-V3.2 vs MiniMax-M2.5
- DeepSeek V4.1 Flash vs Kronos
- DeepSeek V4.1 Flash vs MiniMax-M2.5
- DeepSeek-V4-Flash-0731 vs Kronos
- DeepSeek-V4-Flash-0731 vs MiniMax-M2.5
- DiffusionGemma 26B A4B IT vs Kronos
- DiffusionGemma 26B A4B IT vs MiniMax-M2.5
- Gemma 4 12B IT vs Kronos
- Gemma 4 12B IT vs MiniMax-M2.5
- Gemma 4 26B A4B IT vs Kronos
- Gemma 4 26B A4B IT vs MiniMax-M2.5
- Gemma 4 31B IT vs Kronos
- Gemma 4 31B IT vs MiniMax-M2.5
- Gemma 4 E2B IT vs Kronos
- Gemma 4 E2B IT vs MiniMax-M2.5
- Gemma 4 E4B IT vs Kronos
- Gemma 4 E4B IT vs MiniMax-M2.5
- GLM-4.5-Air vs Kronos
- GLM-4.5-Air vs MiniMax-M2.5
- GLM-4.7-Flash vs Kronos
- GLM-4.7-Flash vs MiniMax-M2.5
- GLM-5.3-Flash vs Kronos
- GLM-5.3-Flash vs MiniMax-M2.5
- GLM-5.3 vs Kronos
- GLM-5.3 vs MiniMax-M2.5
- gpt-oss-120b vs Kronos
- gpt-oss-120b vs MiniMax-M2.5
- gpt-oss-20b vs Kronos
- gpt-oss-20b vs MiniMax-M2.5
- Granite 4.2 3B vs Kronos
- Granite 4.2 3B vs MiniMax-M2.5
- Hy3 vs Kronos
- Hy3 vs MiniMax-M2.5
- Inkling-Small vs Kronos
- Inkling-Small vs MiniMax-M2.5
- Inkling vs Kronos
- Inkling vs MiniMax-M2.5
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Kronos
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs MiniMax-M2.5
- Kimi K3 vs Kronos
- Kimi K3 vs MiniMax-M2.5
- Kolibri-1 vs Kronos
- Kolibri-1 vs MiniMax-M2.5
- Kronos vs Laguna M.1
- Kronos vs Laguna S 2.1
- Kronos vs Laguna XS 2.1
- Kronos vs LFM2.5-2.6B
- Kronos vs Ling-3.0-tiny
- Kronos vs MiMo-V2.6 Distill Qwen 9B
- Kronos vs MiniCPM-o 4.5
- Kronos vs MiniCPM5-2B
- Kronos vs MiniMax-M2.7
- Kronos vs MiniMax-M3.1-Flash
- Kronos vs Muse Glimmer 30B
- Kronos vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Kronos vs Nemotron 3.5 Lightning 30B A3B
- Kronos vs Nemotron 3 Nano 30B A3B
- Kronos vs Nemotron 3 Nano 4B
- Kronos vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Kronos vs Nemotron 3 Super 120B A12B
- Kronos vs Nemotron 3 Ultra 550B A55B
- Kronos vs occamy-1.0
- Kronos vs Olmo 3 7B Think
- Kronos vs Ornith-1.5-35B-A3B
- Kronos vs Ornith-1.5-397B
- Kronos vs Ornith-1.5-9B
- Kronos vs Qwen3-30B-A3B-Instruct-2507
- Kronos vs Qwen3-4B-Instruct-2507
- Kronos vs Qwen3.5-0.8B
- Kronos vs Qwen3.5-122B-A10B
- Kronos vs Qwen3.5-2B
- Kronos vs Qwen3.5-397B-A17B
- Kronos vs Qwen3.5-4B
- Kronos vs Qwen3.5-9B
- Kronos vs Qwen3.6-27B
- Kronos vs Qwen3.6-35B-A3B
- Kronos vs Qwen3.8-27B
- Kronos vs Qwen3.8-Flash-Next
- Kronos vs Qwen3-Coder-30B-A3B-Instruct
- Kronos vs Qwen3-Coder-Next
- Kronos vs Qwen3-Omni-30B-A3B-Instruct
- Kronos vs Qwen3-VL-2B-Instruct
- Kronos vs Qwen3-VL-30B-A3B-Instruct
- Kronos vs Qwen3-VL-32B-Instruct
- Kronos vs Qwen3-VL-4B-Instruct
- Kronos vs Qwen3-VL-8B-Instruct
- Kronos vs Qwopus3.8-27B-Flash-V2
- Kronos vs Recursive Flint
- Kronos vs SmolLM3-3B
- Kronos vs Spark-X2.6-4B
- Kronos vs Swift 1.5 Qwen3.8-27B
- Kronos vs Swift 1.5 Qwen3.8-Flash-Next
- Kronos vs ThinkingCap (Qwen3.8 27B)
- 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 MiniMax-M3.1-Flash
- MiniMax-M2.5 vs Muse Glimmer 30B
- MiniMax-M2.5 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- 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 Recursive Flint
- 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/kronos-vs-minimax-m2-5.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/kronos.json·/api/v1/tools/minimax-m2-5.json - From a terminal
anchor compare kronos minimax-m2-5(the CLI) - Over MCP
compare_tools {"a": "kronos", "b": "minimax-m2-5"}at/mcp, no key