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

OTel-2.0-LLM-31B-IT vs Qwen3.8-Flash-Next

Qwen3.8-Flash-Next scores 61.8 (C) 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 risk and 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

  • Risk, 55 against 45
  • Documentation and upkeep, 74 against 36

Watch for

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

Qwen3.8-Flash-Next C

Best for Teams with a multi-GPU server or a 128 GB Mac who want Qwen's newest sparse architecture for agentic coding and multimodal work, and aren't a hosted-model or coding-assistant business.

Ahead on

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

Watch for

No build fits the reference machine's 107.4 GB, and Ollama's smallest Linux build is 120 GB

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 +38

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.8-Flash-Next 36

Model card 11 of 20, intended use, architecture, parameters and context are there, but limitations, languages and a knowledge cut-off aren't. Training data 0, not described beyond a token count relative to an earlier model. Last change 15, the FP8 config fix on 31 August 2026, 63 days before 2 November. Responsiveness 0, Qwen answered none of the 40 most recent questions and reports (29 to 79, 27 August to 26 October), its only reply came in the first week. Version policy 5, a first release with nothing replaced. File health 5, the files agree with the card, but a 19 October report about the template and a pull request to fix it still wait without a reply. 11 + 0 + 15 + 0 + 5 + 5 = 36.

Reach Qwen3.8-Flash-Next +15

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.8-Flash-Next 65

Memory 5 of 30, the smallest listed 4-bit build is Ollama's 120 GB q4_K_M, 144 GB with a fifth added, which is beyond the reference machine and inside 256 GB. Ollama's Apple-only 105 GB MLX build isn't among the builds and would land in the same band. Runtimes 25, released versions of llama.cpp, Ollama, vLLM, SGLang and Transformers all run the qwen4_exp architecture. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 10 of 15, a custom licence that's free for commercial use except for model-as-a-service and coding or office assistant businesses, which need a separate licence. Download 10, neither repository is gated. Hosted 5, Hugging Face lists two live providers, Featherless AI for the BF16 repository and Nscale for the FP8 build, and Alibaba's Qwen Cloud serves Qwen3.8-Flash, which the card says is based on these weights.

Risk OTel-2.0-LLM-31B-IT +10

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.

Qwen3.8-Flash-Next 45

File safety 25, safetensors only and nothing from the repository runs to load it or build prompts. Provenance 15, the files are in the Qwen organisation that Qwen's GitHub links to, and every file has a checksum. Safety evaluation 0, none published on the card or in the technical report. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 5 of 15, 5 off for the field-of-use limit on model-as-a-service and coding or office assistant businesses and 5 off for the naming duty above a user or revenue threshold. Security programme 0, no security.txt, disclosure policy or security contact for Qwen was found, and Alibaba's group security centre couldn't be checked, so it's scored as absent.

Agent interface Qwen3.8-Flash-Next +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.8-Flash-Next 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10 of 25, the format lives only in the template and the parser name only in serving commands, and Alibaba doesn't describe how tools are declared or returned. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, not documented for the weights. Reasoning control 10, thinking turns off per request, reasoning_effort budgets it and the card shows the reasoning coming back in reasoning_content. Context 10, 262,144 tokens native.

Score by category

CategoryWeight this runOTel-2.0-LLM-31B-ITQwen3.8-Flash-NextEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255065Qwen3.8-Flash-Next +15
Risk20%205545OTel-2.0-LLM-31B-IT +10
Agent interface10%106070Qwen3.8-Flash-Next +10
Documentation and upkeep10%107436OTel-2.0-LLM-31B-IT +38
Negative events≤1500
TotalC 56.8/100C 61.8/100

Facts side by side

FactOTel-2.0-LLM-31B-ITQwen3.8-Flash-Next
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.0Qwen Community License 1.0 (custom, not an OSI licence). Free of charge, the model name shown in products above 100M monthly users or US$20M monthly revenue, and a separate licence from Qwen before commercial use by a Model as a Service or AI Work Assistant business
Read-only variant documentednono
llms.txtnono
Last release2026-11-012026-08-31
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2/5 (4)

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.8-Flash-Next

A large sparse cousin with 6B active parameters for agentic coding and multimodal work, previewing Qwen's next architecture. It needs a 128 GB Mac for Ollama's MLX build or about 144 GB for the 4-bit GGUF, and Qwen Cloud serves it. The main risk is a licence that needs a separate deal for hosted-model and coding or office assistant businesses.

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.8-Flash-Next

  1. On a 128 GB Mac start it with ollama run qwen3.8-flash-next:125b-mlx (105 GB, NVFP4), on Linux the smallest Ollama build is qwen3.8-flash-next:125b-a6b-q4_K_M at 120 GB, which won't fit a 107.4 GB GPU share
  2. On a server, vllm serve Qwen/Qwen3.8-Flash-Next-FP8 --tensor-parallel-size 4 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. Use the qwen3_coder tool parser and the qwen3 reasoning parser, as Qwen's GitHub README does
  4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false to skip it, and read the reasoning from reasoning_content, even though SGLang's cookbook says thinking can't be turned off
  5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
  6. Send at most one system message and put it first, since the template raises an error otherwise
  7. Sampling per the card is temperature 1.0 and top_p 0.95 when thinking, temperature 0.7, top_p 0.8 and presence_penalty 1.5 without
  8. vLLM keeps the 51B n-gram table in host memory on 80 GB GPUs by default, per its recipe
  9. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
  10. Read the Qwen Community License before serving it to others as an API or inside a coding or office assistant product

Questions

Which is better for AI agents, OTel-2.0-LLM-31B-IT or Qwen3.8-Flash-Next?

Qwen3.8-Flash-Next scores 61.8 (C) 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 risk and documentation and upkeep.

Other comparisons with OTel-2.0-LLM-31B-IT or Qwen3.8-Flash-Next

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.