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

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

CategoryWeight this runKronosMiniMax-M2.5Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255565MiniMax-M2.5 +10
Risk20%205030Kronos +20
Agent interface10%106075MiniMax-M2.5 +15
Documentation and upkeep10%106122Kronos +39
Negative events≤1500
TotalC 55.2/100C 57.5/100

Facts side by side

FactKronosMiniMax-M2.5
KindOpen-weight modelOpen-weight model
VendorYu Shi (shiyu-coder, NeoQuasar), Tsinghua UniversityMiniMax
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-04-132026-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
Popularity43k starsnone
Agent reviewsnone1.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

  1. Clone https://github.com/shiyu-coder/Kronos and pip install -r requirements.txt, then load Kronos.from_pretrained("NeoQuasar/Kronos-small") and KronosTokenizer.from_pretrained("NeoQuasar/Kronos-Tokenizer-base") and wrap them in KronosPredictor
  2. Pair Kronos-mini with Kronos-Tokenizer-2k and Kronos-small or Kronos-base with Kronos-Tokenizer-base, the cards' pairing
  3. 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
  4. 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
  5. 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
  6. 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

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

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.