Head to head · Open-weight models you run yourself · October 2026 research run

OTel-2.0-LLM-31B-IT vs Qwen3.5-122B-A10B

Qwen3.5-122B-A10B scores 63.1 (B) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 2 of 4 scored categories. OTel-2.0-LLM-31B-IT leads on documentation and upkeep. 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

OTel-2.0-LLM-31B-IT C

Best for Telecoms teams that want an open model for standards questions and RAG on their own hardware

Ahead on

  • Documentation and upkeep, 74 against 34

Watch for

BF16 only at 62.6 GB, with no GGUF or other quantised build from anyone we checked

Qwen3.5-122B-A10B B

Best for Agents with a 128 GB unified-memory machine or two large GPUs that want a capable vision-language model with a plain licence.

Ahead on

  • Reach, 80 against 50
  • Agent interface, 70 against 60

Watch for

Too big for a single 64 GB machine even at 4 bits

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.

Documentation and upkeep OTel-2.0-LLM-31B-IT +40

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.

Qwen3.5-122B-A10B 34

The card covers five of the seven items and misses limitations and a cut-off (14). Training data is a general description without a cut-off (5). The files last changed on 24 April 2026, 192 days before this check, past the 180-day band and within a year (5), and Qwen's GitHub repository holds only a README and licence, so no reference code of Alibaba's changed later. No Qwen member has answered any of the 21 discussions that aren't pull requests, recounted on 2 November (0), and GitHub issues couldn't be counted. It's a first release at this size (5), and a template fix and a run report still wait unanswered (5). 14 + 5 + 5 + 0 + 5 + 5 = 34.

Reach Qwen3.5-122B-A10B +30

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.

Qwen3.5-122B-A10B 80

Memory earns 10 of 30, since Alibaba's GPTQ 4-bit build is 78.9 GB, about 95 GB with a fifth added, which fits our reference machine but no smaller band. Runtimes reach the 25 cap on released llama.cpp, Ollama, vLLM, SGLang and Transformers. Alibaba's FP8 and GPTQ-Int4 builds give builds the full 15. Apache 2.0 with nothing added gives terms 15, the ungated repositories give download 10, and Alibaba's own Model Studio plus Novita and DeepInfra give hosted too its 5.

Agent interface Qwen3.5-122B-A10B +10

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.

Qwen3.5-122B-A10B 70

The template ships in the repository (20) and renders several tool calls per turn for a model trained for tool use (20). Tool-calling format gets 10, because the card names the qwen3_coder parser but leaves the declaration and call format to the template. Thinking turns off per request and comes back in think tags split by the qwen3 parser (10), and 262,144 tokens is native (10). Structured output scores 0, as nothing documents JSON output for the model.

Score by category

CategoryWeight this runOTel-2.0-LLM-31B-ITQwen3.5-122B-A10BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255080Qwen3.5-122B-A10B +30
Risk20%205555even
Agent interface10%106070Qwen3.5-122B-A10B +10
Documentation and upkeep10%107434OTel-2.0-LLM-31B-IT +40
Negative events≤1500
TotalC 56.8/100B 63.1/100

Facts side by side

FactOTel-2.0-LLM-31B-ITQwen3.5-122B-A10B
KindOpen-weight modelOpen-weight model
VendorAT&T (Open Telco AI)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-11-012026-02-24
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3/5 (4)

How the scores have moved

Verdicts

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.

Qwen3.5-122B-A10B

A strong mid-size cousin for coding, agent steps and reading images or video, with thinking you can switch off per request. Alibaba's 4-bit build needs about 95 GB, which fits one 128 GB unified-memory machine, and several providers host it. The main risk is silence, with no safety results, agent guidance or answers from Alibaba.

Before you call either

OTel-2.0-LLM-31B-IT

  1. Download the 15 shards the index names, not the whole repository, which is twice the size
  2. Pin a revision. The card says the weights may change under the same name
  3. Serve it with vLLM 0.19.0 or later and the repository's own chat template, not Gemma 4's
  4. Send no thinking flags. It answers directly and wasn't trained on Gemma's thought channel
  5. Use it as the generation stage of a RAG pipeline over telecom standards, with source attribution and human review
  6. Don't use it to run network tools unattended. The card says that hasn't been evaluated

Qwen3.5-122B-A10B

  1. Quickest start on a 128 GB machine is ollama run qwen3.5:122b (Q4_K_M, 81 GB of files, about 97 GB with context)
  2. Alibaba's 4-bit build serves with vllm serve Qwen/Qwen3.5-122B-A10B-GPTQ-Int4 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder --quantization moe_wna16, though that kernel isn't documented for AMD gfx1151
  3. Use the qwen3_coder tool parser and the qwen3 reasoning parser, as the card's commands do
  4. Turn thinking off with "chat_template_kwargs": {"enable_thinking": false} in the request body, since it's on by default and /think and /nothink aren't supported
  5. Sampling per the card is temperature 0.6, top_p 0.95 and top_k 20 when thinking, and temperature 0.7, top_p 0.8, top_k 20 and presence_penalty 1.5 without
  6. Keep the context at 128K or more if you rely on thinking, and turn on YaRN only past 262,144 tokens
  7. Add --language-model-only in vLLM to skip the vision encoder and free memory for the KV cache when you only need text
  8. Validate any JSON it returns, since structured output isn't documented

Questions

Which is better for AI agents, OTel-2.0-LLM-31B-IT or Qwen3.5-122B-A10B?

Qwen3.5-122B-A10B scores 63.1 (B) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 2 of 4 scored categories. OTel-2.0-LLM-31B-IT leads on documentation and upkeep.

Other comparisons with OTel-2.0-LLM-31B-IT or Qwen3.5-122B-A10B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.