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

Ling-3.1-flash-1019 vs Qwen3-Omni-30B-A3B-Instruct

Ling-3.1-flash-1019 scores 54.8 (C) on agent readiness against Qwen3-Omni-30B-A3B-Instruct's 41.8 (E), and leads in 2 of 4 scored categories. Qwen3-Omni-30B-A3B-Instruct leads on risk. 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

Best conversational voice-agent APIs · All 581 voice agents comparisons

Which one, for what

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

Ahead on

  • Reach, 60 against 55
  • Documentation and upkeep, 56 against 26

Watch for

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

Qwen3-Omni-30B-A3B-Instruct E

Best for Agents on a machine with about 96 GB to spare that need one local model to hear, see and answer by voice

Ahead on

  • Risk, 55 against 45

Watch for

Only a 70.5 GB BF16 build, about 85 GB to run, with no quantised build from Alibaba

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 Ling-3.1-flash-1019 +30

Ling-3.1-flash-1019 56

Model card 11, Intended use (complex reasoning, multi-step tasks and agentic workflows), architecture, parameters (560B total, 25B active) and context (1M claimed) are on the card. Training data 15, the training-content summary the card links names the source categories (Common Crawl and other public datasets, commercially licensed data, the Ant Spider crawler, synthetic data), the size band (over 10 trillion text tokens), data collected up to about July 2026 and the filtering, without listing datasets with sizes. Last change 20, the newest commit, on 4 November 2026, edited the card, six days before this check, and the files went up on 27 October. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (both opened on 27 October 2026) has a reply from an inclusionAI member. Version policy 5, the update went into a repository of its own and Ling-3.1-flash and Ling 3.0 stay in theirs. File health 5, the card states a 1M-token context while config.json gives 262,144 with no rope scaling, and its serve commands name the earlier repository as the model path. 11 + 15 + 20 + 0 + 5 + 5 = 56.

Qwen3-Omni-30B-A3B-Instruct 26

Model card 11, intended use, architecture, parameters and languages are there, limitations, context and a cut-off aren't. Training data 5, the report's description has no cut-off. Last change 0, nothing that runs the model has changed for over a year. Responsiveness 0, Qwen answered none of the 40 most recent discussions. Version policy 5, Qwen2.5-Omni kept without notes. File health 5, contradictory licence and language metadata and an unanswered report about long audio.

Risk Qwen3-Omni-30B-A3B-Instruct +10

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.

Qwen3-Omni-30B-A3B-Instruct 55

File safety 25, safetensors only and no code in the repository, so the cookbook's trust_remote_code flag runs nothing. Provenance 15, files in the Qwen organisation with a checksum on every file. Safety evaluation 0 and agent guidance 0, nothing published, though spoken input can trigger tool calls. Licence risk 15, plain Apache 2.0. Security programme 0, no security contact, disclosure policy or advisories for Qwen.

Reach Ling-3.1-flash-1019 +5

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.

Qwen3-Omni-30B-A3B-Instruct 55

Memory earns 10, because the only build is the 70.5 GB BF16 checkpoint, about 85 GB with a fifth added, which fits only the reference machine's band. Runtimes earn 20. Transformers runs the whole model, and released vLLM, SGLang and llama.cpp run its Thinker with text out, while Ollama and LM Studio have nothing. Builds score 0, with no FP8, 4-bit or GGUF build from Alibaba. Apache 2.0 with nothing added gives terms the full 15 and the ungated repository gives download the full 10. Hosted too scores 0, since no provider serves this checkpoint and Alibaba's API serves a different Flash model.

Score by category

CategoryWeight this runLing-3.1-flash-1019Qwen3-Omni-30B-A3B-InstructEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256055Ling-3.1-flash-1019 +5
Risk20%204555Qwen3-Omni-30B-A3B-Instruct +10
Agent interface10%106060even
Documentation and upkeep10%105626Ling-3.1-flash-1019 +30
Negative events≤1500
TotalC 54.8/100E 41.8/100

Facts side by side

FactLing-3.1-flash-1019Qwen3-Omni-30B-A3B-Instruct
KindOpen-weight modelOpen-weight model
VendorinclusionAI (Ant Group)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-11-042025-09-22
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2/5 (4)

Verdicts

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.

Qwen3-Omni-30B-A3B-Instruct

An omni-modal cousin that listens, watches and reads, then answers in text or one of three voices, with tool calls from spoken requests, under plain Apache 2.0. Its only build, BF16, needs about 85 GB, and speech out needs Transformers or vLLM-Omni. The main risk is no answers from Qwen and no safety work for speech-driven actions.

Before you call either

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

Qwen3-Omni-30B-A3B-Instruct

  1. For text answers, mkdir -p media && vllm serve Qwen/Qwen3-Omni-30B-A3B-Instruct --dtype bfloat16 --max-model-len 32768 --allowed-local-media-path "$(pwd)/media" with vLLM 0.11.1 or later serves the Thinker on an OpenAI-compatible API
  2. The card's command passes --allowed-local-media-path /, which lets anyone who can reach the server have it read any file on the machine through a file:// URL. Point it at a dedicated folder that holds only the media you mean to send, as above, and give vLLM an absolute path
  3. Send audio as audio_url and images as image_url content parts; vLLM serve doesn't take use_audio_in_video, so pass a video's audio separately
  4. For speech out, load Qwen3OmniMoeForConditionalGeneration in Transformers 4.57.0 or later with qwen-omni-utils, pick speaker Ethan, Chelsie or Aiden, and write the returned waveform at 24 kHz
  5. Call model.disable_talker() or pass return_audio=False when you only need text, which saves about 10 GB and time
  6. Parse tool calls as JSON inside <tool_call> tags yourself, since no parser is named, and confirm actions triggered by speech before running them
  7. Keep use_audio_in_video the same across every step of a conversation, the card warns results go wrong otherwise
  8. Budget memory for video, the card's table rises from 78.85 GB for 15 seconds to 144.81 GB for 120 seconds in BF16

Questions

Which is better for AI agents, Ling-3.1-flash-1019 or Qwen3-Omni-30B-A3B-Instruct?

Ling-3.1-flash-1019 scores 54.8 (C) on agent readiness against Qwen3-Omni-30B-A3B-Instruct's 41.8 (E), and leads in 2 of 4 scored categories. Qwen3-Omni-30B-A3B-Instruct leads on risk.

Other comparisons with Ling-3.1-flash-1019 or Qwen3-Omni-30B-A3B-Instruct

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.