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
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
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
| Category | Weight this run | Ling-3.0-tiny | Ling-3.1-flash-1019 | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 95 | 60 | Ling-3.0-tiny +35 |
| Risk | 20%20 | 50 | 45 | Ling-3.0-tiny +5 |
| Agent interface | 10%10 | 60 | 60 | even |
| Documentation and upkeep | 10%10 | 56 | 56 | even |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 56.2/100 | C 54.8/100 |
Facts side by side
| Fact | Ling-3.0-tiny | Ling-3.1-flash-1019 |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | inclusionAI (Ant Group) | inclusionAI (Ant Group) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | MIT |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-08-31 | 2026-11-04 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 2.8/5 (4) | none |
How the scores have moved
Ling-3.1-flash-1019
No score change since it was listed.
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
- 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 - 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 - With SGLang 0.5.22, its cookbook uses
--reasoning-parser deepseek-r1 --tool-call-parser glm45for this model, and drop the card's NEXTN flags since tiny has no MTP layer - Thinking is on by default, pass
chat_template_kwargswithenable_thinkingfalse for short tasks - Sampling per the card is temperature 1.0, top_p 0.95 and top_k 20
- The template keeps earlier reasoning in the prompt, which grows long agent sessions
- Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
- 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
- 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
- With vLLM pass
--trust-remote-code,--tool-call-parser ling3and--reasoning-parser ling3 - Set
chat_template_kwargsenable_thinkingfalse for direct answers. Reasoning comes back inreasoning_contentper SGLang's cookbook - Plan on 262,144 tokens of context. The 1M figure needs the YaRN override in SGLang's cookbook
- Use temperature 1.0, top_p 0.95 and top_k 20, per the card
- 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
- Agents-A1-4B vs Ling-3.0-tiny
- Agents-A1-4B vs Ling-3.1-flash-1019
- Apertus v1.5 8B vs Ling-3.0-tiny
- Apertus v1.5 8B vs Ling-3.1-flash-1019
- Apodex-1.1-mini vs Ling-3.0-tiny
- Apodex-1.1-mini vs Ling-3.1-flash-1019
- Arete-27B vs Ling-3.0-tiny
- Arete-27B vs Ling-3.1-flash-1019
- BigBang-v1 vs Ling-3.0-tiny
- BigBang-v1 vs Ling-3.1-flash-1019
- Carbon-X vs Ling-3.0-tiny
- Carbon-X vs Ling-3.1-flash-1019
- Cosmos-Reason2-2B vs Ling-3.0-tiny
- Cosmos-Reason2-2B vs Ling-3.1-flash-1019
- Darwin-36B-Opus vs Ling-3.0-tiny
- Darwin-36B-Opus vs Ling-3.1-flash-1019
- DeepSeek-V3.2 vs Ling-3.0-tiny
- DeepSeek-V3.2 vs Ling-3.1-flash-1019
- DeepSeek V4.1 Flash vs Ling-3.0-tiny
- DeepSeek V4.1 Flash vs Ling-3.1-flash-1019
- DeepSeek-V4-Flash-0731 vs Ling-3.0-tiny
- DeepSeek-V4-Flash-0731 vs Ling-3.1-flash-1019
- DiffusionGemma 26B A4B IT vs Ling-3.0-tiny
- DiffusionGemma 26B A4B IT vs Ling-3.1-flash-1019
- Gemma 4 12B IT vs Ling-3.0-tiny
- Gemma 4 12B IT vs Ling-3.1-flash-1019
- Gemma 4 26B A4B IT vs Ling-3.0-tiny
- Gemma 4 26B A4B IT vs Ling-3.1-flash-1019
- Gemma 4 31B IT vs Ling-3.0-tiny
- Gemma 4 31B IT vs Ling-3.1-flash-1019
- Gemma 4 E2B IT vs Ling-3.0-tiny
- Gemma 4 E2B IT vs Ling-3.1-flash-1019
- Gemma 4 E4B IT vs Ling-3.0-tiny
- Gemma 4 E4B IT vs Ling-3.1-flash-1019
- GLM-4.5-Air vs Ling-3.0-tiny
- GLM-4.5-Air vs Ling-3.1-flash-1019
- GLM-4.7-Flash vs Ling-3.0-tiny
- GLM-4.7-Flash vs Ling-3.1-flash-1019
- GLM-5.3-Flash vs Ling-3.0-tiny
- GLM-5.3-Flash vs Ling-3.1-flash-1019
- GLM-5.3 vs Ling-3.0-tiny
- GLM-5.3 vs Ling-3.1-flash-1019
- gpt-oss-120b vs Ling-3.0-tiny
- gpt-oss-120b vs Ling-3.1-flash-1019
- gpt-oss-20b vs Ling-3.0-tiny
- gpt-oss-20b vs Ling-3.1-flash-1019
- Granite 4.2 30B vs Ling-3.0-tiny
- Granite 4.2 30B vs Ling-3.1-flash-1019
- Granite 4.2 3B vs Ling-3.0-tiny
- Granite 4.2 3B vs Ling-3.1-flash-1019
- Granite 4.2 8B vs Ling-3.0-tiny
- Granite 4.2 8B vs Ling-3.1-flash-1019
- Hy-Memory-30B-A3B vs Ling-3.0-tiny
- Hy-Memory-30B-A3B vs Ling-3.1-flash-1019
- Hy3 vs Ling-3.0-tiny
- Hy3 vs Ling-3.1-flash-1019
- Inkling-Small vs Ling-3.0-tiny
- Inkling-Small vs Ling-3.1-flash-1019
- Inkling vs Ling-3.0-tiny
- Inkling vs Ling-3.1-flash-1019
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Ling-3.0-tiny
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Ling-3.1-flash-1019
- Kimi K3.1 Pro vs Ling-3.0-tiny
- Kimi K3.1 Pro vs Ling-3.1-flash-1019
- Kimi K3 vs Ling-3.0-tiny
- Kimi K3 vs Ling-3.1-flash-1019
- Kolibri-1 vs Ling-3.0-tiny
- Kolibri-1 vs Ling-3.1-flash-1019
- Kronos vs Ling-3.0-tiny
- Kronos vs Ling-3.1-flash-1019
- Laguna M.1 vs Ling-3.0-tiny
- Laguna M.1 vs Ling-3.1-flash-1019
- Laguna S 2.1 vs Ling-3.0-tiny
- Laguna S 2.1 vs Ling-3.1-flash-1019
- Laguna XS 2.1 vs Ling-3.0-tiny
- Laguna XS 2.1 vs Ling-3.1-flash-1019
- LBS-27B vs Ling-3.0-tiny
- LBS-27B vs Ling-3.1-flash-1019
- LFM2.5-2.6B vs Ling-3.0-tiny
- LFM2.5-2.6B vs Ling-3.1-flash-1019
- LFM3-1.7B vs Ling-3.0-tiny
- LFM3-1.7B vs Ling-3.1-flash-1019
- LFM3-Audio-2B vs Ling-3.0-tiny
- LFM3-Audio-2B vs Ling-3.1-flash-1019
- LFM3-Omni-2B vs Ling-3.0-tiny
- LFM3-Omni-2B vs Ling-3.1-flash-1019
- LFM3-VL-2B vs Ling-3.0-tiny
- LFM3-VL-2B vs Ling-3.1-flash-1019
- Ling-3.0-tiny vs MiMo-V2.6 Distill Qwen 9B
- Ling-3.0-tiny vs MiniCPM-o 4.5
- Ling-3.0-tiny vs MiniCPM-V 4.7 1B
- Ling-3.0-tiny vs MiniCPM-V 4.7 35B-A3B
- Ling-3.0-tiny vs MiniCPM5-2B
- Ling-3.0-tiny vs MiniMax-M2.5
- Ling-3.0-tiny vs MiniMax-M2.7
- Ling-3.0-tiny vs MiniMax-M3.1-Flash
- Ling-3.0-tiny vs Mistral Large 4
- Ling-3.0-tiny vs Muse Glimmer 30B
- Ling-3.0-tiny vs Nanbeige4.3-33B
- Ling-3.0-tiny vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Ling-3.0-tiny vs Nemotron 3.5 Lightning 30B A3B
- Ling-3.0-tiny vs Nemotron 3 Nano 30B A3B
- Ling-3.0-tiny vs Nemotron 3 Nano 4B
- Ling-3.0-tiny vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Ling-3.0-tiny vs Nemotron 3 Super 120B A12B
- Ling-3.0-tiny vs Nemotron 3 Ultra 550B A55B
- Ling-3.0-tiny vs occamy-1.0
- Ling-3.0-tiny vs Olmo 3 7B Think
- Ling-3.0-tiny vs Ornith-1.5-122B
- Ling-3.0-tiny vs Ornith-1.5-35B-A3B
- Ling-3.0-tiny vs Ornith-1.5-397B
- Ling-3.0-tiny vs Ornith-1.5-9B
- Ling-3.0-tiny vs Qwen-AgentWorld-35B-A3B
- Ling-3.0-tiny vs Qwen3-30B-A3B-Instruct-2507
- Ling-3.0-tiny vs Qwen3-4B-Instruct-2507
- Ling-3.0-tiny vs Qwen3.5-0.8B
- Ling-3.0-tiny vs Qwen3.5-122B-A10B
- Ling-3.0-tiny vs Qwen3.5-2B
- Ling-3.0-tiny vs Qwen3.5-397B-A17B
- Ling-3.0-tiny vs Qwen3.5-4B
- Ling-3.0-tiny vs Qwen3.5-9B
- Ling-3.0-tiny vs Qwen3.6-27B
- Ling-3.0-tiny vs Qwen3.6-35B-A3B
- Ling-3.0-tiny vs Qwen3.8-27B
- Ling-3.0-tiny vs Qwen3.8-Flash-Next
- Ling-3.0-tiny vs Qwen3-Coder-30B-A3B-Instruct
- Ling-3.0-tiny vs Qwen3-Coder-Next
- Ling-3.0-tiny vs Qwen3-Omni-30B-A3B-Instruct
- Ling-3.0-tiny vs Qwen3-VL-2B-Instruct
- Ling-3.0-tiny vs Qwen3-VL-30B-A3B-Instruct
- Ling-3.0-tiny vs Qwen3-VL-32B-Instruct
- Ling-3.0-tiny vs Qwen3-VL-4B-Instruct
- Ling-3.0-tiny vs Qwen3-VL-8B-Instruct
- Ling-3.0-tiny vs Qwopus3.8-27B-Flash-V2
- Ling-3.0-tiny vs Recursive Flint
- Ling-3.0-tiny vs Ripple-65B Preview
- Ling-3.0-tiny vs SmolLM3-3B
- Ling-3.0-tiny vs Spark-X2.6-4B
- Ling-3.0-tiny vs Swift 1.5 Qwen3.8-27B
- Ling-3.0-tiny vs Swift 1.5 Qwen3.8-Flash-Next
- Ling-3.0-tiny vs ThinkingCap (Qwen3.8 27B)
- Ling-3.0-tiny vs Baidu Unlimited-OCR-2
- Ling-3.1-flash-1019 vs MiMo-V2.6 Distill Qwen 9B
- Ling-3.1-flash-1019 vs MiniCPM-o 4.5
- Ling-3.1-flash-1019 vs MiniCPM-V 4.7 1B
- Ling-3.1-flash-1019 vs MiniCPM-V 4.7 35B-A3B
- Ling-3.1-flash-1019 vs MiniCPM5-2B
- Ling-3.1-flash-1019 vs MiniMax-M2.5
- Ling-3.1-flash-1019 vs MiniMax-M2.7
- Ling-3.1-flash-1019 vs MiniMax-M3.1-Flash
- Ling-3.1-flash-1019 vs Mistral Large 4
- Ling-3.1-flash-1019 vs Muse Glimmer 30B
- Ling-3.1-flash-1019 vs Nanbeige4.3-33B
- Ling-3.1-flash-1019 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Ling-3.1-flash-1019 vs Nemotron 3.5 Lightning 30B A3B
- Ling-3.1-flash-1019 vs Nemotron 3 Nano 30B A3B
- Ling-3.1-flash-1019 vs Nemotron 3 Nano 4B
- Ling-3.1-flash-1019 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Ling-3.1-flash-1019 vs Nemotron 3 Super 120B A12B
- Ling-3.1-flash-1019 vs Nemotron 3 Ultra 550B A55B
- Ling-3.1-flash-1019 vs occamy-1.0
- Ling-3.1-flash-1019 vs Olmo 3 7B Think
- Ling-3.1-flash-1019 vs Ornith-1.5-122B
- Ling-3.1-flash-1019 vs Ornith-1.5-35B-A3B
- Ling-3.1-flash-1019 vs Ornith-1.5-397B
- Ling-3.1-flash-1019 vs Ornith-1.5-9B
- Ling-3.1-flash-1019 vs Qwen-AgentWorld-35B-A3B
- Ling-3.1-flash-1019 vs Qwen3-30B-A3B-Instruct-2507
- Ling-3.1-flash-1019 vs Qwen3-4B-Instruct-2507
- Ling-3.1-flash-1019 vs Qwen3.5-0.8B
- Ling-3.1-flash-1019 vs Qwen3.5-122B-A10B
- Ling-3.1-flash-1019 vs Qwen3.5-2B
- Ling-3.1-flash-1019 vs Qwen3.5-397B-A17B
- Ling-3.1-flash-1019 vs Qwen3.5-4B
- Ling-3.1-flash-1019 vs Qwen3.5-9B
- Ling-3.1-flash-1019 vs Qwen3.6-27B
- Ling-3.1-flash-1019 vs Qwen3.6-35B-A3B
- Ling-3.1-flash-1019 vs Qwen3.8-27B
- Ling-3.1-flash-1019 vs Qwen3.8-Flash-Next
- Ling-3.1-flash-1019 vs Qwen3-Coder-30B-A3B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-Coder-Next
- Ling-3.1-flash-1019 vs Qwen3-Omni-30B-A3B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-VL-2B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-VL-30B-A3B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-VL-32B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-VL-4B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-VL-8B-Instruct
- Ling-3.1-flash-1019 vs Qwopus3.8-27B-Flash-V2
- Ling-3.1-flash-1019 vs Recursive Flint
- Ling-3.1-flash-1019 vs Ripple-65B Preview
- Ling-3.1-flash-1019 vs SmolLM3-3B
- Ling-3.1-flash-1019 vs Spark-X2.6-4B
- Ling-3.1-flash-1019 vs Swift 1.5 Qwen3.8-27B
- Ling-3.1-flash-1019 vs Swift 1.5 Qwen3.8-Flash-Next
- Ling-3.1-flash-1019 vs ThinkingCap (Qwen3.8 27B)
- Ling-3.1-flash-1019 vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/ling-3-0-tiny-vs-ling-3-1-flash-1019.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/ling-3-0-tiny.json·/api/v1/tools/ling-3-1-flash-1019.json - From a terminal
anchor compare ling-3-0-tiny ling-3-1-flash-1019(the CLI) - Over MCP
compare_tools {"a": "ling-3-0-tiny", "b": "ling-3-1-flash-1019"}at/mcp, no key