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

Ling-3.0-tiny vs OTel-2.0-LLM-31B-IT

OTel-2.0-LLM-31B-IT and Ling-3.0-tiny score within a point of each other on agent readiness, 56.8 (C) and 56.2 (C). Ling-3.0-tiny 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

Ling-3.0-tiny C

Best for Agents on a laptop or small GPU that want a fast local model for tool calls and short reasoning, under MIT

Ahead on

  • Reach, 95 against 50

Watch for

No inference provider is listed on the Hub and no inclusionAI API serves it

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 50
  • Documentation and upkeep, 74 against 56

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 Ling-3.0-tiny +45

Ling-3.0-tiny 95

Memory earns the full 30, since inclusionAI's own Q4_K_M GGUF is 4.8 GB, about 6 GB with a fifth added. Runtimes earn the full 25, from released Transformers, vLLM, SGLang and llama.cpp, and Ollama, whose v0.40.14 (2 November 2026) pins llama.cpp b11963 with the bailingmoe3 architecture (Ollama v0.40.7 of 20 October already pinned b11738, which has it). LM Studio has nothing. Builds earn 15 for FP8, INT4 and four GGUF precisions from inclusionAI. MIT with nothing added gives terms the full 15 and the ungated repositories give download the full 10. Hosted too scores 0, because the Hub's model page lists no inference provider and no inclusionAI or Ant Group API serving it was found.

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 OTel-2.0-LLM-31B-IT +18

Ling-3.0-tiny 56

Model card 11, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't. Training data 15, a data card with sources, size, cut-off and filtering. Last change 15, the newest commit is still the card change of 24 September 2026, 41 days before 4 November. Responsiveness 10, six of 16 discussions answered by an inclusionAI member, some. Version policy 5, a first release at this size. File health 0, the card's MTP recipe contradicts the files and a broken index size waits without a reply.

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.

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

Ling-3.0-tiny 50

File safety gets 15, safetensors and GGUF only, but the card's vLLM command runs the repository's config code with --trust-remote-code. Provenance gets 15 for files in inclusionAI's own organisation with a checksum on each. Safety evaluation is 0, since SingProbe's results grade the probe, not the model. Agent guidance gets 5 for the SingProbe guardrail inclusionAI publishes for this model, with no statement of trained refusals. MIT carries no licence deductions (15). No security contact or disclosure policy was found (0).

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

CategoryWeight this runLing-3.0-tinyOTel-2.0-LLM-31B-ITEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259550Ling-3.0-tiny +45
Risk20%205055OTel-2.0-LLM-31B-IT +5
Agent interface10%106060even
Documentation and upkeep10%105674OTel-2.0-LLM-31B-IT +18
Negative events≤1500
TotalC 56.2/100C 56.8/100

Facts side by side

FactLing-3.0-tinyOTel-2.0-LLM-31B-IT
KindOpen-weight modelOpen-weight model
VendorinclusionAI (Ant Group)AT&T (Open Telco AI)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-312026-11-01
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

Ling-3.0-tiny

A small, quick hybrid reasoning model for local agent work, tool calls and coding, under MIT. It runs in about 6 GB from inclusionAI's 4-bit GGUF in released Transformers, vLLM, SGLang, llama.cpp and Ollama, with no host. The risks are a card that doesn't match the files in places, a vLLM route running repository code, and no safety results.

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

Ling-3.0-tiny

  1. Start it with llama-server -hf inclusionAI/Ling-3.0-tiny-GGUF:Q4_K_M --jinja -c 32768, which needs llama.cpp b11772 or a recent release with bailingmoe3
  2. With vLLM 0.32.0, vllm serve inclusionAI/Ling-3.0-tiny --trust-remote-code --enable-prefix-caching --mamba-cache-mode align --enable-auto-tool-choice --tool-call-parser ling3 --reasoning-parser ling3, which runs the repository's config code
  3. With SGLang 0.5.22, its cookbook uses --reasoning-parser deepseek-r1 --tool-call-parser glm45 for this model, and drop the card's NEXTN flags since tiny has no MTP layer
  4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks
  5. Sampling per the card is temperature 1.0, top_p 0.95 and top_k 20
  6. The template keeps earlier reasoning in the prompt, which grows long agent sessions
  7. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
  8. For a guardrail, inclusionAI's Ling-3.0-tiny-singprobe scores intent, unsafe output and hallucination per token, but only through SGLang and vLLM integration branches

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

Questions

Which is better for AI agents, Ling-3.0-tiny or OTel-2.0-LLM-31B-IT?

OTel-2.0-LLM-31B-IT and Ling-3.0-tiny score within a point of each other on agent readiness, 56.8 (C) and 56.2 (C). Ling-3.0-tiny leads on reach.

Other comparisons with Ling-3.0-tiny or OTel-2.0-LLM-31B-IT

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.