Qwen3.8-Max-0902 API: Release, Price, and Limits

Qwen’s September 2 post says the updated model is live, but Alibaba’s API docs still label it qwen3.8-max. That naming gap matters for budgeting, model pinning, and production migration.

Qwen3.8-Max-0902 should be treated as a live API revision, not a separately documented SKU

Qwen3.8-Max-0902 has an official release signal, but its dated suffix is not yet reflected consistently in the public API contract. Treat it as a revision or snapshot of qwen3.8-max until the provider catalog or a dedicated model page exposes qwen3.8-max-0902 as a separate identifier.

What the official announcement confirms

The official Qwen announcement on X says Qwen3.8-Max was upgraded to Qwen3.8-Max-0902, received further post-training for coding and “cowork,” and was live through the QwenCloud API on September 2, 2026. The post also repeats the family’s 2.4-trillion-parameter and 1-million-token context positioning.

The announcement confirms a live revision, not a separate public SKU, billing row, or 0902 benchmark suite.

What Alibaba’s public docs still call it

The Alibaba Cloud Model Studio page was updated September 2, 2026, but its model name remains qwen3.8-max. The page documents regional capabilities, prices, rate limits, and context fields for that model name; it does not provide a separate qwen3.8-max-0902 row.

Use the exact ID returned by the live provider catalog. Do not assume that appending -0902 to an existing request will work, and do not treat the announcement label as proof that 0902 has independent pricing.

What changed from the original Qwen3.8-Max release

Qwen3.8-Max-0902 is a coding-and-cowork post-training update; no matched 0902 benchmark, latency, reliability, or token-efficiency results are published. The change is therefore best evaluated through task behavior and API telemetry rather than a new parameter-count claim.

The documented model envelope remains broad

The public qwen3.8-max documentation describes a multimodal, text-output model with a 2.4-trillion-parameter MoE architecture and a 1,000,000-token context window. It supports function calling, structured outputs, partial mode, and context caching across the listed regions; fine-tuning is unsupported in every listed region.

These are family-level specifications, not a complete technical description of the 0902 post-training update.

Qwen3.8-Max-0902 API pricing depends on region

There is no single universal Qwen3.8-Max-0902 price in the public documentation. Alibaba lists prices for the broader qwen3.8-max model by deployment region, with Singapore priced higher than the other listed regions and with feature differences that can matter more than the headline token rate.

Regional price and feature matrix

The official Model Studio pricing tables list the following original API rates, excluding limited-time promotions:

Singapore is $2/$6 per million input/output tokens; the other listed regions are $1.65/$4.951. Budget from the endpoint you will use.

Beijing is the only listed region with batch inference. Beijing and Singapore support web search; Frankfurt, Virginia, Tokyo, and Hong Kong do not. Every listed region supports the core multimodal, function-calling, structured-output, partial-mode, and context-cache features.

What caching changes in a real bill

For a token-only workload with 10 million fresh input tokens and 2 million output tokens, the listed prices produce materially different totals:

The cached figures assume 9 million cached input tokens, 1 million fresh input tokens, and 2 million output tokens. For the Virginia row, the calculation is 9M × $0.206 + 1M × $1.65 + 2M × $4.951 = $13.41.

Include tools, retries, reasoning output, and verification when estimating an agent run; compare accepted-result cost, not one-response cost.

The 1M-token headline has three practical limits

Qwen3.8-Max’s 1-million-token context is a ceiling composed of separate input, output, and thinking limits. A request cannot automatically use the maximum value of every field at once, and Alibaba says supported lengths can vary with the combination of API parameters.

Standard, thinking, and output limits

The 991,808-token input limit is not the same as “send one million input tokens and receive 131,072 output tokens.” Validate the exact request shape against the current API documentation and your chosen endpoint before designing around the upper bound.

Long context is a ceiling, not a performance promise

Independent tracking of the broader Qwen3.8 Max listing shows why context size should not be confused with responsiveness. Artificial Analysis reports an Intelligence Index score of 58, ranked 18th in a 192-model comparison class, but it also reports 40.6 output tokens per second and a rank of 139th for output speed. Its page describes the model as notably slow and very verbose.

These broader-model results are planning signals, not 0902 proof; benchmark 32K, 128K, and 262K contexts for latency, output, and cost before relying on million-token requests.

0902 is still API-first, even with open Qwen3.8 weights

The hosted Qwen3.8-Max service and the open Qwen3.8 checkpoints are related but not interchangeable. Open weights give you control over the model files and serving stack; they do not automatically reproduce QwenCloud’s regional tools, vision interface, context defaults, or 0902 revision.

Hosted 0902 versus the open checkpoint

