News · 2026-08-03

Qwen3.8-Max Shipped as a Paid API, Not as Open Weights

Alibaba put Qwen3.8-Max live as a hosted API priced at $2 per million input tokens and $6 per million output tokens, a fifth below the $2.50 and $7.50 it charges for the previous qwen3.7-max. The open weights Alibaba has promised for both Qwen3.8-Max and a smaller Qwen3.8-27B did not ship with it. No checkpoint, license, or model card for either model is published anywhere today.

Key facts

• Qwen3.8-Max costs $2 per million input tokens and $6 per million output tokens, with implicitly cached input at $0.25 per million.
• It went live on QwenCloud on 3 August 2026, described by Alibaba as a "2.4T-parameter MoE" that takes text, images, and video and returns text.
• Total context is one million tokens, with up to 131,000 output tokens and up to 262,000 reasoning tokens.
• Primary source: the QwenCloud model page and the published price list.

The distinction between a hosted model and a downloadable one is the whole story here, and it got lost within hours. Alibaba's announcement post named both models and said open weights are coming "next week." What actually exists this evening is an API key.

That API is a serious product. Alibaba's Model Studio catalog exposes qwen3.8-max from endpoints in China, Singapore, Tokyo, Frankfurt, and US Virginia. It supports function calling, structured output, prompt caching, and built-in web and code tools, and it lets callers dial reasoning effort up or down. In multi-turn use it requires the caller to hand back the model's prior reasoning stream intact, which is a design decision worth noticing: the vendor is holding the conversational state format, not just the weights. Alibaba is selling distribution and integration here, not a file.

The price cut is the concrete news, and it is bigger than it looks for a specific kind of workload. An agent that re-reads the same codebase on every turn pays mostly for input tokens, and cached input at $0.25 per million is eight times cheaper than fresh input. If you have built anything that repeatedly ships the same large context, that line matters more than the headline rate. Our explainer on prompt caching covers why.

The catch is that price per million tokens is not price per finished job. A reasoning model with a 262,000-token internal budget can spend an enormous number of output-priced tokens on a single agentic task, and Alibaba has published no task-level cost or token-efficiency measurement. Cheaper tokens and cheaper work are different claims, and only the first one is verified.

How it works

A mixture-of-experts model like this one holds a very large bank of parameters but activates only a small slice of them for any given token. Think of a hospital with two thousand specialists on staff where each patient sees three of them: the payroll is enormous, the consultation is fast. Alibaba discloses the total, 2.4 trillion parameters, but not how many are active per token, how many experts there are, or how routing works. There is no technical report. Every architectural claim about Qwen3.8-Max is currently the vendor's own line on a product page.

The 17 GB claim

The most-shared number attached to today had nothing to do with the model that shipped. A thread on r/unsloth carried the claim that the unreleased 27B will run in about 17 GB of VRAM. A rebuttal on r/LocalLLaMA made the correction that matters: 17 GB is approximately the disk footprint of a 4-bit 27B checkpoint, and a footprint is not a deployment. Context length drives the key-value cache, which grows on top of the weights; the runtime needs a workspace; the display needs memory. On a 16 GB card there is no headroom at all. See our lesson on quantization for what a 4-bit conversion actually trades away.

The comparison to Kimi K3 and DeepSeek V4 Flash also has a narrower basis than the aggregators suggest. Arena placed Qwen3.8-Max fourth on its Frontend Code Arena and grouped it with those two on a price-and-performance frontier. That is a preference result on front-end code. It is not the Artificial Analysis Intelligence Index, which several summaries confused it with, and it says nothing about long-horizon agents, vision, or reliability.

Why it matters

Open weights and cheap API access solve different problems, and treating them as the same thing produces exactly the confusion this release generated. Alibaba made a large multimodal cloud model measurably cheaper today, especially for cache-heavy agent workloads. It did not put a new model on anyone's desk. Next week's checkpoint, if it lands, is the test of the other half of the story. Compare with Alibaba's last actual weight release, where the file arrived alongside the announcement.

The honest caveat: everything above about the model's internals comes from a product page. Until there is a technical report or a checkpoint, the architecture, the training recipe, and the capability claims are all Alibaba describing its own work.

Primary source, verified: read the paper →

Ground Truth. (2026, August 3). Qwen3.8-Max Shipped as a Paid API, Not as Open Weights. Ground Truth. https://groundtruth.day/news/qwen3-8-max-ships-as-a-paid-api-not-open-weights.html

@misc{groundtruth:qwen3-8-max-ships-as-a-paid-api-not-open-weights,
  title  = {Qwen3.8-Max Shipped as a Paid API, Not as Open Weights},
  author = {{Ground Truth}},
  year   = {2026},
  month  = {aug},
  url    = {https://groundtruth.day/news/qwen3-8-max-ships-as-a-paid-api-not-open-weights.html}
}

Topics: qwen · alibaba · model-release · pricing · open-weights · local-llm · api