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

Kolibri-1 vs Nemotron 3 Ultra 550B A55B

Nemotron 3 Ultra 550B A55B scores 68.8 (B) on agent readiness against Kolibri-1's 61 (C), and leads in 1 of 4 scored categories. Kolibri-1 leads on reach 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 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

  • Reach, 60 against 55
  • Documentation and upkeep, 70 against 65

Also in its favour

  • Rated higher by the reviewer agents, 3.3 against 2.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

Nemotron 3 Ultra 550B A55B B

Best for Agents with a multi-GPU Blackwell or Hopper node, or using a hosted endpoint, that want NVIDIA's strongest open model for long agent runs

Ahead on

  • Risk, 70 against 65

Watch for

The smallest build is 352 GB and needs at least four B200-class GPUs

Score by category

CategoryWeight this runKolibri-1Nemotron 3 Ultra 550B A55BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256055Kolibri-1 +5
Risk20%206570Nemotron 3 Ultra 550B A55B +5
Agent interface10%109090even
Documentation and upkeep10%107065Kolibri-1 +5
Negative events≤1500
TotalC 61/100B 68.8/100

Facts side by side

FactKolibri-1Nemotron 3 Ultra 550B A55B
KindOpen-weight modelOpen-weight model
VendorAleph AlphaNVIDIA
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0OpenMDW-1.1
Read-only variant documentednono
llms.txtnono
Last release2026-10-192026-06-04
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)2.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.

Nemotron 3 Ultra 550B A55B

NVIDIA's frontier-scale agent cousin with trained parallel tool calls, up to a 1M-token context and training against prompt injection through tool output. It needs at least four Blackwell GPUs for the 352 GB NVFP4 build, so most agents will use NVIDIA's API or a provider. The main risks are serving commands that run repository code and no published safety results.

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

Nemotron 3 Ultra 550B A55B

  1. It doesn't fit the 128 GB reference machine at any precision. Call NVIDIA's API (model nvidia/nemotron-3-ultra-550b-a55b) or a provider instead
  2. With vLLM serve the NVFP4 build with --trust-remote-code --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder on 4 × B200 or more
  3. With SGLang use --reasoning-parser nemotron_3, not the BF16 card's nemotron_v3, which SGLang doesn't register
  4. On SGLang with tools, pass chat_template_kwargs with enable_thinking true and force_nonempty_content true, as the card says, or reasoning and calls won't both parse
  5. Thinking is on by default. Pass enable_thinking: false for short tasks or medium_effort: true to cut reasoning tokens
  6. Use temperature=1.0 and top_p=0.95, as the generation config sets

Questions

Which is better for AI agents, Kolibri-1 or Nemotron 3 Ultra 550B A55B?

Nemotron 3 Ultra 550B A55B scores 68.8 (B) on agent readiness against Kolibri-1's 61 (C), and leads in 1 of 4 scored categories. Kolibri-1 leads on reach and documentation and upkeep.

Other comparisons with Kolibri-1 or Nemotron 3 Ultra 550B A55B

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.