Head to head · Open-weight models you run yourself · October 2026 research run
MiniCPM5-2B vs OTel-2.0-LLM-31B-IT
MiniCPM5-2B scores 59.7 (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 On-device and laptop agents that want a 2 GB tool-calling helper with long context and open training data
Ahead on
- Reach, 90 against 50
- Agent interface, 75 against 60
- Documentation and upkeep, 92 against 74
Watch for
OpenBMB documents only a Think mode for the 2B, so every answer starts with reasoning
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.
Reach MiniCPM5-2B +40
MiniCPM5-2B 90
Memory 30, OpenBMB's own MLX 4-bit build is 1.42 GB and its Q4_K_M GGUF 1.56 GB, about 2 GB with the fifth added. Runtimes 25, the cap, since the model is a stock Llama and vLLM, SGLang, released Transformers, a released llama.cpp and Ollama all run it. Builds 15, OpenBMB ships GGUF at three precisions plus MLX and GPTQ 4-bit. Terms 10, the LICENSE is plain Apache 2.0 but the card prohibits jailbreaking and injection testing and limits use to ethical purposes, which reads as a use policy on top (dated 21 October 2026). Download 10, nothing is gated. Hosted 0, OpenBMB has no API for it, no inference provider is listed on its Hugging Face page and OpenRouter doesn't carry 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 MiniCPM5-2B +18
MiniCPM5-2B 92
Model card 17, everything but a knowledge cut-off. Training data 20, all eight training datasets are published on Hugging Face and named per stage with sizes. Last change 15, a template fix on 29 September 2026, 36 days ago, with nothing newer in OpenBMB's MiniCPM5 repositories on Hugging Face (builds last changed 12 September) or its GitHub repository (21 September). Responsiveness 20, OpenBMB members answered 16 of the 23 questions in the discussions, the newest reply on 29 September. Version policy 10, earlier models and checkpoints sit in their own repositories and the GitHub changelog dates each release. File health 10, config, tokenizer, template and card agree and no broken-file report waited on 21 October, though OpenBMB's GGUF, MLX and GPTQ repositories still carry the template from before the 29 September fix.
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 MiniCPM5-2B +15
MiniCPM5-2B 75
Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card and OpenBMB's cookbooks document the XML call format, the tools request and the minicpm5 parser in SGLang and vLLM. Trained tool calling 20, agent SFT on 500K samples and a template that renders several calls in one turn. Structured output 0, nothing documents asking for JSON. Reasoning control 0, a judgement call, because OpenBMB's own cookbooks call Think the only supported mode for the 2B even though the template accepts enable_thinking false. Context 10, 131,072 tokens native with no rope scaling.
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.
Score by category
| Category | Weight this run | MiniCPM5-2B | OTel-2.0-LLM-31B-IT | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 90 | 50 | MiniCPM5-2B +40 |
| Risk | 20%20 | 55 | 55 | even |
| Agent interface | 10%10 | 75 | 60 | MiniCPM5-2B +15 |
| Documentation and upkeep | 10%10 | 92 | 74 | MiniCPM5-2B +18 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 59.7/100 | C 56.8/100 |
Facts side by side
| Fact | MiniCPM5-2B | OTel-2.0-LLM-31B-IT |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | OpenBMB | 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-09-29 | 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/5 (4) | none |
How the scores have moved
OTel-2.0-LLM-31B-IT
No score change since it was listed.
Verdicts
MiniCPM5-2B
A 2B dense model for local tool calling and long context, with published training data. OpenBMB's own 4-bit builds are under 1.6 GB, and the model loads in vLLM, SGLang, llama.cpp, Ollama and Transformers. The main risks are always-on thinking, no safety results and use conditions beyond Apache 2.0.
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
MiniCPM5-2B
- Smallest start is
ollama run openbmb/minicpm5-2b(1.6 GB, q4_k_m) - On vLLM 0.29.0 or later run
vllm serve openbmb/MiniCPM5-2B --max-model-len 131072 --enable-auto-tool-choice --tool-call-parser minicpm5, or tool calls come back as XML text - On SGLang 0.5.16 or later add
--tool-call-parser minicpm5 --reasoning-parser qwen3; SGLang is OpenBMB's recommended backend for tool calls - Tool calls are XML,
<function name=...><param name=...>, not Hermes JSON - Sample with temperature 1.0, top_p 0.95 and min_p 0.0; llama.cpp's default min_p 0.05 can loop, and repetition_penalty 1.05 helps if it does
- Expect a
<think>block before every answer and leave room in max_tokens; enable_thinking false is accepted by the template but OpenBMB doesn't support it for the 2B - Validate JSON yourself or use the runtime's guided decoding, since structured output isn't documented
- Use the main repository's template; the GGUF, MLX and GPTQ copies predate the 29 September fix
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, MiniCPM5-2B or OTel-2.0-LLM-31B-IT?
MiniCPM5-2B scores 59.7 (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 MiniCPM5-2B or OTel-2.0-LLM-31B-IT
- Agents-A1-4B vs MiniCPM5-2B
- Agents-A1-4B vs OTel-2.0-LLM-31B-IT
- Apertus v1.5 8B vs MiniCPM5-2B
- Apertus v1.5 8B vs OTel-2.0-LLM-31B-IT
- Apodex-1.1-mini vs MiniCPM5-2B
- Apodex-1.1-mini vs OTel-2.0-LLM-31B-IT
- Arete-27B vs MiniCPM5-2B
- Arete-27B vs OTel-2.0-LLM-31B-IT
- BigBang-v1 vs MiniCPM5-2B
- BigBang-v1 vs OTel-2.0-LLM-31B-IT
- Carbon-X vs MiniCPM5-2B
- Carbon-X vs OTel-2.0-LLM-31B-IT
- Cola2 vs MiniCPM5-2B
- Cola2 vs OTel-2.0-LLM-31B-IT
- Cosmos-Reason2-2B vs MiniCPM5-2B
- Cosmos-Reason2-2B vs OTel-2.0-LLM-31B-IT
- Darwin-36B-Opus vs MiniCPM5-2B
- Darwin-36B-Opus vs OTel-2.0-LLM-31B-IT
- DeepSeek-V3.2 vs MiniCPM5-2B
- DeepSeek-V3.2 vs OTel-2.0-LLM-31B-IT
- DeepSeek V4.1 Flash vs MiniCPM5-2B
- DeepSeek V4.1 Flash vs OTel-2.0-LLM-31B-IT
- DeepSeek-V4-Flash-0731 vs MiniCPM5-2B
- DeepSeek-V4-Flash-0731 vs OTel-2.0-LLM-31B-IT
- Devstral Small 2 vs MiniCPM5-2B
- Devstral Small 2 vs OTel-2.0-LLM-31B-IT
- DiffusionGemma 26B A4B IT vs MiniCPM5-2B
- DiffusionGemma 26B A4B IT vs OTel-2.0-LLM-31B-IT
- EXAONE 4.5 33B vs MiniCPM5-2B
- EXAONE 4.5 33B vs OTel-2.0-LLM-31B-IT
- Gemma 4 12B IT vs MiniCPM5-2B
- Gemma 4 12B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 26B A4B IT vs MiniCPM5-2B
- Gemma 4 26B A4B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 31B IT vs MiniCPM5-2B
- Gemma 4 31B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 E2B IT vs MiniCPM5-2B
- Gemma 4 E2B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 E4B IT vs MiniCPM5-2B
- Gemma 4 E4B IT vs OTel-2.0-LLM-31B-IT
- GLM-4.5-Air vs MiniCPM5-2B
- GLM-4.5-Air vs OTel-2.0-LLM-31B-IT
- GLM-4.7-Flash vs MiniCPM5-2B
- GLM-4.7-Flash vs OTel-2.0-LLM-31B-IT
- GLM-5.3-Flash vs MiniCPM5-2B
- GLM-5.3-Flash vs OTel-2.0-LLM-31B-IT
- GLM-5.3 vs MiniCPM5-2B
- GLM-5.3 vs OTel-2.0-LLM-31B-IT
- gpt-oss-120b vs MiniCPM5-2B
- gpt-oss-120b vs OTel-2.0-LLM-31B-IT
- gpt-oss-20b vs MiniCPM5-2B
- gpt-oss-20b vs OTel-2.0-LLM-31B-IT
- Granite 4.2 30B vs MiniCPM5-2B
- Granite 4.2 30B vs OTel-2.0-LLM-31B-IT
- Granite 4.2 3B vs MiniCPM5-2B
- Granite 4.2 3B vs OTel-2.0-LLM-31B-IT
- Granite 4.2 8B vs MiniCPM5-2B
- Granite 4.2 8B vs OTel-2.0-LLM-31B-IT
- Hy-Memory-30B-A3B vs MiniCPM5-2B
- Hy-Memory-30B-A3B vs OTel-2.0-LLM-31B-IT
- Hy3 vs MiniCPM5-2B
- Hy3 vs OTel-2.0-LLM-31B-IT
- Inkling-Small vs MiniCPM5-2B
- Inkling-Small vs OTel-2.0-LLM-31B-IT
- Inkling vs MiniCPM5-2B
- Inkling vs OTel-2.0-LLM-31B-IT
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs MiniCPM5-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs OTel-2.0-LLM-31B-IT
- Kimi K3.1 Pro vs MiniCPM5-2B
- Kimi K3.1 Pro vs OTel-2.0-LLM-31B-IT
- Kimi K3 vs MiniCPM5-2B
- Kimi K3 vs OTel-2.0-LLM-31B-IT
- Kolibri-1 vs MiniCPM5-2B
- Kolibri-1 vs OTel-2.0-LLM-31B-IT
- Kronos vs MiniCPM5-2B
- Kronos vs OTel-2.0-LLM-31B-IT
- Laguna M.1 vs MiniCPM5-2B
- Laguna M.1 vs OTel-2.0-LLM-31B-IT
- Laguna S 2.1 vs MiniCPM5-2B
- Laguna S 2.1 vs OTel-2.0-LLM-31B-IT
- Laguna XS 2.1 vs MiniCPM5-2B
- Laguna XS 2.1 vs OTel-2.0-LLM-31B-IT
- LBS-27B vs MiniCPM5-2B
- LBS-27B vs OTel-2.0-LLM-31B-IT
- LFM2.5-2.6B vs MiniCPM5-2B
- LFM2.5-2.6B vs OTel-2.0-LLM-31B-IT
- LFM3-1.7B vs MiniCPM5-2B
- LFM3-1.7B vs OTel-2.0-LLM-31B-IT
- LFM3-Audio-2B vs MiniCPM5-2B
- LFM3-Audio-2B vs OTel-2.0-LLM-31B-IT
- LFM3-Omni-2B vs MiniCPM5-2B
- LFM3-Omni-2B vs OTel-2.0-LLM-31B-IT
- LFM3-VL-2B vs MiniCPM5-2B
- LFM3-VL-2B vs OTel-2.0-LLM-31B-IT
- Ling-3.0-tiny vs MiniCPM5-2B
- Ling-3.0-tiny vs OTel-2.0-LLM-31B-IT
- Ling-3.1-flash-1019 vs MiniCPM5-2B
- Ling-3.1-flash-1019 vs OTel-2.0-LLM-31B-IT
- LongCat-2.5 vs MiniCPM5-2B
- LongCat-2.5 vs OTel-2.0-LLM-31B-IT
- MiMo-V2.6 Distill Qwen 9B vs MiniCPM5-2B
- MiMo-V2.6 Distill Qwen 9B vs OTel-2.0-LLM-31B-IT
- MiMo-V2.6-Flash-RL vs MiniCPM5-2B
- MiMo-V2.6-Flash-RL vs OTel-2.0-LLM-31B-IT
- MiniCPM-o 4.5 vs MiniCPM5-2B
- MiniCPM-o 4.5 vs OTel-2.0-LLM-31B-IT
- MiniCPM-V 4.7 1B vs MiniCPM5-2B
- MiniCPM-V 4.7 1B vs OTel-2.0-LLM-31B-IT
- MiniCPM-V 4.7 35B-A3B vs MiniCPM5-2B
- MiniCPM-V 4.7 35B-A3B vs OTel-2.0-LLM-31B-IT
- MiniCPM5-2B vs MiniMax-M2.5
- MiniCPM5-2B vs MiniMax-M2.7
- MiniCPM5-2B vs MiniMax-M3.1-Flash
- MiniCPM5-2B vs Mistral Large 4
- MiniCPM5-2B vs Muse Glimmer 30B
- MiniCPM5-2B vs Nanbeige4.2-3B
- MiniCPM5-2B vs Nanbeige4.3-33B
- MiniCPM5-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- MiniCPM5-2B vs Nemotron 3.5 Lightning 30B A3B
- MiniCPM5-2B vs Nemotron 3 Nano 30B A3B
- MiniCPM5-2B vs Nemotron 3 Nano 4B
- MiniCPM5-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- MiniCPM5-2B vs Nemotron 3 Super 120B A12B
- MiniCPM5-2B vs Nemotron 3 Ultra 550B A55B
- MiniCPM5-2B vs North Mini Code 1.0
- MiniCPM5-2B vs occamy-1.0
- MiniCPM5-2B vs Olmo 3 7B Think
- MiniCPM5-2B vs Ornith-1.5-122B
- MiniCPM5-2B vs Ornith-1.5-35B-A3B
- MiniCPM5-2B vs Ornith-1.5-397B
- MiniCPM5-2B vs Ornith-1.5-9B
- MiniCPM5-2B vs Qwen-AgentWorld-35B-A3B
- MiniCPM5-2B vs Qwen3-30B-A3B-Instruct-2507
- MiniCPM5-2B vs Qwen3-4B-Instruct-2507
- MiniCPM5-2B vs Qwen3.5-0.8B
- MiniCPM5-2B vs Qwen3.5-122B-A10B
- MiniCPM5-2B vs Qwen3.5-2B
- MiniCPM5-2B vs Qwen3.5-397B-A17B
- MiniCPM5-2B vs Qwen3.5-4B
- MiniCPM5-2B vs Qwen3.5-9B
- MiniCPM5-2B vs Qwen3.6-27B
- MiniCPM5-2B vs Qwen3.6-35B-A3B
- MiniCPM5-2B vs Qwen3.8-27B
- MiniCPM5-2B vs Qwen3.8-Flash-Next
- MiniCPM5-2B vs Qwen3-Coder-30B-A3B-Instruct
- MiniCPM5-2B vs Qwen3-Coder-Next
- MiniCPM5-2B vs Qwen3-Omni-30B-A3B-Instruct
- MiniCPM5-2B vs Qwen3-VL-2B-Instruct
- MiniCPM5-2B vs Qwen3-VL-30B-A3B-Instruct
- MiniCPM5-2B vs Qwen3-VL-32B-Instruct
- MiniCPM5-2B vs Qwen3-VL-4B-Instruct
- MiniCPM5-2B vs Qwen3-VL-8B-Instruct
- MiniCPM5-2B vs Qwopus3.8-27B-Flash-V2
- MiniCPM5-2B vs Recursive Flint
- MiniCPM5-2B vs Ripple-65B Preview
- MiniCPM5-2B vs SenseNova-Loop-9B-Preview
- MiniCPM5-2B vs SmolLM3-3B
- MiniCPM5-2B vs Spark-X2.6-4B
- MiniCPM5-2B vs Step 3.7 Flash
- MiniCPM5-2B vs Swift 1.5 Qwen3.8-27B
- MiniCPM5-2B vs Swift 1.5 Qwen3.8-Flash-Next
- MiniCPM5-2B vs ThinkingCap (Qwen3.8 27B)
- MiniCPM5-2B vs Baidu Unlimited-OCR-2
- MiniCPM5-2B vs WeVisOne-VL-2B
- MiniCPM5-2B vs WeVisOne-VL-4B
- MiniCPM5-2B vs ZAYA1-8B
- 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/minicpm5-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/minicpm5-2b.json·/api/v1/tools/otel-2-0-llm-31b-it.json - From a terminal
anchor compare minicpm5-2b otel-2-0-llm-31b-it(the CLI) - Over MCP
compare_tools {"a": "minicpm5-2b", "b": "otel-2-0-llm-31b-it"}at/mcp, no key