Qwen3.8 LiveTranslate API Pricing and WebSocket Setup

A live translator that answers in about 2.3 seconds sounds ready for a meeting room. Qwen3.8-LiveTranslate is available now, but only as a hosted Alibaba Cloud/Model Studio API; the 2.3-second figure is an official claim, not an independent production measurement. That distinction changes how I would budget and deploy it.

The 30-second buying decision

Use Qwen3.8-LiveTranslate for a guarded prototype if you need streaming speech translation, captions, and audio output through a realtime connection. Do not treat the headline latency as a guarantee for noisy meetings, overlapping speakers, or every language pair: independent hands-on evidence for this exact release is still thin.

The model is a reasonable fit for a backend service that can keep an API key private and tolerate a region-specific Alibaba Cloud setup. It is a poor fit if you need downloadable weights, a mature third-party hosting footprint, or a proven accuracy benchmark before writing production requirements.

What is actually available

The exact hosted model ID is qwen3.8-livetranslate-flash-realtime. Alibaba Cloud’s official documentation and Model Studio changelog list it as a realtime service released on September 17, 2026. The official model page describes 60 recognized source languages and 29 spoken-output languages.

The release is therefore more concrete than a product teaser, but it is not the same thing as an open model download. The official documentation presents inference access through Model Studio rather than local checkpoints.

Cost before code

For the international/Singapore deployment, the official rate card separates four billable categories. The listed prices are per one million tokens:

Qwen’s realtime translation guide says audio input is counted at 7 tokens per second and audio output at 12.5 tokens per second. That lets you estimate the input side for a continuous stream:

• 60 seconds of audio input: 420 tokens, or about $0.00315 at the listed audio-input rate.
• 60 seconds of generated audio output: 750 tokens, or about $0.0225 at the listed audio-output rate.

Those figures are not a complete “cost per minute.” They exclude text output, images, connection behavior, and the possibility that translated audio lasts longer or shorter than the source. Requesting text only also changes the output meter. Use the official model pricing page for the region and deployment you will actually use.

The WebSocket path that matters

The documented integration is a server-side realtime session, not a normal one-shot translation request. The official Realtime API overview identifies WebSocket as the straightforward option for server applications and prototypes.

A minimal implementation has this shape:

1. Create a region-specific realtime WebSocket URL with qwen3.8-livetranslate-flash-realtime as the model.
2. Send Authorization: Bearer <API_KEY> during the handshake; keep the key on your backend.
3. Send session.update with the source/target language and requested output modalities.
4. Stream base64 audio with input_audio_buffer.append.
5. Commit the buffer or let the configured voice-activity detection trigger processing.
6. Consume translated text and audio events until the turn is complete.

The endpoint is workspace- and region-dependent, so copying a hostname from another deployment can fail even when the event payload is correct. The LiveTranslate client-event reference is the source to check when implementing session configuration, VAD, hotwords, or manual commits.

Where it earns its keep—and where it does not

A useful ecosystem signal is the open-source AlbusWei/LiveTranslate implementation. Its README describes solo translation, file dubbing, and meeting modes, with WebRTC-first transport and WebSocket fallback. That proves developers can build a practical wrapper around Qwen realtime models; it does not prove Qwen3.8’s accuracy or production uptime.

What the evidence can—and cannot—say yet

The official documentation gives a concrete feature and price surface, but independent testing is still the weak point. Community discussion found only a small number of posts about this exact release and no substantive Reddit thread dedicated to Qwen3.8-LiveTranslate.

One real-user post summarized the headline change cautiously:

“2.3 秒还没有消失，但已经更接近人类能自然接话的节奏了。” — @WukongNumber1, X

That is useful as a human reaction to the latency claim, not as a benchmark. A separate Reddit discussion about earlier Qwen translation use was also mixed: u/ReplacementTommy wrote, “Honestly, Qwen AI has been the most accurate and natural-sounding for translations I've used,” while u/Valhall22 reported that Qwen was not in their top five in English, German, and French tests. Those comments do not identify the exact Qwen3.8 realtime model or a controlled test, so they should not be turned into a ranking.

The practical conclusion is narrower: Qwen3.8-LiveTranslate is officially callable, its billing is documented, and its realtime architecture is actionable. Accuracy under difficult speech conditions remains a validation task for the buyer.

Qwen3.8 LiveTranslate API FAQ

Is Qwen3.8 LiveTranslate available now?

Yes. Alibaba Cloud documentation lists qwen3.8-livetranslate-flash-realtime as a hosted Model Studio API model. The evidence does not show an open-weight release.

Does Qwen3.8 LiveTranslate use WebSocket?

Yes. The official Realtime API and LiveTranslate event references document WebSocket access, authentication, session updates, audio-buffer events, and streamed output.

How much does Qwen3.8 LiveTranslate cost per minute?

There is no single universal per-minute price because audio input, text output, audio output, and image context use separate meters. Using the documented 7 input tokens per second and 12.5 output tokens per second, one minute of audio input is about $0.00315 and one minute of generated audio is about $0.0225 at the listed international rates, before text and other usage.

Can it return text without translated audio?

Yes. The session can configure output modalities, including text or text plus audio. Confirm the current event names in the official client-event documentation before shipping.

How many languages does it support?

The official model information lists 60 recognized languages and 29 spoken-output languages. The audio-output count is therefore smaller than the recognition count.

Can it translate video in real time?

The model accepts audio and image context and is positioned for audiovisual translation. That does not mean every file-based video dubbing workflow uses this realtime model; Qwen documents separate non-realtime audio/video translation paths.

Can I download the model and run it locally?

No official open-weight release was found for this exact realtime model. Plan around hosted inference unless Qwen publishes a separate checkpoint and license.

The practical call: prototype behind a switch

Qwen3.8-LiveTranslate is worth a controlled API prototype, not a blind production commitment. Before rollout, test three things with your own audio: measured time to first translated output, language-pair quality with names and domain terms, and behavior during silence, interruptions, and reconnects.

Keep the model behind a configuration switch so you can change region, transport, or provider without rewriting the application. That is the sensible trade-off today: the API surface and pricing are real enough to build against, while the hardest production questions—noisy-room accuracy and sustained reliability—still belong to your test plan rather than the launch announcement.

Sources checked

• Alibaba Cloud model information
• QwenCloud realtime translation guide
• QwenCloud client events
• QwenCloud realtime API overview