Head to head · Open-weight models you run yourself · October 2026 research run
Hy3 vs Ling-3.1-flash-1019
Hy3 scores 62.6 (B) on agent readiness against Ling-3.1-flash-1019's 54.8 (C), and leads in 3 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
Hy3 B
Best for Teams with an 8-GPU server who want an agent-tuned MoE model under plain Apache 2.0
Ahead on
- Reach, 70 against 60
- Risk, 60 against 45
- Agent interface, 75 against 60
Watch for
597.6 GB in BF16, 299.9 GB in FP8 and 168.5 GB at the smallest 4-bit build
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.
Risk Hy3 +15
Hy3 60
File safety earns the full 25, safetensors only with no pickle files, and the documented route runs vLLM or SGLang from their own code with a Jinja template, so nothing from the repository runs at load or prompt time. Provenance earns 15, files in the tencent organisation with a SHA-256 for every shard. Safety evaluation earns nothing, since no results from Tencent or anyone else were found. Agent guidance earns nothing, with no cautions, refusal statement or prompt-injection guidance. Licence risk keeps all 15 under plain Apache 2.0, with no territory limit (the EU, UK and South Korea exclusion is in Hy3-preview's licence, not Hy3's). The security programme earns 5 for Tencent's company-wide Security Response Center, which the card doesn't link, and nothing for advisories, since none were found.
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.
Agent interface Hy3 +15
Hy3 75
The chat template earns 20, a chat_template.jinja in the repository. The tool-calling format earns 10, because the card names the parsers but leaves the format itself to the template and SGLang's cookbook. Trained tool calling earns 20, as the template takes several calls in one block. Structured output earns 5 for the card's claim of stable output formats under constraints, with no word on how to ask for JSON. Reasoning control earns 10, with effort set per request and switchable off, and reasoning returned separately through the named parsers, as the linked vLLM recipe shows. Context earns 10 for 262,144 tokens native.
Ling-3.1-flash-1019 60
Chat template 20, chat_template.jinja in the repository (6,042 characters), which handles tools, the thinking switch and preserved reasoning. Tool-calling format 10, only the template says how tools are declared (JSON in <tools>) and how calls come back (<tool_call>name with <arg_key> and <arg_value> pairs). Trained tool calling 20, the template tells the model it may call one or more functions and loops over every entry in an assistant message's tool_calls, and the card reports gains on agentic benchmarks, AA-Briefcase and AutomationBench-AA among them. Structured output 0, the card doesn't document JSON or JSON Schema output. Reasoning control 0, the card documents turning thinking on or off per request with chat_template_kwargs enable_thinking, and names the ling3 reasoning parser, but doesn't say where the reasoning text comes back. Context 10, 262,144 tokens natively in config.json (max_position_embeddings 262144, rope_scaling null) and per SGLang's cookbook. 20 + 10 + 20 + 0 + 0 + 10 = 60.
Reach Hy3 +10
Hy3 70
Memory earns 5, because the smallest build of 4-bit precision or better is AngelSlim's GPTQ-Int4 of 168.5 GB, about 202 GB with the fifth added, which is within 256 GB but beyond any single workstation. The 1-bit IQ1_M GGUF fits our reference machine but sits below the 4-bit line. Runtimes earn 20, for model code in released Transformers, vLLM, SGLang and llama.cpp; Ollama and LM Studio have no entry for it. Builds earn the full 15, with Tencent's FP8 repository and AngelSlim's GPTQ and GGUF builds. Terms earn 15 for plain Apache 2.0. Download earns 10, with no gate and no account. Hosted earns 5, since Featherless AI and DeepInfra serve it live through Hugging Face.
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.
Score by category
| Category | Weight this run | Hy3 | Ling-3.1-flash-1019 | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 70 | 60 | Hy3 +10 |
| Risk | 20%20 | 60 | 45 | Hy3 +15 |
| Agent interface | 10%10 | 75 | 60 | Hy3 +15 |
| Documentation and upkeep | 10%10 | 56 | 56 | even |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.6/100 | C 54.8/100 |
Facts side by side
| Fact | Hy3 | Ling-3.1-flash-1019 |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Tencent (Hy team) | inclusionAI (Ant Group) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-07-20 | 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 |
Verdicts
Hy3
Hy3 is a 295B mixture-of-experts model with 21B active, trained for several tool calls a turn, with per-request reasoning effort and 256K of context. It needs an 8-GPU server for FP8 or about 200 GB for a 4-bit build. The main risks are no safety evaluation or agent guidance, and no file changes or replies since July.
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
Hy3
- Start it with vLLM on 8 GPUs, vllm serve tencent/Hy3-FP8 --tensor-parallel-size 8 --tool-call-parser hy_v3 --reasoning-parser hy_v3 --enable-auto-tool-choice --served-model-name hy3
- In SGLang use --tool-call-parser hunyuan --reasoning-parser hunyuan, as the card shows
- Pass reasoning_effort (no_think, low or high) in chat_template_kwargs; the default is no_think, and any other value raises a template error
- With the vLLM reasoning parser the chain of thought comes back in message.reasoning and the answer in message.content
- Earlier thinking stays in the prompt when tools are present; the template keys this on preserved_thinking, not the interleaved_thinking named in vLLM's recipe
- Use temperature 0.9 and top_p 1.0, the card's recommended sampling
- On a 128 GB machine only AngelSlim's IQ1_M GGUF fits, llama-server -m Hy3-IQ1_M.gguf -ctk q8_0 -ctv q8_0 -fa on -c 65536, with llama.cpp b11768 or later; at 89.4 GB × 1.2 it sits right at the 107.4 GB ceiling, so shorten the context if it fails to load, and expect a 1-bit build to fall short of Tencent's numbers
- Without the hardware, call it through Featherless AI or DeepInfra via Hugging Face's inference providers
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, Hy3 or Ling-3.1-flash-1019?
Hy3 scores 62.6 (B) on agent readiness against Ling-3.1-flash-1019's 54.8 (C), and leads in 3 of 4 scored categories.
Other comparisons with Hy3 or Ling-3.1-flash-1019
- Agents-A1-4B vs Hy3
- Agents-A1-4B vs Ling-3.1-flash-1019
- Apertus v1.5 8B vs Hy3
- Apertus v1.5 8B vs Ling-3.1-flash-1019
- Apodex-1.1-mini vs Hy3
- Apodex-1.1-mini vs Ling-3.1-flash-1019
- Arete-27B vs Hy3
- Arete-27B vs Ling-3.1-flash-1019
- BigBang-v1 vs Hy3
- BigBang-v1 vs Ling-3.1-flash-1019
- Carbon-X vs Hy3
- Carbon-X vs Ling-3.1-flash-1019
- Cosmos-Reason2-2B vs Hy3
- Cosmos-Reason2-2B vs Ling-3.1-flash-1019
- Darwin-36B-Opus vs Hy3
- Darwin-36B-Opus vs Ling-3.1-flash-1019
- DeepSeek-V3.2 vs Hy3
- DeepSeek-V3.2 vs Ling-3.1-flash-1019
- DeepSeek V4.1 Flash vs Hy3
- DeepSeek V4.1 Flash vs Ling-3.1-flash-1019
- DeepSeek-V4-Flash-0731 vs Hy3
- DeepSeek-V4-Flash-0731 vs Ling-3.1-flash-1019
- DiffusionGemma 26B A4B IT vs Hy3
- DiffusionGemma 26B A4B IT vs Ling-3.1-flash-1019
- Gemma 4 12B IT vs Hy3
- Gemma 4 12B IT vs Ling-3.1-flash-1019
- Gemma 4 26B A4B IT vs Hy3
- Gemma 4 26B A4B IT vs Ling-3.1-flash-1019
- Gemma 4 31B IT vs Hy3
- Gemma 4 31B IT vs Ling-3.1-flash-1019
- Gemma 4 E2B IT vs Hy3
- Gemma 4 E2B IT vs Ling-3.1-flash-1019
- Gemma 4 E4B IT vs Hy3
- Gemma 4 E4B IT vs Ling-3.1-flash-1019
- GLM-4.5-Air vs Hy3
- GLM-4.5-Air vs Ling-3.1-flash-1019
- GLM-4.7-Flash vs Hy3
- GLM-4.7-Flash vs Ling-3.1-flash-1019
- GLM-5.3-Flash vs Hy3
- GLM-5.3-Flash vs Ling-3.1-flash-1019
- GLM-5.3 vs Hy3
- GLM-5.3 vs Ling-3.1-flash-1019
- gpt-oss-120b vs Hy3
- gpt-oss-120b vs Ling-3.1-flash-1019
- gpt-oss-20b vs Hy3
- gpt-oss-20b vs Ling-3.1-flash-1019
- Granite 4.2 30B vs Hy3
- Granite 4.2 30B vs Ling-3.1-flash-1019
- Granite 4.2 3B vs Hy3
- Granite 4.2 3B vs Ling-3.1-flash-1019
- Granite 4.2 8B vs Hy3
- Granite 4.2 8B vs Ling-3.1-flash-1019
- Hy-Memory-30B-A3B vs Hy3
- Hy-Memory-30B-A3B vs Ling-3.1-flash-1019
- Hy3 vs Inkling
- Hy3 vs Inkling-Small
- Hy3 vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Hy3 vs Kimi K3
- Hy3 vs Kimi K3.1 Pro
- Hy3 vs Kolibri-1
- Hy3 vs Kronos
- Hy3 vs Laguna M.1
- Hy3 vs Laguna S 2.1
- Hy3 vs Laguna XS 2.1
- Hy3 vs LBS-27B
- Hy3 vs LFM2.5-2.6B
- Hy3 vs LFM3-1.7B
- Hy3 vs LFM3-Audio-2B
- Hy3 vs LFM3-Omni-2B
- Hy3 vs LFM3-VL-2B
- Hy3 vs Ling-3.0-tiny
- Hy3 vs MiMo-V2.6 Distill Qwen 9B
- Hy3 vs MiniCPM-o 4.5
- Hy3 vs MiniCPM-V 4.7 1B
- Hy3 vs MiniCPM-V 4.7 35B-A3B
- Hy3 vs MiniCPM5-2B
- Hy3 vs MiniMax-M2.5
- Hy3 vs MiniMax-M2.7
- Hy3 vs MiniMax-M3.1-Flash
- Hy3 vs Mistral Large 4
- Hy3 vs Muse Glimmer 30B
- Hy3 vs Nanbeige4.3-33B
- Hy3 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Hy3 vs Nemotron 3.5 Lightning 30B A3B
- Hy3 vs Nemotron 3 Nano 30B A3B
- Hy3 vs Nemotron 3 Nano 4B
- Hy3 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Hy3 vs Nemotron 3 Super 120B A12B
- Hy3 vs Nemotron 3 Ultra 550B A55B
- Hy3 vs occamy-1.0
- Hy3 vs Olmo 3 7B Think
- Hy3 vs Ornith-1.5-122B
- Hy3 vs Ornith-1.5-35B-A3B
- Hy3 vs Ornith-1.5-397B
- Hy3 vs Ornith-1.5-9B
- Hy3 vs Qwen-AgentWorld-35B-A3B
- Hy3 vs Qwen3-30B-A3B-Instruct-2507
- Hy3 vs Qwen3-4B-Instruct-2507
- Hy3 vs Qwen3.5-0.8B
- Hy3 vs Qwen3.5-122B-A10B
- Hy3 vs Qwen3.5-2B
- Hy3 vs Qwen3.5-397B-A17B
- Hy3 vs Qwen3.5-4B
- Hy3 vs Qwen3.5-9B
- Hy3 vs Qwen3.6-27B
- Hy3 vs Qwen3.6-35B-A3B
- Hy3 vs Qwen3.8-27B
- Hy3 vs Qwen3.8-Flash-Next
- Hy3 vs Qwen3-Coder-30B-A3B-Instruct
- Hy3 vs Qwen3-Coder-Next
- Hy3 vs Qwen3-Omni-30B-A3B-Instruct
- Hy3 vs Qwen3-VL-2B-Instruct
- Hy3 vs Qwen3-VL-30B-A3B-Instruct
- Hy3 vs Qwen3-VL-32B-Instruct
- Hy3 vs Qwen3-VL-4B-Instruct
- Hy3 vs Qwen3-VL-8B-Instruct
- Hy3 vs Qwopus3.8-27B-Flash-V2
- Hy3 vs Recursive Flint
- Hy3 vs Ripple-65B Preview
- Hy3 vs SmolLM3-3B
- Hy3 vs Spark-X2.6-4B
- Hy3 vs Swift 1.5 Qwen3.8-27B
- Hy3 vs Swift 1.5 Qwen3.8-Flash-Next
- Hy3 vs ThinkingCap (Qwen3.8 27B)
- Hy3 vs Baidu Unlimited-OCR-2
- Inkling-Small vs Ling-3.1-flash-1019
- Inkling vs Ling-3.1-flash-1019
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Ling-3.1-flash-1019
- Kimi K3.1 Pro vs Ling-3.1-flash-1019
- Kimi K3 vs Ling-3.1-flash-1019
- Kolibri-1 vs Ling-3.1-flash-1019
- Kronos vs Ling-3.1-flash-1019
- Laguna M.1 vs Ling-3.1-flash-1019
- Laguna S 2.1 vs Ling-3.1-flash-1019
- Laguna XS 2.1 vs Ling-3.1-flash-1019
- LBS-27B vs Ling-3.1-flash-1019
- LFM2.5-2.6B vs Ling-3.1-flash-1019
- LFM3-1.7B vs Ling-3.1-flash-1019
- LFM3-Audio-2B vs Ling-3.1-flash-1019
- LFM3-Omni-2B vs Ling-3.1-flash-1019
- LFM3-VL-2B vs Ling-3.1-flash-1019
- Ling-3.0-tiny vs Ling-3.1-flash-1019
- 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/hy3-vs-ling-3-1-flash-1019.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hy3.json·/api/v1/tools/ling-3-1-flash-1019.json - From a terminal
anchor compare hy3 ling-3-1-flash-1019(the CLI) - Over MCP
compare_tools {"a": "hy3", "b": "ling-3-1-flash-1019"}at/mcp, no key