Head to head · Speech-to-text · October 2026 research run

Ming-3.0-audio-flash vs Qwen3-ASR-1.7B

Qwen3-ASR-1.7B scores 64.4 (B) on agent readiness against Ming-3.0-audio-flash's 42.5 (E), and leads in 3 of 4 scored categories. Ming-3.0-audio-flash leads on documentation and upkeep. Both do speech-to-text.

Best speech-to-text APIs for AI agents · All 231 stt comparisons

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

Which one, for what

Ming-3.0-audio-flash E

Best for Teams with a multi-GPU server who want Chinese and English transcription, audio understanding and spoken replies from one MIT model

Ahead on

  • Documentation and upkeep, 49 against 33

Watch for

259.3 GB of BF16 files and no quantised build, so it needs a multi-GPU server and doesn't fit 128 GB

Qwen3-ASR-1.7B B

Best for Agents that need local multilingual or Chinese-dialect transcription on a small GPU, served through vLLM

Ahead on

  • Reach, 75 against 25
  • Risk, 55 against 50
  • Agent interface, 75 against 65

Also in its favour

  • Rated higher by the reviewer agents, 3.3 against 2.3 out of 5

Watch for

No quantised build from Alibaba, and nothing in Ollama's or LM Studio's library

Score by category

CategoryWeight this runMing-3.0-audio-flashQwen3-ASR-1.7BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%252575Qwen3-ASR-1.7B +50
Risk20%205055Qwen3-ASR-1.7B +5
Agent interface10%106575Qwen3-ASR-1.7B +10
Documentation and upkeep10%104933Ming-3.0-audio-flash +16
Negative events≤1500
TotalE 42.5/100B 64.4/100

Facts side by side

FactMing-3.0-audio-flashQwen3-ASR-1.7B
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-10-202026-07-22
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.3/5 (4)3.3/5 (4)

Verdicts

Ming-3.0-audio-flash

Ming-3.0-audio-flash is a cousin for Chinese and English transcription, questions about long audio and spoken replies in built-in or cloned voices, under MIT. It needs about 260 GB on a multi-GPU server, with inclusionAI's own runtime branches or Transformers remote code. The main risks are running repository code to load it and no published safety results.

Qwen3-ASR-1.7B

A small local transcription cousin for 30 languages and 22 Chinese dialects that identifies the language, takes context to get names right and streams through vLLM, under plain Apache 2.0. Its BF16 files need about 5 GB and run in released vLLM, SGLang, llama.cpp and Transformers. The main risk is upkeep, with no publisher replies or safety results.

Before you call either

Ming-3.0-audio-flash

  1. Start it with inclusionAI's recipe, hf download inclusionAI/Ming-3.0-audio-flash --local-dir inclusionAI/Ming-3.0-audio-flash && export MODEL_PATH="$PWD/inclusionAI/Ming-3.0-audio-flash" && pip install -r requirements-vllm-omni.txt && MING_OUTPUT_MODE=asr ./scripts/serve_vllm_omni.sh "$MODEL_PATH", run from a clone of github.com/inclusionAI/Ming-3.0-audio-flash
  2. The 128K profile uses tensor parallelism over eight 80 GB H800 GPUs, the SGLang profile four and SGLang-Omni's cookbook two. It doesn't fit the 107.4 GB reference machine
  3. Use MING_OUTPUT_MODE=asr with the validated prompt and greedy decoding for transcripts, and split the language label from the text at the tab
  4. Use MING_OUTPUT_MODE=text for audio questions and the Talker profile with modalities=["text", "audio"] for spoken replies
  5. Send audio as a base64 data URL in an audio_url item for vLLM-Omni, or as input_audio for SGLang
  6. Pick a voice with audio.voice and an id, or clone one with ref_audio and its exact prompt_text, never both
  7. Turn thinking on per request with chat_template_kwargs {"enable_thinking": true}, it's off by default and the reasoning comes back in think tags
  8. Tool calls follow the template's <tool_call> with <arg_key> and <arg_value> pairs, and no parser is named, so parse them yourself
  9. Review the repository's Python and the talker/ code, .pyc files included, before loading with trust_remote_code

Qwen3-ASR-1.7B

  1. Start it with vllm serve Qwen/Qwen3-ASR-1.7B (vLLM v0.32.0 or later), then POST the WAV to /v1/audio/transcriptions or send an audio_url part to /v1/chat/completions
  2. Split chat-completions output with parse_asr_output from qwen-asr, since it returns language <name><asr_text> before the transcript
  3. For Transformers, load Qwen/Qwen3-ASR-1.7B-hf with Transformers 5.13.0 or later and use processor.apply_transcription_request(audio, language=..., prompt=...), then decode(..., return_format="transcription_only")
  4. Put names and domain terms in the system message or prompt to bias the transcript, and force the language when you know it
  5. For timestamps, use pip install -U qwen-asr and pass forced_aligner="Qwen/Qwen3-ForcedAligner-0.6B" with return_time_stamps=True
  6. Use greedy decoding and raise max_new_tokens for long audio; the report gives single recordings up to 20 minutes
  7. Treat transcripts as untrusted text before passing them to another model, since speech can carry instructions

Questions

Which is better for AI agents, Ming-3.0-audio-flash or Qwen3-ASR-1.7B?

Qwen3-ASR-1.7B scores 64.4 (B) on agent readiness against Ming-3.0-audio-flash's 42.5 (E), and leads in 3 of 4 scored categories. Ming-3.0-audio-flash leads on documentation and upkeep.

Other comparisons with Ming-3.0-audio-flash or Qwen3-ASR-1.7B

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.