Head to head · Open-weight models you run yourself · October 2026 research run
Apertus v1.5 8B vs OTel-2.0-LLM-31B-IT
Apertus v1.5 8B 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 reach. 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 fully open, multilingual 8B with image and audio input on one 24 GB GPU, and can run a publisher fork of vLLM.
Ahead on
- Risk, 75 against 55
- Agent interface, 85 against 60
- Documentation and upkeep, 84 against 74
Watch for
No released runtime supports it, only Swiss AI's forks of vLLM and Transformers
Best for Telecoms teams that want an open model for standards questions and RAG on their own hardware
Ahead on
- Reach, 50 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.
Agent interface Apertus v1.5 8B +25
Apertus v1.5 8B 85
Chat template 20, a Jinja file in the repository. Tool-calling format 25, Swiss AI's report documents how tools are declared and returned and the card names vLLM's apertus parser. Trained tool calling 20, trained on verified tool use with several calls a turn, though parallel calls are weaker on the 8B and tools don't work with thinking on. Structured output 0, not documented. Reasoning control 10, thinking turns on per request and the card says where the reasoning comes back. Context 10, 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.
Risk Apertus v1.5 8B +20
Apertus v1.5 8B 75
File safety 25, safetensors only and no code in the repository. Provenance 15, the files are in the swiss-ai organisation the report links, with a checksum on every file. Safety evaluation 10 of 20, published safety benchmarks run with Swiss AI's open harnesses and early access for three outside evaluators, but the manual evaluation is Swiss AI's own and can't be rerun. Agent guidance 10, the report says what the refusals cover, how far jailbreaks get and that capability limits are the main defence, with a personal-data filter to apply, but nothing on prompt injection for deployers. Licence risk 10, 5 off for the use policy. Security programme 5, ETH Zurich's disclosure policy, with no advisories 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.
Reach OTel-2.0-LLM-31B-IT +10
Apertus v1.5 8B 40
Memory 25 of 30, the BF16 files are 18.4 GB, or 22.1 GB with a fifth added, which fits 24 GB. Runtimes 0, no released vLLM (to 0.33.0), SGLang (to 0.5.23), Transformers (to 5.22.1), llama.cpp, Ollama or LM Studio runs version 1.5 yet, only Swiss AI's forks. Builds 0, Swiss AI publishes no quantised build. Terms 10 of 15, Apache 2.0 with an acceptable use policy added at the gate. Download 5, a click-through that needs an account and your contact details. Hosted 0, no inference provider or publisher API was found, and Swiss AI's documentation page names none on 3 November 2026.
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 Apertus v1.5 8B +10
Apertus v1.5 8B 84
Model card 14 of 20, languages and a knowledge cut-off are missing. Training data 20, every dataset is public and listed with versions, licences and counts. Last change 20, the card changed on 14 October 2026, 20 days before 3 November, and Swiss AI added its own evaluation-results files on 26 October and 3 November. Responsiveness 20, Swiss AI answered all three questions, unchanged on 3 November 2026. Version policy 5, earlier models stay in their own repositories without a dated note. File health 5, the gated config couldn't be checked against the card, and the card and the policy disagree on the output filter.
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.
Score by category
| Category | Weight this run | Apertus v1.5 8B | OTel-2.0-LLM-31B-IT | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 40 | 50 | OTel-2.0-LLM-31B-IT +10 |
| Risk | 20%20 | 75 | 55 | Apertus v1.5 8B +20 |
| Agent interface | 10%10 | 85 | 60 | Apertus v1.5 8B +25 |
| Documentation and upkeep | 10%10 | 84 | 74 | Apertus v1.5 8B +10 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 56.8/100 |
Facts side by side
| Fact | Apertus v1.5 8B | OTel-2.0-LLM-31B-IT |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Swiss AI Initiative (EPFL and ETH Zurich) | 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, with the Apertus Acceptable Use Policy (v1.5, 14 July 2026) accepted at the download gate | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-14 | 2026-11-01 |
| Terms last updated | not read yet | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 2.8/5 (4) | none |
Verdicts
Apertus v1.5 8B
A fully open 8B cousin, training data included, for multilingual chat and tool calls with images and audio in. It needs about 22 GB in BF16 and Swiss AI's own vLLM or Transformers fork, since no released runtime supports it. The main risks are a gated download with a policy to pass on and tools that fail with thinking on.
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
Apertus v1.5 8B
- Accept the terms on the card and set HF_TOKEN before downloading
- Use Swiss AI's Docker image ghcr.io/swiss-ai/vllm_apertus_1.5_release, since stock vLLM and Transformers don't load Apertus1p5ForConditionalGeneration yet
- Serve with
--chat-template-content-format string --enable-auto-tool-choice --tool-call-parser apertusfor tools, and leave thinking off when you need tools - For thinking, set
--reasoning-parser apertusand--default-chat-template-kwargs.enable_thinking true, and budget max tokens generously - Audio is resampled to 24 kHz and costs 40 tokens a second, and video must be passed as frames
- Don't cast the loaded model with .half(), the image and audio tokenizers must stay in F32
- If you redistribute the weights, the policy says you must pass it on and get the recipient's express assent
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, Apertus v1.5 8B or OTel-2.0-LLM-31B-IT?
Apertus v1.5 8B 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 reach.
Other comparisons with Apertus v1.5 8B or OTel-2.0-LLM-31B-IT
- Agents-A1-4B vs Apertus v1.5 8B
- Agents-A1-4B vs OTel-2.0-LLM-31B-IT
- Apertus v1.5 8B vs Apodex-1.1-mini
- Apertus v1.5 8B vs Arete-27B
- Apertus v1.5 8B vs BigBang-v1
- Apertus v1.5 8B vs Carbon-X
- Apertus v1.5 8B vs Cola2
- Apertus v1.5 8B vs Cosmos-Reason2-2B
- Apertus v1.5 8B vs Darwin-36B-Opus
- Apertus v1.5 8B vs DeepSeek-V3.2
- Apertus v1.5 8B vs DeepSeek V4.1 Flash
- Apertus v1.5 8B vs DeepSeek-V4-Flash-0731
- Apertus v1.5 8B vs Devstral Small 2
- Apertus v1.5 8B vs DiffusionGemma 26B A4B IT
- Apertus v1.5 8B vs EXAONE 4.5 33B
- Apertus v1.5 8B vs Gemma 4 12B IT
- Apertus v1.5 8B vs Gemma 4 26B A4B IT
- Apertus v1.5 8B vs Gemma 4 31B IT
- Apertus v1.5 8B vs Gemma 4 E2B IT
- Apertus v1.5 8B vs Gemma 4 E4B IT
- Apertus v1.5 8B vs GLM-4.5-Air
- Apertus v1.5 8B vs GLM-4.7-Flash
- Apertus v1.5 8B vs GLM-5.3
- Apertus v1.5 8B vs GLM-5.3-Flash
- Apertus v1.5 8B vs gpt-oss-120b
- Apertus v1.5 8B vs gpt-oss-20b
- Apertus v1.5 8B vs Granite 4.2 30B
- Apertus v1.5 8B vs Granite 4.2 3B
- Apertus v1.5 8B vs Granite 4.2 8B
- Apertus v1.5 8B vs Hy-Memory-30B-A3B
- Apertus v1.5 8B vs Hy3
- Apertus v1.5 8B vs Inkling
- Apertus v1.5 8B vs Inkling-Small
- Apertus v1.5 8B vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Apertus v1.5 8B vs Kimi K3
- Apertus v1.5 8B vs Kimi K3.1 Pro
- Apertus v1.5 8B vs Kolibri-1
- Apertus v1.5 8B vs Kronos
- Apertus v1.5 8B vs Laguna M.1
- Apertus v1.5 8B vs Laguna S 2.1
- Apertus v1.5 8B vs Laguna XS 2.1
- Apertus v1.5 8B vs LBS-27B
- Apertus v1.5 8B vs LFM2.5-2.6B
- Apertus v1.5 8B vs LFM3-1.7B
- Apertus v1.5 8B vs LFM3-Audio-2B
- Apertus v1.5 8B vs LFM3-Omni-2B
- Apertus v1.5 8B vs LFM3-VL-2B
- Apertus v1.5 8B vs Ling-3.0-tiny
- Apertus v1.5 8B vs Ling-3.1-flash-1019
- Apertus v1.5 8B vs LongCat-2.5
- Apertus v1.5 8B vs MiMo-V2.6 Distill Qwen 9B
- Apertus v1.5 8B vs MiMo-V2.6-Flash-RL
- Apertus v1.5 8B vs MiniCPM-o 4.5
- Apertus v1.5 8B vs MiniCPM-V 4.7 1B
- Apertus v1.5 8B vs MiniCPM-V 4.7 35B-A3B
- Apertus v1.5 8B vs MiniCPM5-2B
- Apertus v1.5 8B vs MiniMax-M2.5
- Apertus v1.5 8B vs MiniMax-M2.7
- Apertus v1.5 8B vs MiniMax-M3.1-Flash
- Apertus v1.5 8B vs Mistral Large 4
- Apertus v1.5 8B vs Muse Glimmer 30B
- Apertus v1.5 8B vs Nanbeige4.2-3B
- Apertus v1.5 8B vs Nanbeige4.3-33B
- Apertus v1.5 8B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Apertus v1.5 8B vs Nemotron 3.5 Lightning 30B A3B
- Apertus v1.5 8B vs Nemotron 3 Nano 30B A3B
- Apertus v1.5 8B vs Nemotron 3 Nano 4B
- Apertus v1.5 8B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Apertus v1.5 8B vs Nemotron 3 Super 120B A12B
- Apertus v1.5 8B vs Nemotron 3 Ultra 550B A55B
- Apertus v1.5 8B vs North Mini Code 1.0
- Apertus v1.5 8B vs occamy-1.0
- Apertus v1.5 8B vs Olmo 3 7B Think
- Apertus v1.5 8B vs Ornith-1.5-122B
- Apertus v1.5 8B vs Ornith-1.5-35B-A3B
- Apertus v1.5 8B vs Ornith-1.5-397B
- Apertus v1.5 8B vs Ornith-1.5-9B
- Apertus v1.5 8B vs Qwen-AgentWorld-35B-A3B
- Apertus v1.5 8B vs Qwen3-30B-A3B-Instruct-2507
- Apertus v1.5 8B vs Qwen3-4B-Instruct-2507
- Apertus v1.5 8B vs Qwen3.5-0.8B
- Apertus v1.5 8B vs Qwen3.5-122B-A10B
- Apertus v1.5 8B vs Qwen3.5-2B
- Apertus v1.5 8B vs Qwen3.5-397B-A17B
- Apertus v1.5 8B vs Qwen3.5-4B
- Apertus v1.5 8B vs Qwen3.5-9B
- Apertus v1.5 8B vs Qwen3.6-27B
- Apertus v1.5 8B vs Qwen3.6-35B-A3B
- Apertus v1.5 8B vs Qwen3.8-27B
- Apertus v1.5 8B vs Qwen3.8-Flash-Next
- Apertus v1.5 8B vs Qwen3-Coder-30B-A3B-Instruct
- Apertus v1.5 8B vs Qwen3-Coder-Next
- Apertus v1.5 8B vs Qwen3-Omni-30B-A3B-Instruct
- Apertus v1.5 8B vs Qwen3-VL-2B-Instruct
- Apertus v1.5 8B vs Qwen3-VL-30B-A3B-Instruct
- Apertus v1.5 8B vs Qwen3-VL-32B-Instruct
- Apertus v1.5 8B vs Qwen3-VL-4B-Instruct
- Apertus v1.5 8B vs Qwen3-VL-8B-Instruct
- Apertus v1.5 8B vs Qwopus3.8-27B-Flash-V2
- Apertus v1.5 8B vs Recursive Flint
- Apertus v1.5 8B vs Ripple-65B Preview
- Apertus v1.5 8B vs SenseNova-Loop-9B-Preview
- Apertus v1.5 8B vs SmolLM3-3B
- Apertus v1.5 8B vs Spark-X2.6-4B
- Apertus v1.5 8B vs Step 3.7 Flash
- Apertus v1.5 8B vs Swift 1.5 Qwen3.8-27B
- Apertus v1.5 8B vs Swift 1.5 Qwen3.8-Flash-Next
- Apertus v1.5 8B vs ThinkingCap (Qwen3.8 27B)
- Apertus v1.5 8B vs Baidu Unlimited-OCR-2
- Apertus v1.5 8B vs WeVisOne-VL-2B
- Apertus v1.5 8B vs WeVisOne-VL-4B
- Apertus v1.5 8B vs ZAYA1-8B
- Apodex-1.1-mini vs OTel-2.0-LLM-31B-IT
- Arete-27B vs OTel-2.0-LLM-31B-IT
- BigBang-v1 vs OTel-2.0-LLM-31B-IT
- Carbon-X vs OTel-2.0-LLM-31B-IT
- Cola2 vs OTel-2.0-LLM-31B-IT
- Cosmos-Reason2-2B vs OTel-2.0-LLM-31B-IT
- Darwin-36B-Opus vs OTel-2.0-LLM-31B-IT
- DeepSeek-V3.2 vs OTel-2.0-LLM-31B-IT
- DeepSeek V4.1 Flash vs OTel-2.0-LLM-31B-IT
- DeepSeek-V4-Flash-0731 vs OTel-2.0-LLM-31B-IT
- Devstral Small 2 vs OTel-2.0-LLM-31B-IT
- DiffusionGemma 26B A4B IT vs OTel-2.0-LLM-31B-IT
- EXAONE 4.5 33B vs OTel-2.0-LLM-31B-IT
- Gemma 4 12B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 26B A4B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 31B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 E2B IT vs OTel-2.0-LLM-31B-IT
- Gemma 4 E4B IT vs OTel-2.0-LLM-31B-IT
- GLM-4.5-Air vs OTel-2.0-LLM-31B-IT
- GLM-4.7-Flash vs OTel-2.0-LLM-31B-IT
- GLM-5.3-Flash vs OTel-2.0-LLM-31B-IT
- GLM-5.3 vs OTel-2.0-LLM-31B-IT
- gpt-oss-120b vs OTel-2.0-LLM-31B-IT
- gpt-oss-20b vs OTel-2.0-LLM-31B-IT
- Granite 4.2 30B vs OTel-2.0-LLM-31B-IT
- Granite 4.2 3B vs OTel-2.0-LLM-31B-IT
- Granite 4.2 8B vs OTel-2.0-LLM-31B-IT
- Hy-Memory-30B-A3B vs OTel-2.0-LLM-31B-IT
- Hy3 vs OTel-2.0-LLM-31B-IT
- Inkling-Small vs OTel-2.0-LLM-31B-IT
- Inkling vs OTel-2.0-LLM-31B-IT
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs OTel-2.0-LLM-31B-IT
- Kimi K3.1 Pro vs OTel-2.0-LLM-31B-IT
- Kimi K3 vs OTel-2.0-LLM-31B-IT
- Kolibri-1 vs OTel-2.0-LLM-31B-IT
- 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/apertus-v1-5-8b-vs-otel-2-0-llm-31b-it.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/apertus-v1-5-8b.json·/api/v1/tools/otel-2-0-llm-31b-it.json - From a terminal
anchor compare apertus-v1-5-8b otel-2-0-llm-31b-it(the CLI) - Over MCP
compare_tools {"a": "apertus-v1-5-8b", "b": "otel-2-0-llm-31b-it"}at/mcp, no key