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

Kolibri-1 vs Spark-X2.6-4B

Kolibri-1 and Spark-X2.6-4B score within a point of each other on agent readiness, 61 (C) and 61 (C). Spark-X2.6-4B 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 50
  • Agent interface, 90 against 70
  • Documentation and upkeep, 70 against 41

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

Spark-X2.6-4B C

Best for Agents that want a tiny local model for tool loops and long documents on a laptop, CPU or small GPU.

Ahead on

  • Reach, 85 against 60

Watch for

No safety results and no agent or prompt-injection guidance

Score by category

CategoryWeight this runKolibri-1Spark-X2.6-4BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256085Spark-X2.6-4B +25
Risk20%206550Kolibri-1 +15
Agent interface10%109070Kolibri-1 +20
Documentation and upkeep10%107041Kolibri-1 +29
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactKolibri-1Spark-X2.6-4B
KindOpen-weight modelOpen-weight model
VendorAleph AlphaSparkLLM (XHToken)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-192026-10-20
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)3/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.

Spark-X2.6-4B

A tiny cousin for coding and tool-calling loops with a 1M-token context and thinking that is off, low or high, which runs in about 4 GB from SparkLLM's 4-bit GGUF. Use llama.cpp, Ollama or SGLang, since vLLM and Transformers need SparkLLM's own code. The risks are no safety work or agent guidance and a thin, two-day-old card.

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

Spark-X2.6-4B

  1. Quickest start is llama-server -hf XHToken/Spark-X2.6-4B-GGUF:Q4_K_M --jinja, which needs llama.cpp b10828 or later, or ollama run SparkLLM/Spark-X2.6-4B (8.2 GB, Ollama 0.34.1 or later)
  2. For parsed tool calls serve it with SGLang 0.5.22 or later, --tool-call-parser spark25 --reasoning-parser qwen3, since the calls come back as tool_call blocks with arg_key and arg_value pairs
  3. Thinking is on by default. Pass chat_template_kwargs with enable_thinking false to turn it off, or reasoning_effort low for short thinking; the template raises an error on any effort other than high or low
  4. SparkLLM's recommended sampling is temperature 1.0, top_p 0.95 and top_k -1
  5. The template always opens with its own default system line, with the effort instruction, and puts your system message after the tool list
  6. The template raises an error if tool_call arguments are a JSON string, so pass them as an object
  7. Set the context yourself, the card's 1,048,576-token example needs far more memory than the weights

Questions

Which is better for AI agents, Kolibri-1 or Spark-X2.6-4B?

Kolibri-1 and Spark-X2.6-4B score within a point of each other on agent readiness, 61 (C) and 61 (C). Spark-X2.6-4B leads on reach.

Other comparisons with Kolibri-1 or Spark-X2.6-4B

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.