Head to head · Open-weight models you run yourself · October 2026 research run
LFM2.5-2.6B vs OTel-2.0-LLM-31B-IT
OTel-2.0-LLM-31B-IT scores 56.8 (C) on agent readiness against LFM2.5-2.6B's 50.3 (D), and leads in 2 of 4 scored categories. LFM2.5-2.6B leads on reach and agent interface. 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 Agents that want a small local helper for tool calls, extraction and RAG on a laptop, phone or CPU, at organisations under the licence's revenue threshold
Ahead on
- Reach, 90 against 50
- Agent interface, 75 against 60
Watch for
Liquid lists it as deprecated, replaced by LFM3-1.7B; deprecated models stay downloadable but get no further updates
Best for Telecoms teams that want an open model for standards questions and RAG on their own hardware
Ahead on
- Risk, 55 against 50
- Documentation and upkeep, 74 against 57
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.
Reach LFM2.5-2.6B +40
LFM2.5-2.6B 90
Memory earns the full 30, since Liquid's own 4-bit GGUF is 1.59 GB and fits 8 GB with room to spare. Runtimes earn 25, with the lfm2 architecture in released llama.cpp, vLLM, SGLang and Transformers, and in Ollama through the llama.cpp version it pins. Builds earn 15 for Liquid's own GGUF, MLX and ONNX builds at many precisions. Terms earn 10, a custom licence that is free for commercial use under $10M of annual revenue. Download earns 10, with no gate. Hosted earns nothing, as Hugging Face maps no inference provider and Liquid's docs list no hosted API for 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.
Documentation and upkeep OTel-2.0-LLM-31B-IT +17
LFM2.5-2.6B 57
The model card earns 17, with everything but a knowledge cut-off. Training data earns 5 for a general description without a cut-off. The last change earns 20, a card commit on 3 November 2026 naming LFM3-1.7B as the new version. Responsiveness earns 5, with Liquid replies in 2 of 16 discussions. Version policy earns 5, as Liquid now lists the model as deprecated with a replacement but no date. File health earns 5, since the files agree but a report about the card waits without a reply.
OTel-2.0-LLM-31B-IT 74
Model card 14, Intended use, a long limitations section, the architecture and training method, the parameters (31B) and the language (English) are on the card. Training data 15, the card names the sources (3GPP, ETSI, ITU, GSMA, CAMARA, O-RAN and TM Forum material provided by GSMA), the overall sizes (15 billion raw tokens, over 1 trillion processed, about 440 billion used), the mix of example types and the processing tool, and lists what was left out. Last change 20, the last commit, on 1 November 2026, updated the card's links, resources, citation and contacts, nine days before this check. Responsiveness 20, Of the 3 discussions that aren't pull requests (7 August to 28 October 2026), 2 have a reply from the repository's owner, which is most. Version policy 0, the weights were replaced in place: uploads on 27 July, 3 August and 1 September 2026 under one name, with a standing notice on the card that they may change and that users should pin a revision, and no dated note of what changed. File health 5, the card describes 15 shards of about 62.6 GB while the repository still holds an earlier 14-shard set beside them, 126.8 GB in all. 14 + 15 + 20 + 20 + 0 + 5 = 74.
Agent interface LFM2.5-2.6B +15
LFM2.5-2.6B 75
The chat template earns 20 for chat_template.jinja in the repository. The tool-calling format earns 25, as Liquid's card and tool-use page say how tools go in and how calls come back, and its vLLM and SGLang pages name the lfm2 parser. Trained tool calling earns 20, with several calls in one Python list and agentic RL inside agent harnesses. Structured output earns nothing, as JSON output isn't documented for the model. Reasoning control earns nothing, since the model always thinks. Context earns 10 for 131,072 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.
Risk OTel-2.0-LLM-31B-IT +5
LFM2.5-2.6B 50
File safety earns 25, safetensors and GGUF only, and nothing from the repository runs to load it or build prompts. Provenance earns 15, files in the LiquidAI organisation Liquid links to, with a checksum for every file. Safety evaluation and agent guidance earn nothing, since Liquid publishes neither. Licence risk earns 10, losing 5 for the revenue threshold, with no use policy and no change since release. The security programme earns nothing, since no security.txt, disclosure policy or security contact was found.
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 | LFM2.5-2.6B | OTel-2.0-LLM-31B-IT | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 90 | 50 | LFM2.5-2.6B +40 |
| Risk | 20%20 | 50 | 55 | OTel-2.0-LLM-31B-IT +5 |
| Agent interface | 10%10 | 75 | 60 | LFM2.5-2.6B +15 |
| Documentation and upkeep | 10%10 | 57 | 74 | OTel-2.0-LLM-31B-IT +17 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50.3/100 | C 56.8/100 |
Facts side by side
| Fact | LFM2.5-2.6B | OTel-2.0-LLM-31B-IT |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Liquid AI | AT&T (Open Telco AI) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | LFM Open License v1.0 (free commercial use below $10M annual revenue) | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-03 | 2026-11-01 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 2.5/5 (4) | none |
How the scores have moved
OTel-2.0-LLM-31B-IT
No score change since it was listed.
Verdicts
LFM2.5-2.6B
A small, fast model for tool calls, extraction and long-context steps on a laptop or phone, which Liquid now lists as deprecated in favour of LFM3-1.7B. Liquid's own 4-bit build is 1.6 GB and five common runtimes run it. It always thinks, and organisations over $10M of revenue need another licence. There are no safety results or security contact.
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
LFM2.5-2.6B
- Quickest start is
ollama run LiquidAI/lfm2.5-2.6b, 1.7 GB, orllama-cli -hf LiquidAI/LFM2.5-2.6B-GGUF - With vLLM or SGLang pass
--tool-call-parser lfm2; for vLLM add--reasoning-parser qwen3so the thinking comes back separately - Sample at temperature 0.1, top_k 50 and repetition_penalty 1.1, as the card and generation_config.json set
- Put tools in the system prompt as
List of tools: [...]JSON, or pass tools to apply_chat_template; calls come back as a Python list of function calls, and the system prompt can ask for JSON calls instead - Leave max_tokens unset or generous, since a low cap cuts the reasoning off mid-thought
- Earlier thinking is dropped from the prompt unless
preserve_thinkingis true - Liquid's 328M LFM2.5-2.6B-DSpark drafter speeds decoding about 2.6 times in SGLang and on Apple silicon, per Liquid
- Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
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, LFM2.5-2.6B or OTel-2.0-LLM-31B-IT?
OTel-2.0-LLM-31B-IT scores 56.8 (C) on agent readiness against LFM2.5-2.6B's 50.3 (D), and leads in 2 of 4 scored categories. LFM2.5-2.6B leads on reach and agent interface.
Other comparisons with LFM2.5-2.6B or OTel-2.0-LLM-31B-IT
- Agents-A1-4B vs LFM2.5-2.6B
- Agents-A1-4B vs OTel-2.0-LLM-31B-IT
- Apertus v1.5 8B vs LFM2.5-2.6B
- Apertus v1.5 8B vs OTel-2.0-LLM-31B-IT
- Apodex-1.1-mini vs LFM2.5-2.6B
- Apodex-1.1-mini vs OTel-2.0-LLM-31B-IT
- Arete-27B vs LFM2.5-2.6B
- Arete-27B vs OTel-2.0-LLM-31B-IT
- BigBang-v1 vs LFM2.5-2.6B
- BigBang-v1 vs OTel-2.0-LLM-31B-IT
- Carbon-X vs LFM2.5-2.6B
- Carbon-X vs OTel-2.0-LLM-31B-IT
- Cola2 vs LFM2.5-2.6B
- Cola2 vs OTel-2.0-LLM-31B-IT
- Cosmos-Reason2-2B vs LFM2.5-2.6B
- Cosmos-Reason2-2B vs OTel-2.0-LLM-31B-IT
- Darwin-36B-Opus vs LFM2.5-2.6B
- Darwin-36B-Opus vs OTel-2.0-LLM-31B-IT
- DeepSeek-V3.2 vs LFM2.5-2.6B
- DeepSeek-V3.2 vs OTel-2.0-LLM-31B-IT
- DeepSeek V4.1 Flash vs LFM2.5-2.6B
- DeepSeek V4.1 Flash vs OTel-2.0-LLM-31B-IT
- DeepSeek-V4-Flash-0731 vs LFM2.5-2.6B
- DeepSeek-V4-Flash-0731 vs OTel-2.0-LLM-31B-IT
- Devstral Small 2 vs LFM2.5-2.6B
- Devstral Small 2 vs OTel-2.0-LLM-31B-IT
- DiffusionGemma 26B A4B IT vs LFM2.5-2.6B
- DiffusionGemma 26B A4B IT vs OTel-2.0-LLM-31B-IT
- EXAONE 4.5 33B vs LFM2.5-2.6B
- EXAONE 4.5 33B vs OTel-2.0-LLM-31B-IT
- Gemma 4 12B IT vs LFM2.5-2.6B
- Gemma 4 12B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 26B A4B IT vs LFM2.5-2.6B
- Gemma 4 26B A4B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 31B IT vs LFM2.5-2.6B
- Gemma 4 31B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 E2B IT vs LFM2.5-2.6B
- Gemma 4 E2B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 E4B IT vs LFM2.5-2.6B
- Gemma 4 E4B IT vs OTel-2.0-LLM-31B-IT
- GLM-4.5-Air vs LFM2.5-2.6B
- GLM-4.5-Air vs OTel-2.0-LLM-31B-IT
- GLM-4.7-Flash vs LFM2.5-2.6B
- GLM-4.7-Flash vs OTel-2.0-LLM-31B-IT
- GLM-5.3-Flash vs LFM2.5-2.6B
- GLM-5.3-Flash vs OTel-2.0-LLM-31B-IT
- GLM-5.3 vs LFM2.5-2.6B
- GLM-5.3 vs OTel-2.0-LLM-31B-IT
- gpt-oss-120b vs LFM2.5-2.6B
- gpt-oss-120b vs OTel-2.0-LLM-31B-IT
- gpt-oss-20b vs LFM2.5-2.6B
- gpt-oss-20b vs OTel-2.0-LLM-31B-IT
- Granite 4.2 30B vs LFM2.5-2.6B
- Granite 4.2 30B vs OTel-2.0-LLM-31B-IT
- Granite 4.2 3B vs LFM2.5-2.6B
- Granite 4.2 3B vs OTel-2.0-LLM-31B-IT
- Granite 4.2 8B vs LFM2.5-2.6B
- Granite 4.2 8B vs OTel-2.0-LLM-31B-IT
- Hy-Memory-30B-A3B vs LFM2.5-2.6B
- Hy-Memory-30B-A3B vs OTel-2.0-LLM-31B-IT
- Hy3 vs LFM2.5-2.6B
- Hy3 vs OTel-2.0-LLM-31B-IT
- Inkling-Small vs LFM2.5-2.6B
- Inkling-Small vs OTel-2.0-LLM-31B-IT
- Inkling vs LFM2.5-2.6B
- Inkling vs OTel-2.0-LLM-31B-IT
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM2.5-2.6B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs OTel-2.0-LLM-31B-IT
- Kimi K3.1 Pro vs LFM2.5-2.6B
- Kimi K3.1 Pro vs OTel-2.0-LLM-31B-IT
- Kimi K3 vs LFM2.5-2.6B
- Kimi K3 vs OTel-2.0-LLM-31B-IT
- Kolibri-1 vs LFM2.5-2.6B
- Kolibri-1 vs OTel-2.0-LLM-31B-IT
- Kronos vs LFM2.5-2.6B
- Kronos vs OTel-2.0-LLM-31B-IT
- Laguna M.1 vs LFM2.5-2.6B
- Laguna M.1 vs OTel-2.0-LLM-31B-IT
- Laguna S 2.1 vs LFM2.5-2.6B
- Laguna S 2.1 vs OTel-2.0-LLM-31B-IT
- Laguna XS 2.1 vs LFM2.5-2.6B
- Laguna XS 2.1 vs OTel-2.0-LLM-31B-IT
- LBS-27B vs LFM2.5-2.6B
- LBS-27B vs OTel-2.0-LLM-31B-IT
- LFM2.5-2.6B vs LFM3-1.7B
- LFM2.5-2.6B vs LFM3-Audio-2B
- LFM2.5-2.6B vs LFM3-Omni-2B
- LFM2.5-2.6B vs LFM3-VL-2B
- LFM2.5-2.6B vs Ling-3.0-tiny
- LFM2.5-2.6B vs Ling-3.1-flash-1019
- LFM2.5-2.6B vs LongCat-2.5
- LFM2.5-2.6B vs MiMo-V2.6 Distill Qwen 9B
- LFM2.5-2.6B vs MiMo-V2.6-Flash-RL
- LFM2.5-2.6B vs MiniCPM-o 4.5
- LFM2.5-2.6B vs MiniCPM-V 4.7 1B
- LFM2.5-2.6B vs MiniCPM-V 4.7 35B-A3B
- LFM2.5-2.6B vs MiniCPM5-2B
- LFM2.5-2.6B vs MiniMax-M2.5
- LFM2.5-2.6B vs MiniMax-M2.7
- LFM2.5-2.6B vs MiniMax-M3.1-Flash
- LFM2.5-2.6B vs Mistral Large 4
- LFM2.5-2.6B vs Muse Glimmer 30B
- LFM2.5-2.6B vs Nanbeige4.2-3B
- LFM2.5-2.6B vs Nanbeige4.3-33B
- LFM2.5-2.6B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- LFM2.5-2.6B vs Nemotron 3.5 Lightning 30B A3B
- LFM2.5-2.6B vs Nemotron 3 Nano 30B A3B
- LFM2.5-2.6B vs Nemotron 3 Nano 4B
- LFM2.5-2.6B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- LFM2.5-2.6B vs Nemotron 3 Super 120B A12B
- LFM2.5-2.6B vs Nemotron 3 Ultra 550B A55B
- LFM2.5-2.6B vs North Mini Code 1.0
- LFM2.5-2.6B vs occamy-1.0
- LFM2.5-2.6B vs Olmo 3 7B Think
- LFM2.5-2.6B vs Ornith-1.5-122B
- LFM2.5-2.6B vs Ornith-1.5-35B-A3B
- LFM2.5-2.6B vs Ornith-1.5-397B
- LFM2.5-2.6B vs Ornith-1.5-9B
- LFM2.5-2.6B vs Qwen-AgentWorld-35B-A3B
- LFM2.5-2.6B vs Qwen3-30B-A3B-Instruct-2507
- LFM2.5-2.6B vs Qwen3-4B-Instruct-2507
- LFM2.5-2.6B vs Qwen3.5-0.8B
- LFM2.5-2.6B vs Qwen3.5-122B-A10B
- LFM2.5-2.6B vs Qwen3.5-2B
- LFM2.5-2.6B vs Qwen3.5-397B-A17B
- LFM2.5-2.6B vs Qwen3.5-4B
- LFM2.5-2.6B vs Qwen3.5-9B
- LFM2.5-2.6B vs Qwen3.6-27B
- LFM2.5-2.6B vs Qwen3.6-35B-A3B
- LFM2.5-2.6B vs Qwen3.8-27B
- LFM2.5-2.6B vs Qwen3.8-Flash-Next
- LFM2.5-2.6B vs Qwen3-Coder-30B-A3B-Instruct
- LFM2.5-2.6B vs Qwen3-Coder-Next
- LFM2.5-2.6B vs Qwen3-Omni-30B-A3B-Instruct
- LFM2.5-2.6B vs Qwen3-VL-2B-Instruct
- LFM2.5-2.6B vs Qwen3-VL-30B-A3B-Instruct
- LFM2.5-2.6B vs Qwen3-VL-32B-Instruct
- LFM2.5-2.6B vs Qwen3-VL-4B-Instruct
- LFM2.5-2.6B vs Qwen3-VL-8B-Instruct
- LFM2.5-2.6B vs Qwopus3.8-27B-Flash-V2
- LFM2.5-2.6B vs Recursive Flint
- LFM2.5-2.6B vs Ripple-65B Preview
- LFM2.5-2.6B vs SenseNova-Loop-9B-Preview
- LFM2.5-2.6B vs SmolLM3-3B
- LFM2.5-2.6B vs Spark-X2.6-4B
- LFM2.5-2.6B vs Step 3.7 Flash
- LFM2.5-2.6B vs Swift 1.5 Qwen3.8-27B
- LFM2.5-2.6B vs Swift 1.5 Qwen3.8-Flash-Next
- LFM2.5-2.6B vs ThinkingCap (Qwen3.8 27B)
- LFM2.5-2.6B vs Baidu Unlimited-OCR-2
- LFM2.5-2.6B vs WeVisOne-VL-2B
- LFM2.5-2.6B vs WeVisOne-VL-4B
- LFM2.5-2.6B vs ZAYA1-8B
- 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/lfm2-5-2-6b-vs-otel-2-0-llm-31b-it.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lfm2-5-2-6b.json·/api/v1/tools/otel-2-0-llm-31b-it.json - From a terminal
anchor compare lfm2-5-2-6b otel-2-0-llm-31b-it(the CLI) - Over MCP
compare_tools {"a": "lfm2-5-2-6b", "b": "otel-2-0-llm-31b-it"}at/mcp, no key