Qwen API pricing by model and provider

Route-specific buying guide

How to budget Qwen3.8 Max on OpenRouter

Route ID: qwen/qwen3.8-max

The accepted rows describe OpenRouter's Qwen3.8 Max route. They are not Alibaba Cloud direct-list prices and should not be presented as a family-wide cheapest Qwen claim.

OpenRouter reported a 1,000,000-token context window when checked. A large context limit does not mean every prompt should use it: longer requests increase billable input and may change latency or upstream routing behavior.

Cost formula

Estimate one request as uncached input tokens × the input rate, cached input tokens × the cached-input rate, plus output tokens × the output rate. Divide every token count by one million before applying APIDir's displayed rates.

Costs that move the bill

• Prompt size, retrieved context, conversation history, and agent scratch data
• Cache-hit rate and any separately priced cache-write operation shown by the route
• Completion length, retry policy, tool loops, and rejected or abandoned outputs
• Router behavior, account limits, region, data terms, and availability requirements

Checks before purchase

• Record the exact qwen/qwen3.8-max route ID in every benchmark and invoice sample.
• Test a representative prompt-length distribution instead of multiplying one best-case request.
• Reconcile estimated prompt, cached-prompt, and completion tokens against returned usage fields.
• Compare the router offer with a direct Qwen route only after identity, meter, limits, and terms match.

Source checked Aug 22, 2026: OpenRouter public model API. Recheck the live route before committing spend.

Estimate this route with the LLM workload calculator →

Compare another model family

• Kimi API pricing
• Grok API pricing
• Claude API pricing

Decision guide

How to compare Qwen API API providers

Qwen is a broad family covering many sizes, releases, modalities, and deployment choices. The current comparison uses Qwen3.8 2.4T A95B. APIDir stores each provider's route ID so a cheaper smaller Qwen model cannot be mistaken for the same product.

Input and output rates are only part of the decision. Context limits, caching, batching, quantization, throughput, rate limits, tool support, and hosted versus self-managed operations all affect total cost and suitability. Benchmark the exact route with representative prompts.

What changes the Qwen API API cost

• Exact Qwen release and size, context, input-output ratio, and cache behavior
• Shared serverless, dedicated, router, or self-hosted deployment channel
• Throughput, quantization, tool calls, retries, storage, and operations

Integration checks before production

• Pin the full provider model key rather than a Qwen family alias
• Validate context and output limits before submission
• Capture route, token counts, latency, retry count, and provider request ID

Workloads this comparison can inform

Multilingual application backends

Measure output quality and tokenization on your language mix beside the meter.

Large-context processing

Confirm the provider's supported context and any separate high-context rate.

Open-model deployment planning

Compare managed token pricing with realistic utilization and operations, not raw GPU price alone.

How to read the price result

Two accepted routes expose the exact reviewed Qwen model with separate input and output meters. APIDir displays both but does not publish a winner below the three-provider evidence threshold.

Related model price comparisons

• Kimi API pricing comparisonCompare Kimi API pricing across provider routes without mixing Kimi versions, token meters, context tiers, or service channels.
• GLM-5.2 pricing comparisonCompare GLM-5.2 API token prices across provider routes with exact model identity, meter, tier, source, and check date.
• GPT-OSS 120B pricing comparisonCompare source-linked GPT-OSS 120B input and output token prices across provider routes while keeping infrastructure compute meters separate.