The official Qwen3.8 GitHub repository records the open Qwen3.8-2.4T-A95B release on August 12, 2026 and the Qwen3.8-27B release on August 14, 2026. Those entries confirm that the Qwen3.8 family has open releases; they do not identify either checkpoint as Qwen3.8-Max-0902.

What local deployment actually implies

Do not infer single-GPU feasibility from the 95B active-parameter figure. The Qwen3.8-Max deployment analysis notes that complete model storage, KV-cache memory, routing, and serving configuration still determine infrastructure requirements.

In the r/LocalLLaMA release thread, user u/ResearchCrafty1804 wrote:

“At 2.4T parameters I wouldn’t call it exactly at home, since the hardware requirements to self-host it are significant.”

That is one user’s deployment concern, not an official hardware specification. Open-checkpoint availability also does not establish that the hosted 0902 revision is downloadable.

Coding and agent claims: what to verify before switching

Qwen positions Qwen3.8-Max around long-horizon coding, professional work, research, and multimodal task execution. The useful adoption question is narrower: does the 0902 revision complete your fixed tasks with fewer repairs, lower accepted-result cost, or better tool reliability than the model you already use?

What the first-party evidence establishes

Alibaba’s launch announcement describes Qwen3.8-Max as a 2.4-trillion-parameter model with 95 billion activated parameters, a 1-million-token context window, and claimed placements of fifth in Text Arena, second in Vision Arena, and fourth in Frontend Code Arena. It also describes an internal 16-day autonomous coding project.

The announcement lacks a matched before-and-after evaluation, so treat the 16-day run as a vendor demonstration rather than a standardized guarantee of autonomous production work.

How to use Qwen3.8-Max-0902 without breaking an existing integration

A cautious migration requires separating the announcement label from the API identifier and testing the endpoint you will actually pay for.

Evaluate and migrate safely

1. Pin the endpoint and region. Record whether the run uses Beijing, Singapore, Virginia, Frankfurt, Tokyo, or Hong Kong because prices, web search, batch access, and limits differ.
2. Record the exact model ID returned by the provider. Store response metadata instead of hard-coding qwen3.8-max-0902 from the announcement.
3. Fix reasoning and tool settings. Keep the prompt, tool schemas, permissions, timeout, retry policy, and reasoning effort unchanged across models.
4. Run a small fixed task set. Use repository repair, multi-file edits with tests, structured extraction, and one long-document task.
5. Validate the request shape. Check the selected endpoint’s context, output, modality, structured-output, and function-calling behavior rather than assuming family-level support.
6. Measure the full run. Capture first-pass success, tool failures, retries, input tokens, cached input, output tokens, wall-clock time, and operator intervention.
7. Compare accepted-result cost. Include failed attempts and verification work; nominal token prices alone are insufficient.
8. Measure cache behavior and keep a fallback. Use a stable prefix to test actual cache hits, then retain the previous model until the revision’s identifier and behavior are stable in your logs.

The Qwen Code weekly update says qwen3.8-max moved from preview to stable for Token Plan users and retained three thinking levels: low, medium, and extra high. That client update does not by itself prove that a dated -0902 alias is accepted by every API-compatible provider.

Qwen3.8-Max-0902 FAQ

Is Qwen3.8-Max-0902 officially released?

Yes, the official Qwen announcement says the upgraded revision is live through the QwenCloud API on September 2, 2026. Public Alibaba documentation still presents the model as qwen3.8-max, not as a separately documented qwen3.8-max-0902 SKU.

What API model ID should I use?

Use the exact identifier returned by the provider’s current model catalog. Alibaba’s public documentation uses qwen3.8-max; do not guess that qwen3.8-max-0902 is accepted everywhere.

How much does Qwen3.8-Max-0902 cost?

Public prices are listed for qwen3.8-max by region: $1.65 input and $4.951 output per million tokens in most listed regions, or $2 input and $6 output in Singapore. Implicit-cache input is listed at $0.206 in the lower-priced regions and $0.25 in Singapore.

Does Qwen3.8-Max-0902 have a 1M context window?

The public family documentation lists a nominal 1,000,000-token context window, with maximum input of 991,808 tokens in standard mode, 983,616 in thinking mode, and maximum output of 131,072 tokens. Actual support can depend on the request parameters.

Is Qwen3.8-Max-0902 open source?

The 0902 hosted revision is documented as an API update, not as a separately released open checkpoint. Qwen3.8 has open checkpoints, including Qwen3.8-2.4T-A95B, but the official repository does not identify that checkpoint as the 0902 revision.

What changed in the 0902 update?

The official announcement says the model received further post-training for coding and cowork. No matched public 0902 evaluation currently establishes a measured improvement over the earlier release.