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

Ling-3.0-tiny vs Ling-3.1-flash-1019

Ling-3.0-tiny scores 56.2 (C) on agent readiness against Ling-3.1-flash-1019's 54.8 (C), and leads in 2 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 4969 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 60
  • Risk, 50 against 45

Watch for

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

Ling-3.1-flash-1019 C

Best for Teams with a multi-GPU server that want an MIT-licensed flagship for long agent runs and coding

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

574 GB in FP8 with no smaller build from inclusionAI, so no single machine under 690 GB of GPU memory runs it

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

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.

Ling-3.1-flash-1019 60

Memory 0, inclusionAI's only build is the FP8 release at 573.78 GB, × 1.2 = 688.5 GB, above 256 GB, and no runtime's library has a build. Runtimes 25, Released model code in Transformers 5.22.2 (bailing_hybrid), vLLM 0.33.0 (BailingMoeV3ForCausalLM, with ling3 tool and reasoning parsers), SGLang 0.5.23 (bailing_moe_v3.py, its bailing_hybrid config and MTP module) and llama.cpp b12242 (bailingmoe3), and Ollama, credited through its pinned llama.cpp as on the Ling-3.0-tiny listing: v0.40.16 sets LLAMA_CPP_VERSION to b12177. Builds 10, the release is FP8, the one quantised precision inclusionAI publishes for it. Terms 15, MIT in the card's metadata, with no use policy or other terms added on the card or in the repository. Download 10, the Hub API's model info gives gated false on 10 November 2026, so the files download with no account and no terms to accept. Hosted 0, the Hub API's provider mapping is empty for this repository on 10 November 2026. 0 + 25 + 10 + 15 + 10 + 0 = 60.

Risk Ling-3.0-tiny +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).

Ling-3.1-flash-1019 45

File safety 15, safetensors only, no .bin, .pt or .pth files (25), less 10 because the card's documented vLLM command passes --trust-remote-code, which runs the repository's configuration_bailing_moe_v3.py, since vLLM 0.33.0 registers no bailing_hybrid config of its own. Provenance 15, files in the inclusionAI organisation that inclusion-ai.org links to, per the Ling-3.0-tiny listing (10). Safety evaluation 0, no safety results for the model on its card or in the training-content summary. Agent guidance 0, the card has nothing on prompt injection, refusals or safeguards, and inclusionAI publishes no guardrail probe for this model as it did for Ling 3.0. Licence risk 15, MIT with no use policy, no field-of-use limits, no threshold and no clause letting inclusionAI change or revoke it. Security programme 0, www.inclusion-ai.org answers 404 for security.txt on 10 November 2026, and the Ling-3.0-tiny listing found no SECURITY.md or disclosure policy in the inclusionAI .github repository. 15 + 15 + 0 + 0 + 15 + 0 = 45.

Score by category

CategoryWeight this runLing-3.0-tinyLing-3.1-flash-1019Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259560Ling-3.0-tiny +35
Risk20%205045Ling-3.0-tiny +5
Agent interface10%106060even
Documentation and upkeep10%105656even
Negative events≤1500
TotalC 56.2/100C 54.8/100

Facts side by side

FactLing-3.0-tinyLing-3.1-flash-1019
KindOpen-weight modelOpen-weight model
VendorinclusionAI (Ant Group)inclusionAI (Ant Group)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITMIT
Read-only variant documentednono
llms.txtnono
Last release2026-08-312026-11-04
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.

Ling-3.1-flash-1019

inclusionAI's newest flagship, a 560B hybrid mixture of experts under plain MIT that vLLM, SGLang, Transformers and llama.cpp run in released versions. It ships only as 574 GB of FP8, so it needs a multi-GPU server. The card overstates the context, documents little about tool calls, and has no safety results.

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

Ling-3.1-flash-1019

  1. Serve it with SGLang 0.5.23 or later on 8 H200 or 4 GB300 GPUs, per the card, and use this repository's name as the model path, not the earlier one the card's command shows
  2. With vLLM pass --trust-remote-code, --tool-call-parser ling3 and --reasoning-parser ling3
  3. Set chat_template_kwargs enable_thinking false for direct answers. Reasoning comes back in reasoning_content per SGLang's cookbook
  4. Plan on 262,144 tokens of context. The 1M figure needs the YaRN override in SGLang's cookbook
  5. Use temperature 1.0, top_p 0.95 and top_k 20, per the card
  6. Validate JSON output yourself, since structured output isn't documented

Questions

Which is better for AI agents, Ling-3.0-tiny or Ling-3.1-flash-1019?

Ling-3.0-tiny scores 56.2 (C) on agent readiness against Ling-3.1-flash-1019's 54.8 (C), and leads in 2 of 4 scored categories.

Other comparisons with Ling-3.0-tiny or Ling-3.1-flash-1019

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.