Deployment scope
The US scope lists the same rates as International. The Global scope (Frankfurt, Virginia, Tokyo, Hong Kong) and the Chinese mainland scope publish lower rates, so a Beijing or Global endpoint can cost less than these rows show.
Alibaba Qwen rows use official Model Studio list prices for the International (Singapore) deployment scope. Some models price by input tokens per request, implicit cache hits map to cached input, and Global or Chinese mainland scopes publish different rates.
Choose a current Alibaba Qwen model from the same pricing rows, enter input tokens, output tokens, and request volume, then review the estimated monthly API cost.
Start with realistic input tokens, output tokens, model choice, request volume, and any implicit cache-hit and long-context tier pricing rules that apply. Then compare the estimate against current model pricing and budget limits before launch.
These rows use Alibaba Cloud Model Studio list prices for the International (Singapore) deployment scope. Check the scope your account and endpoint use before comparing totals.
The US scope lists the same rates as International. The Global scope (Frankfurt, Virginia, Tokyo, Hong Kong) and the Chinese mainland scope publish lower rates, so a Beijing or Global endpoint can cost less than these rows show.
Qwen3.7 Plus and Qwen Flash price by the input tokens in each request: up to 256K, or 256K to 1M. The tier applies to every token in that request. Qwen3.8 Max and Qwen3.8 Flash use one rate up to 1M.
Cached input is the implicit, automatic cache-hit rate. Explicit caching is a separate opt-in mode with its own creation and read prices, listed in each row's billing note. Rows show list prices; limited-time discounts, such as the current Qwen3.7 Plus offer, are noted but not applied.
Open a model page for its verified source, workload examples, price history, lifecycle details, and nearby alternatives.
Null or unverified values are displayed as Not listed, never as zero.
All prices in USD per 1M tokens.
| Model | Input | Output | Cached Input | Verified |
|---|---|---|---|---|
Qwen FlashlatestModel ID: qwen-flashDetailsProvider: Alibaba QwenPrice shown: Standard · Short context · ≤256k input tokens · whole request | Input · USD per 1M input tokens$0.05 | Output · USD per 1M output tokens$0.40 | Cached input · USD per 1M cached input tokens$0.01 | Evidence |
Qwen3.7 PluslatestModel ID: qwen3.7-plusDetailsProvider: Alibaba QwenPrice shown: Standard · Short context · ≤256k input tokens · whole request | Input · USD per 1M input tokens$0.40 | Output · USD per 1M output tokens$1.60 | Cached input · USD per 1M cached input tokens$0.08 | Evidence |
Qwen3.8 FlashlatestModel ID: qwen3.8-flashDetailsProvider: Alibaba QwenPrice shown: Standard | Input · USD per 1M input tokens$0.15 | Output · USD per 1M output tokens$0.47 | Cached input · USD per 1M cached input tokens$0.016 | Evidence |
Qwen3.8 MaxlatestModel ID: qwen3.8-maxDetailsProvider: Alibaba QwenPrice shown: Standard | Input · USD per 1M input tokens$2.00 | Output · USD per 1M output tokens$6.00 | Cached input · USD per 1M cached input tokens$0.25 | Evidence |
Use these Alibaba Qwen pricing rows as planning inputs: calculate your monthly API cost with realistic token counts, or compare this provider with other AI models before routing production traffic.
Some Alibaba Qwen models charge a different rate once a request passes a context threshold. The tables below list each model's published tiers.
When a tier's threshold condition matches, that tier prices the entire standard request. This is a tier switch, not progressive pricing across token bands.
The 272K pricing threshold is based on input tokens. Cached tokens are included within the API's input token count.
Prices in USD per 1M tokens.
| Context tier | Input token rule | Regular input | Cached input | Output | Unit |
|---|---|---|---|---|---|
| Short contextshort | ≤256k input tokens | $0.05 | $0.01 | $0.40 | USD / 1M tokens |
| Long contextlong | >256k input tokens | $0.25 | $0.05 | $2.00 | USD / 1M tokens |
Qwen Flash
Model ID: qwen-flash
Provider: Alibaba Qwen
Prices in USD per 1M tokens.
| Context tier | Input token rule | Regular input | Cached input | Output | Unit |
|---|---|---|---|---|---|
| Short contextshort | ≤256k input tokens | $0.40 | $0.08 | $1.60 | USD / 1M tokens |
| Long contextlong | >256k input tokens | $1.20 | $0.24 | $4.80 | USD / 1M tokens |
Qwen3.7 Plus
Model ID: qwen3.7-plus
Provider: Alibaba Qwen
Alibaba Qwen API pricing is the usage-based cost of running Qwen models through API requests. The practical estimate depends on the selected model, input tokens, output tokens, monthly request volume, retries, and any listed caching or discount rules.
Estimate one representative request first: input tokens, expected output tokens, selected Qwen models, request volume, retry rate, and implicit cache-hit and long-context tier pricing assumptions when they are listed. Then multiply by monthly traffic.
Open the Alibaba Qwen API cost calculatorUse the table on this page to compare available Alibaba Qwen rows per 1M tokens. Not listed values stay visible as Not listed, so unknown prices are not accidentally treated as zero.
Compare total workflow cost, not only the cheapest input token price. Output length, quality, retries, context size, and fallback routing can change the real monthly API bill.
Compare Alibaba Qwen with other providersUse cases are planning categories, not pricing promises. Estimate each workflow with its own token shape, expected answer length, quality requirement, and fallback behavior.
Qwen3.8 Flash and Qwen Flash are often evaluated for extraction, classification, summarization, and agent sub-steps where per-token cost dominates.
Qwen3.7 Plus and Qwen Flash switch to a higher rate for every token once a request exceeds 256K input tokens, so size prompts before routing long documents to them.
Qwen3.8 Max is the flagship option for complex reasoning and coding; compare its flat 1M-context rate against frontier models with long-context surcharges.
Compare Alibaba Qwen with DeepSeek, Kimi, Gemini, and OpenAI by input price, output price, cached-input behavior, context needs, latency, quality, and cost per successful task. Always verify current provider pricing before launch or procurement decisions.
Model a normal, high, and worst-case month with expected requests, input tokens, output tokens, retries, and model routes before exposing a feature to real traffic.
Decide which app, workspace, customer tier, or internal team can spend against the provider budget. Review burn rate weekly during launches and pricing changes.
Shorten repeated instructions, cap output length, avoid sending full history when a summary works, and route routine tasks to lower-cost models when quality testing supports it.
The existing calculator route is linked directly without invented provider or model query parameters.
Pricing data is informational and may lag provider changes. Always verify final billing decisions against provider pricing pages, contracts, dashboards, and invoices.
Alibaba Qwen rows use official Model Studio list prices for the International (Singapore) deployment scope. Some models price by input tokens per request, implicit cache hits map to cached input, and Global or Chinese mainland scopes publish different rates.
Alibaba Qwen API cost depends on the selected model, input tokens, output tokens, request volume, retries, and any implicit cache-hit and long-context tier pricing or discount rules that apply. Use the pricing table and calculator with your own workload assumptions instead of relying on a single average price.
Estimate one request with input tokens, expected output tokens, model choice, and current per-1M-token pricing. Then multiply by requests per user, active users, days per month, retry rate, and fallback calls.
Qwen models are usually evaluated for workflows such as high-volume, low-cost routes, long-context workloads, flagship reasoning and coding. The best route depends on quality, latency, context size, output length, and monthly budget.
Alibaba Qwen can be cheaper or more expensive depending on the exact model, prompt size, output length, cache eligibility, retry rate, and quality target. Compare total workflow cost across providers before switching production traffic.
Not listed means the current local pricing source does not expose a confirmed numeric value for that field. It is intentionally not treated as zero. Check the official Alibaba Qwen pricing page and billing dashboard before launch.
Control spend by setting monthly budget limits, measuring input and output tokens separately, capping output length, reducing repeated context, reviewing retry cost, and comparing model routes before high-volume traffic grows.