Head to head · Open-weight models you run yourself · October 2026 research run
LFM3-VL-2B vs OTel-2.0-LLM-31B-IT
LFM3-VL-2B 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. OTel-2.0-LLM-31B-IT leads on risk. 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 on a laptop, phone or robot that need to read screens, documents, images and video from a model under 2 GB at 4 bits
Ahead on
- Reach, 85 against 50
- Agent interface, 90 against 60
Watch for
vLLM and SGLang support is unreleased, which the card says itself
Best for Telecoms teams that want an open model for standards questions and RAG on their own hardware
Ahead on
- Risk, 55 against 40
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 LFM3-VL-2B +35
LFM3-VL-2B 85
Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.20 GB projector file, and 1.30 GB × 1.2 = 1.6 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 15, Released llama.cpp has the lfm3 architecture and the LFM3-VL projector (src/models/lfm3.cpp and tools/mtmd at b12242), Ollama's library has an lfm3-vl entry, and LM Studio's catalogue lists liquid/lfm3-vl-2b. Builds 15, Liquid's GGUF repository holds Q4_0, Q4_K_M, Q8_0, F16 and BF16 files, and Liquid publishes 4-bit and 8-bit MLX builds and an ONNX repository, all in the LiquidAI organisation. Terms 10, the LFM Open License v1.0, a custom licence that lets anyone use it commercially for free below a threshold of $10M annual revenue. Download 10, the Hub API reports gated false for the model and its GGUF, MLX and ONNX repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, Liquid's own API lists lfm3-vl-2b among its models, so the publisher hosts it. 30 + 15 + 15 + 10 + 10 + 5 = 85.
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.
Agent interface LFM3-VL-2B +30
LFM3-VL-2B 90
Chat template 20, chat_template.jinja in the repository (12,129 characters), with roles, images and video, tools, deferred tools, tool results and the thinking switch. Tool-calling format 25, the card and Liquid's tool-use page document tools passed through tools= in apply_chat_template, calls returned as XML and results sent back as tool messages. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so several calls fit in one turn, and the card says its fine-tuning mix included tool calling and agentic traces. Structured output 5, the card's vLLM and SGLang commands set a structured-output backend and its fine-tuning table has a JSON extraction notebook, but nothing says how to ask this model for JSON. Liquid's API guide documents response_format with lfm3-1.7b as its example. Reasoning control 10, Liquid's chat-template page documents enable_thinking=False in apply_chat_template for LFM3, with reasoning on by default inside think tags, and the card documents preserve_thinking and reports a no-thinking configuration in its benchmarks. Context 10, 128K tokens of input and output per the card, and max_position_embeddings 128000 for the language model in config.json. 20 + 25 + 20 + 5 + 10 + 10 = 90.
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 +15
LFM3-VL-2B 40
File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, files in the LiquidAI organisation, which Liquid's docs page for the model and its blog post link to (10). Safety evaluation 0, no safety results on the card or in Liquid's blog post for the LFM3 family, neither of which mentions safety testing. Agent guidance 0, Nothing on prompt injection, an instruction hierarchy, what refusals cover or safeguards to add. Licence risk 10, 15 less 5 for the $10M annual revenue threshold on commercial use. Security programme 0, no way to report a flaw found. 15 + 15 + 0 + 0 + 10 + 0 = 40.
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 | LFM3-VL-2B | OTel-2.0-LLM-31B-IT | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 85 | 50 | LFM3-VL-2B +35 |
| Risk | 20%20 | 40 | 55 | OTel-2.0-LLM-31B-IT +15 |
| Agent interface | 10%10 | 90 | 60 | LFM3-VL-2B +30 |
| Documentation and upkeep | 10%10 | 77 | 74 | LFM3-VL-2B +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 56.8/100 |
Facts side by side
| Fact | LFM3-VL-2B | 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-09 | 2026-11-01 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
Verdicts
LFM3-VL-2B
A 1.92B vision model that reads images and video on an 8 GB machine, with a documented tool-call format and thinking. It runs today in llama.cpp, Ollama and LM Studio, while vLLM and SGLang support is still unreleased. Transformers needs repository code, and there are no safety results, security contact or data sources.
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
LFM3-VL-2B
- Start it with
llama-server -hf LiquidAI/LFM3-VL-2B-GGUF:Q4_K_M --jinjaorollama run lfm3-vl, with llama.cpp b11960 or later - Use temperature 0.1, top_k 50 and repetition penalty 1.1, per the card
- Video is sampled at 2 frames a second up to 768 frames, and each frame costs context. Video input in llama.cpp needs ffmpeg
- Don't plan on vLLM or SGLang until a release carries LFM3-VL
- Validate JSON output yourself
- Liquid doesn't recommend it for coding, multi-turn conversations or complex reasoning
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, LFM3-VL-2B or OTel-2.0-LLM-31B-IT?
LFM3-VL-2B 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. OTel-2.0-LLM-31B-IT leads on risk.
Other comparisons with LFM3-VL-2B or OTel-2.0-LLM-31B-IT
- Agents-A1-4B vs LFM3-VL-2B
- Agents-A1-4B vs OTel-2.0-LLM-31B-IT
- Apertus v1.5 8B vs LFM3-VL-2B
- Apertus v1.5 8B vs OTel-2.0-LLM-31B-IT
- Apodex-1.1-mini vs LFM3-VL-2B
- Apodex-1.1-mini vs OTel-2.0-LLM-31B-IT
- Arete-27B vs LFM3-VL-2B
- Arete-27B vs OTel-2.0-LLM-31B-IT
- BigBang-v1 vs LFM3-VL-2B
- BigBang-v1 vs OTel-2.0-LLM-31B-IT
- Carbon-X vs LFM3-VL-2B
- Carbon-X vs OTel-2.0-LLM-31B-IT
- Cola2 vs LFM3-VL-2B
- Cola2 vs OTel-2.0-LLM-31B-IT
- Cosmos-Reason2-2B vs LFM3-VL-2B
- Cosmos-Reason2-2B vs OTel-2.0-LLM-31B-IT
- Darwin-36B-Opus vs LFM3-VL-2B
- Darwin-36B-Opus vs OTel-2.0-LLM-31B-IT
- DeepSeek-V3.2 vs LFM3-VL-2B
- DeepSeek-V3.2 vs OTel-2.0-LLM-31B-IT
- DeepSeek V4.1 Flash vs LFM3-VL-2B
- DeepSeek V4.1 Flash vs OTel-2.0-LLM-31B-IT
- DeepSeek-V4-Flash-0731 vs LFM3-VL-2B
- DeepSeek-V4-Flash-0731 vs OTel-2.0-LLM-31B-IT
- Devstral Small 2 vs LFM3-VL-2B
- Devstral Small 2 vs OTel-2.0-LLM-31B-IT
- DiffusionGemma 26B A4B IT vs LFM3-VL-2B
- DiffusionGemma 26B A4B IT vs OTel-2.0-LLM-31B-IT
- EXAONE 4.5 33B vs LFM3-VL-2B
- EXAONE 4.5 33B vs OTel-2.0-LLM-31B-IT
- Gemma 4 12B IT vs LFM3-VL-2B
- Gemma 4 12B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 26B A4B IT vs LFM3-VL-2B
- Gemma 4 26B A4B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 31B IT vs LFM3-VL-2B
- Gemma 4 31B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 E2B IT vs LFM3-VL-2B
- Gemma 4 E2B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 E4B IT vs LFM3-VL-2B
- Gemma 4 E4B IT vs OTel-2.0-LLM-31B-IT
- GLM-4.5-Air vs LFM3-VL-2B
- GLM-4.5-Air vs OTel-2.0-LLM-31B-IT
- GLM-4.7-Flash vs LFM3-VL-2B
- GLM-4.7-Flash vs OTel-2.0-LLM-31B-IT
- GLM-5.3-Flash vs LFM3-VL-2B
- GLM-5.3-Flash vs OTel-2.0-LLM-31B-IT
- GLM-5.3 vs LFM3-VL-2B
- GLM-5.3 vs OTel-2.0-LLM-31B-IT
- gpt-oss-120b vs LFM3-VL-2B
- gpt-oss-120b vs OTel-2.0-LLM-31B-IT
- gpt-oss-20b vs LFM3-VL-2B
- gpt-oss-20b vs OTel-2.0-LLM-31B-IT
- Granite 4.2 30B vs LFM3-VL-2B
- Granite 4.2 30B vs OTel-2.0-LLM-31B-IT
- Granite 4.2 3B vs LFM3-VL-2B
- Granite 4.2 3B vs OTel-2.0-LLM-31B-IT
- Granite 4.2 8B vs LFM3-VL-2B
- Granite 4.2 8B vs OTel-2.0-LLM-31B-IT
- Hy-Memory-30B-A3B vs LFM3-VL-2B
- Hy-Memory-30B-A3B vs OTel-2.0-LLM-31B-IT
- Hy3 vs LFM3-VL-2B
- Hy3 vs OTel-2.0-LLM-31B-IT
- Inkling-Small vs LFM3-VL-2B
- Inkling-Small vs OTel-2.0-LLM-31B-IT
- Inkling vs LFM3-VL-2B
- Inkling vs OTel-2.0-LLM-31B-IT
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM3-VL-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs OTel-2.0-LLM-31B-IT
- Kimi K3.1 Pro vs LFM3-VL-2B
- Kimi K3.1 Pro vs OTel-2.0-LLM-31B-IT
- Kimi K3 vs LFM3-VL-2B
- Kimi K3 vs OTel-2.0-LLM-31B-IT
- Kolibri-1 vs LFM3-VL-2B
- Kolibri-1 vs OTel-2.0-LLM-31B-IT
- Kronos vs LFM3-VL-2B
- Kronos vs OTel-2.0-LLM-31B-IT
- Laguna M.1 vs LFM3-VL-2B
- Laguna M.1 vs OTel-2.0-LLM-31B-IT
- Laguna S 2.1 vs LFM3-VL-2B
- Laguna S 2.1 vs OTel-2.0-LLM-31B-IT
- Laguna XS 2.1 vs LFM3-VL-2B
- Laguna XS 2.1 vs OTel-2.0-LLM-31B-IT
- LBS-27B vs LFM3-VL-2B
- LBS-27B vs OTel-2.0-LLM-31B-IT
- LFM2.5-2.6B vs LFM3-VL-2B
- LFM2.5-2.6B vs OTel-2.0-LLM-31B-IT
- LFM3-1.7B vs LFM3-VL-2B
- LFM3-1.7B vs OTel-2.0-LLM-31B-IT
- LFM3-Audio-2B vs LFM3-VL-2B
- LFM3-Audio-2B vs OTel-2.0-LLM-31B-IT
- LFM3-Omni-2B vs LFM3-VL-2B
- LFM3-Omni-2B vs OTel-2.0-LLM-31B-IT
- LFM3-VL-2B vs Ling-3.0-tiny
- LFM3-VL-2B vs Ling-3.1-flash-1019
- LFM3-VL-2B vs LongCat-2.5
- LFM3-VL-2B vs MiMo-V2.6 Distill Qwen 9B
- LFM3-VL-2B vs MiMo-V2.6-Flash-RL
- LFM3-VL-2B vs MiniCPM-o 4.5
- LFM3-VL-2B vs MiniCPM-V 4.7 1B
- LFM3-VL-2B vs MiniCPM-V 4.7 35B-A3B
- LFM3-VL-2B vs MiniCPM5-2B
- LFM3-VL-2B vs MiniMax-M2.5
- LFM3-VL-2B vs MiniMax-M2.7
- LFM3-VL-2B vs MiniMax-M3.1-Flash
- LFM3-VL-2B vs Mistral Large 4
- LFM3-VL-2B vs Muse Glimmer 30B
- LFM3-VL-2B vs Nanbeige4.2-3B
- LFM3-VL-2B vs Nanbeige4.3-33B
- LFM3-VL-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- LFM3-VL-2B vs Nemotron 3.5 Lightning 30B A3B
- LFM3-VL-2B vs Nemotron 3 Nano 30B A3B
- LFM3-VL-2B vs Nemotron 3 Nano 4B
- LFM3-VL-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- LFM3-VL-2B vs Nemotron 3 Super 120B A12B
- LFM3-VL-2B vs Nemotron 3 Ultra 550B A55B
- LFM3-VL-2B vs North Mini Code 1.0
- LFM3-VL-2B vs occamy-1.0
- LFM3-VL-2B vs Olmo 3 7B Think
- LFM3-VL-2B vs Ornith-1.5-122B
- LFM3-VL-2B vs Ornith-1.5-35B-A3B
- LFM3-VL-2B vs Ornith-1.5-397B
- LFM3-VL-2B vs Ornith-1.5-9B
- LFM3-VL-2B vs Qwen-AgentWorld-35B-A3B
- LFM3-VL-2B vs Qwen3-30B-A3B-Instruct-2507
- LFM3-VL-2B vs Qwen3-4B-Instruct-2507
- LFM3-VL-2B vs Qwen3.5-0.8B
- LFM3-VL-2B vs Qwen3.5-122B-A10B
- LFM3-VL-2B vs Qwen3.5-2B
- LFM3-VL-2B vs Qwen3.5-397B-A17B
- LFM3-VL-2B vs Qwen3.5-4B
- LFM3-VL-2B vs Qwen3.5-9B
- LFM3-VL-2B vs Qwen3.6-27B
- LFM3-VL-2B vs Qwen3.6-35B-A3B
- LFM3-VL-2B vs Qwen3.8-27B
- LFM3-VL-2B vs Qwen3.8-Flash-Next
- LFM3-VL-2B vs Qwen3-Coder-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-Coder-Next
- LFM3-VL-2B vs Qwen3-Omni-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-VL-2B-Instruct
- LFM3-VL-2B vs Qwen3-VL-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-VL-32B-Instruct
- LFM3-VL-2B vs Qwen3-VL-4B-Instruct
- LFM3-VL-2B vs Qwen3-VL-8B-Instruct
- LFM3-VL-2B vs Qwopus3.8-27B-Flash-V2
- LFM3-VL-2B vs Recursive Flint
- LFM3-VL-2B vs Ripple-65B Preview
- LFM3-VL-2B vs SenseNova-Loop-9B-Preview
- LFM3-VL-2B vs SmolLM3-3B
- LFM3-VL-2B vs Spark-X2.6-4B
- LFM3-VL-2B vs Step 3.7 Flash
- LFM3-VL-2B vs Swift 1.5 Qwen3.8-27B
- LFM3-VL-2B vs Swift 1.5 Qwen3.8-Flash-Next
- LFM3-VL-2B vs ThinkingCap (Qwen3.8 27B)
- LFM3-VL-2B vs Baidu Unlimited-OCR-2
- LFM3-VL-2B vs WeVisOne-VL-2B
- LFM3-VL-2B vs WeVisOne-VL-4B
- LFM3-VL-2B vs ZAYA1-8B
- 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/lfm3-vl-2b-vs-otel-2-0-llm-31b-it.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lfm3-vl-2b.json·/api/v1/tools/otel-2-0-llm-31b-it.json - From a terminal
anchor compare lfm3-vl-2b otel-2-0-llm-31b-it(the CLI) - Over MCP
compare_tools {"a": "lfm3-vl-2b", "b": "otel-2-0-llm-31b-it"}at/mcp, no key