Head to head · Open-weight models you run yourself · October 2026 research run
Kolibri-1 vs OTel-2.0-LLM-31B-IT
Kolibri-1 scores 61 (C) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 3 of 4 scored categories. Both do open-weight models you run yourself.
Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons
Which one, for what
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, 65 against 50
- Risk, 65 against 55
- Agent interface, 90 against 60
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
Best for Telecoms teams that want an open model for standards questions and RAG on their own hardware
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
BF16 only at 62.6 GB, with no GGUF or other quantised build from anyone we checked
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Agent interface Kolibri-1 +30
Kolibri-1 90
The chat template earns 20 as Jinja in tokenizer_config.json. The tool-calling format earns 25, because the card documents how tools are declared and how calls come back and names the kolibri1 parser for vLLM with a full example. Trained tool calling earns 20, from training on tool environments and a template built for several calls in one turn. Structured output earns 5, since the card claims it without saying how to ask. Reasoning control earns 10 for effort levels and an off switch per request, with the reasoning returned in a separate field. Context earns 10 for 262,144 tokens trained.
OTel-2.0-LLM-31B-IT 60
Chat template 20, chat_template.jinja in the repository, 19,300 characters, the publisher's own. Tool-calling format 10, only the template says how tools are declared and how calls come back. Trained tool calling 20, the template loops over tool_calls, so it renders several calls in one turn, and the card says the training mix included general-purpose agentic tool-calling examples, while none were specific to telecoms. Structured output 0, the card doesn't document JSON or JSON Schema output. Reasoning control 0, the card says the model wasn't trained to produce or consume Gemma's thought channel and answers directly, so there is no thinking to switch or budget. Context 10, 262,144 positions in the text config, the base's native context. 20 + 10 + 20 + 0 + 0 + 10 = 60.
Reach Kolibri-1 +15
Kolibri-1 65
Memory earns 10 because the smallest qualifying build is Aleph Alpha's own FP8 one at 78.8 GB, which comes to 94.6 GB with the fifth added and so fits only the reference machine's band. There is no publisher 4-bit or GGUF build and no Ollama library entry to bring it lower. Runtimes earn 20, for released Transformers 5.20.0, released llama.cpp builds from b11709, Ollama 0.40.14, which builds llama.cpp b11963 with kolibri1, and vLLM, through Aleph Alpha's plugin for 0.29 and natively in 0.33.0 through its Transformers backend. LM Studio's latest runtime predates kolibri1 and SGLang 0.5.23 has no model file. Builds earn 10 for the one FP8 quantisation beside BF16. Terms earn 15 for Apache 2.0 with no use policy. Download earns 10 because neither repository is gated. Hosted earns 0, since no inference provider is listed on the Hub and Aleph Alpha names no API serving it.
OTel-2.0-LLM-31B-IT 50
Memory 10, the publisher's only build is the BF16 safetensors, 62.55 GB for the 15 shards the index names, and 62.55 GB × 1.2 = 75.1 GB, above 64 GB and inside the reference machine's GPU share. Runtimes 15, the architecture is Gemma4ForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors files, three at 5 each. Builds 0, the publisher ships the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata, an OSI licence, with nothing added on the card. Download 10, gated is false on 10 November 2026, so the files download with no account or terms. Hosted 0, Hugging Face maps one inference provider, Featherless AI (live), short of the two the line needs. 10 + 15 + 0 + 15 + 10 + 0 = 50.
Risk Kolibri-1 +10
Kolibri-1 65
File safety earns 25 for safetensors only, with no repository code run on load. Provenance earns 15, for the Aleph-Alpha organisation the launch post links and a SHA-256 for every weight shard. Safety evaluation earns 0, because the card says refusals were measured and neither the card nor the technical report publishes results. Agent guidance earns 10, since the card says what the trained refusals cover and which safeguards to add around the model, without prompt-injection guidance. Licence risk earns the full 15 under unchanged Apache 2.0. The security programme earns 0, as no contact, policy or advisories were found and security.txt answered 403 on 3 November, so it is scored as absent and left open.
OTel-2.0-LLM-31B-IT 55
File safety 25, safetensors only, with no .bin, .pt or .pth files and no Python files. Provenance 5, the files sit in a personal account, farbodtavakkoli, not in an organisation AT&T's or GSMA's site links to: GSMA's article names AT&T as the releaser without linking the repository, and the GitHub repository that links it is the same person's (0). Safety evaluation 0, no safety results on the card. Agent guidance 10, the card says what the trained abstention covers (declining when context is missing, irrelevant or insufficient) and what to add around the model for agent use: an external tool runtime, validated tool schemas, permission controls, audit logging, safeguards and human review. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, nothing is added on the card, and the licence link resolves (200 on 10 November 2026). Security programme 0, no way to report a flaw found. 25 + 5 + 0 + 10 + 15 + 0 = 55.
Score by category
| Category | Weight this run | Kolibri-1 | OTel-2.0-LLM-31B-IT | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 65 | 50 | Kolibri-1 +15 |
| Risk | 20%20 | 65 | 55 | Kolibri-1 +10 |
| Agent interface | 10%10 | 90 | 60 | Kolibri-1 +30 |
| Documentation and upkeep | 10%10 | 70 | 74 | OTel-2.0-LLM-31B-IT +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 56.8/100 |
Facts side by side
| Fact | Kolibri-1 | OTel-2.0-LLM-31B-IT |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Aleph Alpha | AT&T (Open Telco AI) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-19 | 2026-11-01 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 3.3/5 (4) | none |
How the scores have moved
OTel-2.0-LLM-31B-IT
No score change since it was listed.
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 and Transformers 5.20; llama.cpp and Ollama 0.40.14 need a GGUF. The main risk is no published safety results or security contact, and few repository answers.
OTel-2.0-LLM-31B-IT
A real telecoms post-training of Gemma 4 31B IT with an unusually candid card on what was and wasn't trained. It fits a 128 GB machine in BF16 only, with no quantised build, sits in a personal account, and its weights have been replaced in place. Tool-call format, structured output and safety results aren't documented.
Before you call either
Kolibri-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
- Without the kolibri1 tool-call parser and enable-auto-tool-choice, tool calls come back as text in tool_call tags
- The plugin supports one vLLM minor version, 0.29. vLLM 0.33.0 loads the model without it, but has no kolibri1 tool or reasoning parser
- Thinking is on by default at high effort. Pass reasoning_effort none or enable_thinking false in chat_template_kwargs for short tasks
- Recommended sampling is temperature 1.0, top_p 0.97 and top_k 128
- 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
- With Transformers 5.20 or later, tokenizer.parse_response returns the answer in content and the reasoning in thinking
- 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 or Ollama
- Validate tool results in your own code, as the card asks
OTel-2.0-LLM-31B-IT
- Download the 15 shards the index names, not the whole repository, which is twice the size
- Pin a revision. The card says the weights may change under the same name
- Serve it with vLLM 0.19.0 or later and the repository's own chat template, not Gemma 4's
- Send no thinking flags. It answers directly and wasn't trained on Gemma's thought channel
- Use it as the generation stage of a RAG pipeline over telecom standards, with source attribution and human review
- Don't use it to run network tools unattended. The card says that hasn't been evaluated
Questions
Which is better for AI agents, Kolibri-1 or OTel-2.0-LLM-31B-IT?
Kolibri-1 scores 61 (C) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 3 of 4 scored categories.
Other comparisons with Kolibri-1 or OTel-2.0-LLM-31B-IT
- Agents-A1-4B vs Kolibri-1
- Agents-A1-4B vs OTel-2.0-LLM-31B-IT
- Apertus v1.5 8B vs Kolibri-1
- Apertus v1.5 8B vs OTel-2.0-LLM-31B-IT
- Apodex-1.1-mini vs Kolibri-1
- Apodex-1.1-mini vs OTel-2.0-LLM-31B-IT
- Arete-27B vs Kolibri-1
- Arete-27B vs OTel-2.0-LLM-31B-IT
- BigBang-v1 vs Kolibri-1
- BigBang-v1 vs OTel-2.0-LLM-31B-IT
- Carbon-X vs Kolibri-1
- Carbon-X vs OTel-2.0-LLM-31B-IT
- Cola2 vs Kolibri-1
- Cola2 vs OTel-2.0-LLM-31B-IT
- Cosmos-Reason2-2B vs Kolibri-1
- Cosmos-Reason2-2B vs OTel-2.0-LLM-31B-IT
- Darwin-36B-Opus vs Kolibri-1
- Darwin-36B-Opus vs OTel-2.0-LLM-31B-IT
- DeepSeek-V3.2 vs Kolibri-1
- DeepSeek-V3.2 vs OTel-2.0-LLM-31B-IT
- DeepSeek V4.1 Flash vs Kolibri-1
- DeepSeek V4.1 Flash vs OTel-2.0-LLM-31B-IT
- DeepSeek-V4-Flash-0731 vs Kolibri-1
- DeepSeek-V4-Flash-0731 vs OTel-2.0-LLM-31B-IT
- Devstral Small 2 vs Kolibri-1
- Devstral Small 2 vs OTel-2.0-LLM-31B-IT
- DiffusionGemma 26B A4B IT vs Kolibri-1
- DiffusionGemma 26B A4B IT vs OTel-2.0-LLM-31B-IT
- EXAONE 4.5 33B vs Kolibri-1
- EXAONE 4.5 33B vs OTel-2.0-LLM-31B-IT
- Gemma 4 12B IT vs Kolibri-1
- Gemma 4 12B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 26B A4B IT vs Kolibri-1
- Gemma 4 26B A4B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 31B IT vs Kolibri-1
- Gemma 4 31B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 E2B IT vs Kolibri-1
- Gemma 4 E2B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 E4B IT vs Kolibri-1
- Gemma 4 E4B IT vs OTel-2.0-LLM-31B-IT
- GLM-4.5-Air vs Kolibri-1
- GLM-4.5-Air vs OTel-2.0-LLM-31B-IT
- GLM-4.7-Flash vs Kolibri-1
- GLM-4.7-Flash vs OTel-2.0-LLM-31B-IT
- GLM-5.3-Flash vs Kolibri-1
- GLM-5.3-Flash vs OTel-2.0-LLM-31B-IT
- GLM-5.3 vs Kolibri-1
- GLM-5.3 vs OTel-2.0-LLM-31B-IT
- gpt-oss-120b vs Kolibri-1
- gpt-oss-120b vs OTel-2.0-LLM-31B-IT
- gpt-oss-20b vs Kolibri-1
- gpt-oss-20b vs OTel-2.0-LLM-31B-IT
- Granite 4.2 30B vs Kolibri-1
- Granite 4.2 30B vs OTel-2.0-LLM-31B-IT
- Granite 4.2 3B vs Kolibri-1
- Granite 4.2 3B vs OTel-2.0-LLM-31B-IT
- Granite 4.2 8B vs Kolibri-1
- Granite 4.2 8B vs OTel-2.0-LLM-31B-IT
- Hy-Memory-30B-A3B vs Kolibri-1
- Hy-Memory-30B-A3B vs OTel-2.0-LLM-31B-IT
- Hy3 vs Kolibri-1
- Hy3 vs OTel-2.0-LLM-31B-IT
- Inkling-Small vs Kolibri-1
- Inkling-Small vs OTel-2.0-LLM-31B-IT
- Inkling vs Kolibri-1
- Inkling vs OTel-2.0-LLM-31B-IT
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Kolibri-1
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs OTel-2.0-LLM-31B-IT
- Kimi K3.1 Pro vs Kolibri-1
- Kimi K3.1 Pro vs OTel-2.0-LLM-31B-IT
- Kimi K3 vs Kolibri-1
- Kimi K3 vs OTel-2.0-LLM-31B-IT
- Kolibri-1 vs Kronos
- Kolibri-1 vs Laguna M.1
- Kolibri-1 vs Laguna S 2.1
- Kolibri-1 vs Laguna XS 2.1
- Kolibri-1 vs LBS-27B
- Kolibri-1 vs LFM2.5-2.6B
- Kolibri-1 vs LFM3-1.7B
- Kolibri-1 vs LFM3-Audio-2B
- Kolibri-1 vs LFM3-Omni-2B
- Kolibri-1 vs LFM3-VL-2B
- Kolibri-1 vs Ling-3.0-tiny
- Kolibri-1 vs Ling-3.1-flash-1019
- Kolibri-1 vs LongCat-2.5
- Kolibri-1 vs MiMo-V2.6 Distill Qwen 9B
- Kolibri-1 vs MiMo-V2.6-Flash-RL
- Kolibri-1 vs MiniCPM-o 4.5
- Kolibri-1 vs MiniCPM-V 4.7 1B
- Kolibri-1 vs MiniCPM-V 4.7 35B-A3B
- Kolibri-1 vs MiniCPM5-2B
- Kolibri-1 vs MiniMax-M2.5
- Kolibri-1 vs MiniMax-M2.7
- Kolibri-1 vs MiniMax-M3.1-Flash
- Kolibri-1 vs Mistral Large 4
- Kolibri-1 vs Muse Glimmer 30B
- Kolibri-1 vs Nanbeige4.2-3B
- Kolibri-1 vs Nanbeige4.3-33B
- Kolibri-1 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Kolibri-1 vs Nemotron 3.5 Lightning 30B A3B
- Kolibri-1 vs Nemotron 3 Nano 30B A3B
- Kolibri-1 vs Nemotron 3 Nano 4B
- Kolibri-1 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Kolibri-1 vs Nemotron 3 Super 120B A12B
- Kolibri-1 vs Nemotron 3 Ultra 550B A55B
- Kolibri-1 vs North Mini Code 1.0
- Kolibri-1 vs occamy-1.0
- Kolibri-1 vs Olmo 3 7B Think
- Kolibri-1 vs Ornith-1.5-122B
- Kolibri-1 vs Ornith-1.5-35B-A3B
- Kolibri-1 vs Ornith-1.5-397B
- Kolibri-1 vs Ornith-1.5-9B
- Kolibri-1 vs Qwen-AgentWorld-35B-A3B
- Kolibri-1 vs Qwen3-30B-A3B-Instruct-2507
- Kolibri-1 vs Qwen3-4B-Instruct-2507
- Kolibri-1 vs Qwen3.5-0.8B
- Kolibri-1 vs Qwen3.5-122B-A10B
- Kolibri-1 vs Qwen3.5-2B
- Kolibri-1 vs Qwen3.5-397B-A17B
- Kolibri-1 vs Qwen3.5-4B
- Kolibri-1 vs Qwen3.5-9B
- Kolibri-1 vs Qwen3.6-27B
- Kolibri-1 vs Qwen3.6-35B-A3B
- Kolibri-1 vs Qwen3.8-27B
- Kolibri-1 vs Qwen3.8-Flash-Next
- Kolibri-1 vs Qwen3-Coder-30B-A3B-Instruct
- Kolibri-1 vs Qwen3-Coder-Next
- Kolibri-1 vs Qwen3-Omni-30B-A3B-Instruct
- Kolibri-1 vs Qwen3-VL-2B-Instruct
- Kolibri-1 vs Qwen3-VL-30B-A3B-Instruct
- Kolibri-1 vs Qwen3-VL-32B-Instruct
- Kolibri-1 vs Qwen3-VL-4B-Instruct
- Kolibri-1 vs Qwen3-VL-8B-Instruct
- Kolibri-1 vs Qwopus3.8-27B-Flash-V2
- Kolibri-1 vs Recursive Flint
- Kolibri-1 vs Ripple-65B Preview
- Kolibri-1 vs SenseNova-Loop-9B-Preview
- Kolibri-1 vs SmolLM3-3B
- Kolibri-1 vs Spark-X2.6-4B
- Kolibri-1 vs Step 3.7 Flash
- Kolibri-1 vs Swift 1.5 Qwen3.8-27B
- Kolibri-1 vs Swift 1.5 Qwen3.8-Flash-Next
- Kolibri-1 vs ThinkingCap (Qwen3.8 27B)
- Kolibri-1 vs Baidu Unlimited-OCR-2
- Kolibri-1 vs WeVisOne-VL-2B
- Kolibri-1 vs WeVisOne-VL-4B
- Kolibri-1 vs ZAYA1-8B
- Kronos vs OTel-2.0-LLM-31B-IT
- Laguna M.1 vs OTel-2.0-LLM-31B-IT
- Laguna S 2.1 vs OTel-2.0-LLM-31B-IT
- Laguna XS 2.1 vs OTel-2.0-LLM-31B-IT
- LBS-27B vs OTel-2.0-LLM-31B-IT
- LFM2.5-2.6B vs OTel-2.0-LLM-31B-IT
- LFM3-1.7B vs OTel-2.0-LLM-31B-IT
- LFM3-Audio-2B vs OTel-2.0-LLM-31B-IT
- LFM3-Omni-2B vs OTel-2.0-LLM-31B-IT
- LFM3-VL-2B vs OTel-2.0-LLM-31B-IT
- Ling-3.0-tiny vs OTel-2.0-LLM-31B-IT
- Ling-3.1-flash-1019 vs OTel-2.0-LLM-31B-IT
- LongCat-2.5 vs OTel-2.0-LLM-31B-IT
- MiMo-V2.6 Distill Qwen 9B vs OTel-2.0-LLM-31B-IT
- MiMo-V2.6-Flash-RL vs OTel-2.0-LLM-31B-IT
- MiniCPM-o 4.5 vs OTel-2.0-LLM-31B-IT
- MiniCPM-V 4.7 1B vs OTel-2.0-LLM-31B-IT
- MiniCPM-V 4.7 35B-A3B vs OTel-2.0-LLM-31B-IT
- MiniCPM5-2B vs OTel-2.0-LLM-31B-IT
- MiniMax-M2.5 vs OTel-2.0-LLM-31B-IT
- MiniMax-M2.7 vs OTel-2.0-LLM-31B-IT
- MiniMax-M3.1-Flash vs OTel-2.0-LLM-31B-IT
- Mistral Large 4 vs OTel-2.0-LLM-31B-IT
- Muse Glimmer 30B vs OTel-2.0-LLM-31B-IT
- Nanbeige4.2-3B vs OTel-2.0-LLM-31B-IT
- Nanbeige4.3-33B vs OTel-2.0-LLM-31B-IT
- NVIDIA Nemotron 3.5 Bolt E4B 4GB vs OTel-2.0-LLM-31B-IT
- Nemotron 3.5 Lightning 30B A3B vs OTel-2.0-LLM-31B-IT
- Nemotron 3 Nano 30B A3B vs OTel-2.0-LLM-31B-IT
- Nemotron 3 Nano 4B vs OTel-2.0-LLM-31B-IT
- Nemotron 3 Nano Omni 30B A3B Reasoning vs OTel-2.0-LLM-31B-IT
- Nemotron 3 Super 120B A12B vs OTel-2.0-LLM-31B-IT
- Nemotron 3 Ultra 550B A55B vs OTel-2.0-LLM-31B-IT
- North Mini Code 1.0 vs OTel-2.0-LLM-31B-IT
- occamy-1.0 vs OTel-2.0-LLM-31B-IT
- Olmo 3 7B Think vs OTel-2.0-LLM-31B-IT
- Ornith-1.5-122B vs OTel-2.0-LLM-31B-IT
- Ornith-1.5-35B-A3B vs OTel-2.0-LLM-31B-IT
- Ornith-1.5-397B vs OTel-2.0-LLM-31B-IT
- Ornith-1.5-9B vs OTel-2.0-LLM-31B-IT
- OTel-2.0-LLM-31B-IT vs Qwen-AgentWorld-35B-A3B
- OTel-2.0-LLM-31B-IT vs Qwen3-30B-A3B-Instruct-2507
- OTel-2.0-LLM-31B-IT vs Qwen3-4B-Instruct-2507
- OTel-2.0-LLM-31B-IT vs Qwen3.5-0.8B
- OTel-2.0-LLM-31B-IT vs Qwen3.5-122B-A10B
- OTel-2.0-LLM-31B-IT vs Qwen3.5-2B
- OTel-2.0-LLM-31B-IT vs Qwen3.5-397B-A17B
- OTel-2.0-LLM-31B-IT vs Qwen3.5-4B
- OTel-2.0-LLM-31B-IT vs Qwen3.5-9B
- OTel-2.0-LLM-31B-IT vs Qwen3.6-27B
- OTel-2.0-LLM-31B-IT vs Qwen3.6-35B-A3B
- OTel-2.0-LLM-31B-IT vs Qwen3.8-27B
- OTel-2.0-LLM-31B-IT vs Qwen3.8-Flash-Next
- OTel-2.0-LLM-31B-IT vs Qwen3-Coder-30B-A3B-Instruct
- OTel-2.0-LLM-31B-IT vs Qwen3-Coder-Next
- OTel-2.0-LLM-31B-IT vs Qwen3-Omni-30B-A3B-Instruct
- OTel-2.0-LLM-31B-IT vs Qwen3-VL-2B-Instruct
- OTel-2.0-LLM-31B-IT vs Qwen3-VL-30B-A3B-Instruct
- OTel-2.0-LLM-31B-IT vs Qwen3-VL-32B-Instruct
- OTel-2.0-LLM-31B-IT vs Qwen3-VL-4B-Instruct
- OTel-2.0-LLM-31B-IT vs Qwen3-VL-8B-Instruct
- OTel-2.0-LLM-31B-IT vs Qwopus3.8-27B-Flash-V2
- OTel-2.0-LLM-31B-IT vs Recursive Flint
- OTel-2.0-LLM-31B-IT vs Ripple-65B Preview
- OTel-2.0-LLM-31B-IT vs SenseNova-Loop-9B-Preview
- OTel-2.0-LLM-31B-IT vs SmolLM3-3B
- OTel-2.0-LLM-31B-IT vs Spark-X2.6-4B
- OTel-2.0-LLM-31B-IT vs Step 3.7 Flash
- OTel-2.0-LLM-31B-IT vs Swift 1.5 Qwen3.8-27B
- OTel-2.0-LLM-31B-IT vs Swift 1.5 Qwen3.8-Flash-Next
- OTel-2.0-LLM-31B-IT vs ThinkingCap (Qwen3.8 27B)
- OTel-2.0-LLM-31B-IT vs Baidu Unlimited-OCR-2
- OTel-2.0-LLM-31B-IT vs WeVisOne-VL-2B
- OTel-2.0-LLM-31B-IT vs WeVisOne-VL-4B
- OTel-2.0-LLM-31B-IT vs ZAYA1-8B
Machine-readable
- This page as Markdown
/compare/kolibri-1-vs-otel-2-0-llm-31b-it.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/kolibri-1.json·/api/v1/tools/otel-2-0-llm-31b-it.json - From a terminal
anchor compare kolibri-1 otel-2-0-llm-31b-it(the CLI) - Over MCP
compare_tools {"a": "kolibri-1", "b": "otel-2-0-llm-31b-it"}at/mcp, no key