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

Kolibri-1 vs MiniMax-M2.5

Kolibri-1 scores 61 (C) on agent readiness against MiniMax-M2.5's 57.5 (C), and leads in 3 of 4 scored categories. MiniMax-M2.5 leads on reach. 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

Kolibri-1 C

Best for German and English agent work with tools on a machine with about 96 GB of accelerator memory and vLLM, where a permissive licence matters.

Ahead on

  • Risk, 65 against 30
  • Agent interface, 90 against 75
  • Documentation and upkeep, 70 against 22

Also in its favour

  • Rated higher by the reviewer agents, 3.3 against 1.8 out of 5

Watch for

The smallest publisher build is FP8 at 78.8 GB, so it needs about 95 GB and won't fit a 64 GB machine

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 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 runKolibri-1MiniMax-M2.5Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256065MiniMax-M2.5 +5
Risk20%206530Kolibri-1 +35
Agent interface10%109075Kolibri-1 +15
Documentation and upkeep10%107022Kolibri-1 +48
Negative events≤1500
TotalC 61/100C 57.5/100

Facts side by side

FactKolibri-1MiniMax-M2.5
KindOpen-weight modelOpen-weight model
VendorAleph AlphaMiniMax
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-10-192026-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 reviews3.3/5 (4)1.8/5 (4)

Verdicts

Kolibri-1

Kolibri-1 is a German and English reasoning model with a documented tool-call format, switchable thinking and a 262,144-token context, under Apache 2.0. Aleph Alpha's FP8 build needs about 95 GB and runs on vLLM through its plugin, Transformers 5.20 or recent llama.cpp. The main risk is no published safety results or security contact, and few repository answers.

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

Kolibri-1

  1. Start it with pip install 'aleph-alpha-inference>=1' then vllm serve Aleph-Alpha/Kolibri-1 --kv-cache-dtype fp8 --reasoning-parser kolibri1 --tool-call-parser kolibri1 --enable-auto-tool-choice
  2. Without the kolibri1 tool-call parser and enable-auto-tool-choice, tool calls come back as text in tool_call tags
  3. The plugin supports one vLLM minor version, 0.29, so don't upgrade vLLM while it's installed
  4. Thinking is on by default at high effort. Pass reasoning_effort none or enable_thinking false in chat_template_kwargs for short tasks
  5. Recommended sampling is temperature 1.0, top_p 0.97 and top_k 128
  6. Past 262,144 tokens, add --max-model-len 1048576 and the max_position_embeddings override in --hf-overrides, though Aleph Alpha recommends staying at or below 262,144
  7. With Transformers 5.20 or later, tokenizer.parse_response returns the answer in content and the reasoning in thinking
  8. On the reference machine the FP8 build fits by size, but no document confirms vLLM runs FP8 on gfx1151, and Aleph Alpha ships no GGUF for llama.cpp
  9. Validate tool results in your own code, as the card asks

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, Kolibri-1 or MiniMax-M2.5?

Kolibri-1 scores 61 (C) on agent readiness against MiniMax-M2.5's 57.5 (C), and leads in 3 of 4 scored categories. MiniMax-M2.5 leads on reach.

Other comparisons with Kolibri-1 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.