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

Ming-3.0-asr-tiny vs Qwen3-ASR-0.6B

Qwen3-ASR-0.6B scores 61.2 (C) on agent readiness against Ming-3.0-asr-tiny's 52.5 (D), and leads in 2 of 4 scored categories. Ming-3.0-asr-tiny leads on documentation and upkeep. Both do speech-to-text.

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

Which one, for what

Ming-3.0-asr-tiny D

Best for Agents with a CUDA GPU that need local Chinese, English or dialect transcription where names and domain terms matter

Ahead on

  • Documentation and upkeep, 46 against 33

Watch for

Loading runs the publisher's Python with trust_remote_code, and the reference path needs a CUDA GPU

Qwen3-ASR-0.6B C

Best for Agents that need fast, cheap local transcription in many languages on a small GPU, including realtime streaming

Ahead on

  • Reach, 75 against 50
  • Agent interface, 75 against 60

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-asr-tinyQwen3-ASR-0.6BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255075Qwen3-ASR-0.6B +25
Risk20%205555even
Agent interface10%106075Qwen3-ASR-0.6B +15
Documentation and upkeep10%104633Ming-3.0-asr-tiny +13
Negative events≤1500
TotalD 52.5/100C 61.2/100

Facts side by side

FactMing-3.0-asr-tinyQwen3-ASR-0.6B
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 reviews3/5 (4)3/5 (4)

Verdicts

Ming-3.0-asr-tiny

A local transcription cousin for Chinese, English and Chinese dialects that takes hotwords or dialogue context to get names right, under MIT. It needs one CUDA GPU with about 21 GB and runs only through the publisher's remote code or SGLang-Omni's main branch. The main risk is running the publisher's Python on load, with no safety results.

Qwen3-ASR-0.6B

A very small local transcription cousin for 30 languages and 22 Chinese dialects, built for throughput and realtime streaming through vLLM, under plain Apache 2.0. Its BF16 files need about 2 GB and run in released vLLM, SGLang, llama.cpp and Transformers. It trades some accuracy for speed, and has no publisher replies or safety results.

Before you call either

Ming-3.0-asr-tiny

  1. Start it with hf download inclusionAI/Ming-3.0-asr-tiny --local-dir Ming-3.0-asr-tiny, then pip install -r requirements.txt in Python 3.12 with CUDA (Transformers 5.12.1, fla-core 0.5.2, PyTorch 2.11.0), then python examples/transcribe.py --model . --audio speech.wav --language-hint en
  2. To serve it, sgl-omni serve --model-path inclusionAI/Ming-3.0-asr-tiny from SGLang-Omni's main branch, then POST the WAV to /v1/audio/transcriptions with response_format json and read the text field
  3. Parse raw Transformers output with decode_transcript from asr_request.py, which strips the language label before the tab
  4. Pass language zh or en when known, anything else is rejected, and append a topic or hotwords to the base instruction with no newline
  5. Load with dtype torch.bfloat16 rather than casting the model, use greedy decoding, max_new_tokens 256 and no_repeat_ngram_size 10, and don't apply the chat template
  6. Split long recordings yourself or use --audio-chunk-frames, since input and output share 8,192 tokens
  7. Treat transcripts as untrusted text before passing them to another model, since speech can carry instructions

Qwen3-ASR-0.6B

  1. Start it with vllm serve Qwen/Qwen3-ASR-0.6B (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. For vLLM's realtime streaming, start it with --hf-overrides '{"architectures":["Qwen3ASRRealtimeGeneration"]}', which vLLM doesn't pick from config.json
  3. Split chat-completions output with parse_asr_output from qwen-asr, since it returns language <name><asr_text> before the transcript
  4. For Transformers, load Qwen/Qwen3-ASR-0.6B-hf with Transformers 5.13.0 or later and use processor.apply_transcription_request(audio, language=..., prompt=...)
  5. Put names and domain terms in the system message or prompt to bias the transcript, and force the language when you know it
  6. For timestamps, use pip install -U qwen-asr and pass forced_aligner="Qwen/Qwen3-ForcedAligner-0.6B" with return_time_stamps=True
  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-asr-tiny or Qwen3-ASR-0.6B?

Qwen3-ASR-0.6B scores 61.2 (C) on agent readiness against Ming-3.0-asr-tiny's 52.5 (D), and leads in 2 of 4 scored categories. Ming-3.0-asr-tiny leads on documentation and upkeep.

Other comparisons with Ming-3.0-asr-tiny or Qwen3-ASR-0.6B

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.