Alibaba Qwen pricing
Qwen3.7 Max pricing
Qwen3.7 Max bills per million tokens, metered separately for input and output. The current rates are below, along with the parts of the bill a per-token estimate leaves out.
Qwen3.7 Max rates in full
All figures are USD per million tokens, taken from Alibaba Qwen’s own pricing documentation. The API model identifier is qwen3.7-max.
| Per million tokens | Standard, ≤1M tokens |
|---|---|
| Input | $2.50 |
| Output | $7.50 |
Context window: 1M tokens.
What the rate table does not tell you
The prior generation of Qwen's flagship line, superseded by Qwen3.8 Max at a 20% lower headline rate.
Billed under the same context-caching and batch-discount rules as Qwen3.8 Max.
A worked monthly example
Take 500,000 calls in a month at 3,000 input tokens and 400 output tokens each. That is 1.5 billion input tokens against 200 million output tokens, so input is 88% of the token volume.
| Line | Tokens | Rate | Cost |
|---|---|---|---|
| Input | 1,500M | $2.50 | $3,750 |
| Output | 200M | $7.50 | $1,500 |
| Total | 1,700M | $5,250 |
Output is 12% of the tokens and 29% of the bill. That inversion is why prompt trimming so often fails to move the invoice, and it is the single most common reason a forecast built on Qwen3.7 Max comes in under the real number.
How this page stays current
The rate on this page was read off Alibaba Qwen’s published pricing and recorded with the date it was checked, September 16, 2026. The date changes only when someone checks again, not on each deploy. This model is not matched to the live model catalog, so the rate rests on the publisher documentation check alone.
Frequently asked questions
How much does the Qwen3.7 Max API cost?
Qwen3.7 Max is billed per million tokens, metered separately for input and output. As of September 16, 2026 the rate is $2.50 per million input tokens and $7.50 per million output tokens.
Why is my Qwen3.7 Max bill higher than the per-token estimate?
Most estimates multiply expected tokens by the input rate and stop there. Output is priced at $7.50 against $2.50 for input, so responses usually dominate the bill even when prompts look larger. Reasoning tokens bill as output. Retries and agent fan-out pay full input cost for calls that produced nothing. And a cache that gets written but never read is pure overhead rather than a saving.
What is the cheapest way to run Qwen3.7 Max?
The larger lever is usually routing: sending the requests that do not need this tier to a cheaper model, and capping spend per customer before the call goes out.
How do I track Qwen3.7 Max spend per customer or per feature?
Provider reports group usage by model, project or API key. Your application supplies the customer and workflow context needed to see cost per account. That means passing the customer, team or agent with each request from your server and recording the resolved cost against it. Spendline does this for supported requests routed through it, and checks configured budgets before forwarding them. Actual response cost can differ from the pre-call estimate.
See cost per customer, not just per token
A rate card tells you what a token costs. It does not tell you which customer, team or agent spent it. Spendline records attributed cost for supported requests routed through it and checks configured budgets before forwarding them.
Book a 30-minute call Explore a sample account