Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Alibaba Cloud / Qwen3.7

Qwen3.7-Flash · July 2026

Pinned July release of Qwen3.7-Flash with its own regional capability and rate tables.

availableClosed weightsText generationCodingVisionAgents
Official documentation (opens in a new tab)Reviewed 14 Oct 2026
19 of 23 specification fields collected
Input token limit991.8K991,808 tokens
Maximum output131.1K131,072 tokens
Input / 1M tokens$0.03Alibaba Model Studio · Singapore · International
Output / 1M tokens$0.13USD · observed 14 Oct 2026

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
1,000,000 tokensSource for Context / input limit (opens in a new tab)
Input modalities
Text, Image, VideoSource for Input modalities (opens in a new tab)
Tool calling
SupportedSource for Tool calling (opens in a new tab)

At least one reviewed endpoint supports this feature when true.

Structured output
SupportedSource for Structured output (opens in a new tab)

At least one reviewed endpoint supports this feature when true.

Batch processing
Not supportedSource for Batch processing (opens in a new tab)

At least one reviewed endpoint supports this feature when true.

Fine-tuning
Not supportedSource for Fine-tuning (opens in a new tab)

At least one reviewed endpoint supports this feature when true.

Knowledge cutoff
Not collected
Release date
2026-07-21Source for Release date (opens in a new tab)

Earliest reviewed regional platform release entry, not a date inferred from the API selector.

Parameters
Not collected
Architecture
Not collected
Languages
Not collected
Context caching
SupportedSource for Context caching (opens in a new tab)

At least one reviewed endpoint supports this feature when true.

Data retention
Default inference prompts and responses are retained up to 30 days, subject to legal/security exceptions. Stateful conversation storage and files remain until deleted by the user. This release is not named in the current ZDR roster; do not assume zero retention.Source for Data retention (opens in a new tab)
API aliases
qwen3.7-flash-2026-07-15Source for API aliases (opens in a new tab)
Search grounding
SupportedSource for Search grounding (opens in a new tab)

At least one reviewed endpoint supports this feature when true.

Prefix completion
SupportedSource for Prefix completion (opens in a new tab)

At least one reviewed endpoint supports this feature when true.

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

Alibaba Model Studio · Singapore · International

Provider source (opens in a new tab)
API model ID
qwen3.7-flash-2026-07-15
Access
OpenAI-compatible Chat Completions or Responses using a matching regional workspace API key; built-in tool availability is model- and region-specific.
Regions
Singapore / International deployment scope
Published request quota
15000 requests/minuteSource for Published request quota (opens in a new tab)
Published token quota
5,000,000 tokens/minuteSource for Published token quota (opens in a new tab)
INPUT / 1M TOKENS$0.03
OUTPUT / 1M TOKENS$0.13

Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate. Cached input price: $0.006 / 1M tokens (base tier).

Pricing by prompt length, USD / 1M tokens
Input lengthInputOutputCached input
Input<=32k$0.03$0.13$0.006
32k<Input<=256k$0.10$0.40$0.02
256k<Input<=1m$0.20$0.80$0.04
USD · observed 14 Oct 2026 · Pricing evidence (opens in a new tab)
Published billing units · original currency · observed 14 Oct 2026
CategoryUsageRateUnit
Explicit cache · Input<=32kExplicit Cache Creation1$0.0381M tokens
Explicit cache · Input<=32kExplicit Cache Read1$0.0031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Creation2$0.1251M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Read2$0.011M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Creation3$0.251M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Read3$0.021M tokens

Rate conditions

  1. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  2. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
Pricing source (opens in a new tab)

Data & enterprise terms

Default inference prompts and responses are retained up to 30 days, subject to legal/security exceptions. Stateful conversation storage and files remain until deleted by the user. This release is not named in the current ZDR roster; do not assume zero retention.

Read the service policy (opens in a new tab)

Alibaba Model Studio · China (Beijing)

Provider source (opens in a new tab)
API model ID
qwen3.7-flash-2026-07-15
Access
OpenAI-compatible Chat Completions or Responses using a matching regional workspace API key; built-in tool availability is model- and region-specific.
Regions
China (Beijing)
Published request quota
30000 requests/minuteSource for Published request quota (opens in a new tab)
Published token quota
5,000,000 tokens/minuteSource for Published token quota (opens in a new tab)
INPUT / 1M TOKENS$0.028
OUTPUT / 1M TOKENS$0.11

Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate. Cached input price: $0.006 / 1M tokens (base tier).

Pricing by prompt length, USD / 1M tokens
Input lengthInputOutputCached input
Input<=32k$0.028$0.11$0.006
32k<Input<=256k$0.083$0.33$0.017
256k<Input<=1m$0.165$0.66$0.033
USD · observed 14 Oct 2026 · Pricing evidence (opens in a new tab)
Published billing units · original currency · observed 14 Oct 2026
CategoryUsageRateUnit
Explicit cache · Input<=32kExplicit Cache Creation1$0.0341M tokens
Explicit cache · Input<=32kExplicit Cache Read1$0.0031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Creation2$0.1031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Read2$0.0081M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Creation3$0.2061M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Read3$0.0171M tokens

Rate conditions

  1. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  2. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
Pricing source (opens in a new tab)

Data & enterprise terms

Default inference prompts and responses are retained up to 30 days, subject to legal/security exceptions. Stateful conversation storage and files remain until deleted by the user. This release is not named in the current ZDR roster; do not assume zero retention.

Read the service policy (opens in a new tab)

Alibaba Model Studio · Germany (Frankfurt) · Global

Provider source (opens in a new tab)
API model ID
qwen3.7-flash-2026-07-15
Access
OpenAI-compatible Chat Completions or Responses using a matching regional workspace API key; built-in tool availability is model- and region-specific.
Regions
Germany (Frankfurt) / Global deployment scope
Published request quota
15000 requests/minuteSource for Published request quota (opens in a new tab)
Published token quota
5,000,000 tokens/minuteSource for Published token quota (opens in a new tab)
INPUT / 1M TOKENS$0.028
OUTPUT / 1M TOKENS$0.11

Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate. Cached input price: $0.006 / 1M tokens (base tier).

Pricing by prompt length, USD / 1M tokens
Input lengthInputOutputCached input
Input<=32k$0.028$0.11$0.006
32k<Input<=256k$0.083$0.33$0.017
256k<Input<=1m$0.165$0.66$0.033
USD · observed 14 Oct 2026 · Pricing evidence (opens in a new tab)
Published billing units · original currency · observed 14 Oct 2026
CategoryUsageRateUnit
Explicit cache · Input<=32kExplicit Cache Creation1$0.0341M tokens
Explicit cache · Input<=32kExplicit Cache Read1$0.0031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Creation2$0.1031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Read2$0.0081M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Creation3$0.2061M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Read3$0.0171M tokens

Rate conditions

  1. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  2. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
Pricing source (opens in a new tab)

Data & enterprise terms

Default inference prompts and responses are retained up to 30 days, subject to legal/security exceptions. Stateful conversation storage and files remain until deleted by the user. This release is not named in the current ZDR roster; do not assume zero retention.

Read the service policy (opens in a new tab)

Alibaba Model Studio · US (Virginia) · Global

Provider source (opens in a new tab)
API model ID
qwen3.7-flash-2026-07-15
Access
OpenAI-compatible Chat Completions or Responses using a matching regional workspace API key; built-in tool availability is model- and region-specific.
Regions
US (Virginia) / Global deployment scope
INPUT / 1M TOKENS$0.028
OUTPUT / 1M TOKENS$0.11

Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate. Cached input price: $0.006 / 1M tokens (base tier).

Pricing by prompt length, USD / 1M tokens
Input lengthInputOutputCached input
Input<=32k$0.028$0.11$0.006
32k<Input<=256k$0.083$0.33$0.017
256k<Input<=1m$0.165$0.66$0.033
USD · observed 14 Oct 2026 · Pricing evidence (opens in a new tab)
Published billing units · original currency · observed 14 Oct 2026
CategoryUsageRateUnit
Explicit cache · Input<=32kExplicit Cache Creation1$0.0341M tokens
Explicit cache · Input<=32kExplicit Cache Read1$0.0031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Creation2$0.1031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Read2$0.0081M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Creation3$0.2061M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Read3$0.0171M tokens

Rate conditions

  1. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  2. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
Pricing source (opens in a new tab)

Data & enterprise terms

Default inference prompts and responses are retained up to 30 days, subject to legal/security exceptions. Stateful conversation storage and files remain until deleted by the user. This release is not named in the current ZDR roster; do not assume zero retention.

Read the service policy (opens in a new tab)

Alibaba Model Studio · Japan (Tokyo) · Global

Provider source (opens in a new tab)
API model ID
qwen3.7-flash-2026-07-15
Access
OpenAI-compatible Chat Completions or Responses using a matching regional workspace API key; built-in tool availability is model- and region-specific.
Regions
Japan (Tokyo) / Global deployment scope
Published request quota
15000 requests/minuteSource for Published request quota (opens in a new tab)
Published token quota
5,000,000 tokens/minuteSource for Published token quota (opens in a new tab)
INPUT / 1M TOKENS$0.028
OUTPUT / 1M TOKENS$0.11

Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate. Cached input price: $0.006 / 1M tokens (base tier).

Pricing by prompt length, USD / 1M tokens
Input lengthInputOutputCached input
Input<=32k$0.028$0.11$0.006
32k<Input<=256k$0.083$0.33$0.017
256k<Input<=1m$0.165$0.66$0.033
USD · observed 14 Oct 2026 · Pricing evidence (opens in a new tab)
Published billing units · original currency · observed 14 Oct 2026
CategoryUsageRateUnit
Explicit cache · Input<=32kExplicit Cache Creation1$0.0341M tokens
Explicit cache · Input<=32kExplicit Cache Read1$0.0031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Creation2$0.1031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Read2$0.0081M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Creation3$0.2061M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Read3$0.0171M tokens

Rate conditions

  1. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  2. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
Pricing source (opens in a new tab)

Data & enterprise terms

Default inference prompts and responses are retained up to 30 days, subject to legal/security exceptions. Stateful conversation storage and files remain until deleted by the user. This release is not named in the current ZDR roster; do not assume zero retention.

Read the service policy (opens in a new tab)

Alibaba Model Studio · Hong Kong (China) · Global

Provider source (opens in a new tab)
API model ID
qwen3.7-flash-2026-07-15
Access
OpenAI-compatible Chat Completions or Responses using a matching regional workspace API key; built-in tool availability is model- and region-specific.
Regions
Hong Kong (China) / Global deployment scope
Published request quota
15000 requests/minuteSource for Published request quota (opens in a new tab)
Published token quota
5,000,000 tokens/minuteSource for Published token quota (opens in a new tab)
INPUT / 1M TOKENS$0.028
OUTPUT / 1M TOKENS$0.11

Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate. Cached input price: $0.006 / 1M tokens (base tier).

Pricing by prompt length, USD / 1M tokens
Input lengthInputOutputCached input
Input<=32k$0.028$0.11$0.006
32k<Input<=256k$0.083$0.33$0.017
256k<Input<=1m$0.165$0.66$0.033
USD · observed 14 Oct 2026 · Pricing evidence (opens in a new tab)
Published billing units · original currency · observed 14 Oct 2026
CategoryUsageRateUnit
Explicit cache · Input<=32kExplicit Cache Creation1$0.0341M tokens
Explicit cache · Input<=32kExplicit Cache Read1$0.0031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Creation2$0.1031M tokens
Explicit cache · 32k<Input<=256kExplicit Cache Read2$0.0081M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Creation3$0.2061M tokens
Explicit cache · 256k<Input<=1mExplicit Cache Read3$0.0171M tokens

Rate conditions

  1. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  2. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
Pricing source (opens in a new tab)

Data & enterprise terms

Default inference prompts and responses are retained up to 30 days, subject to legal/security exceptions. Stateful conversation storage and files remain until deleted by the user. This release is not named in the current ZDR roster; do not assume zero retention.

Read the service policy (opens in a new tab)

Caching

Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.

01 / INITIAL INPUTProcess & retain

The system processes eligible input and retains reusable state.

02 / LATER REQUESTCheck available state

Reuse depends on matching input, session state and the cache policy.

03 / CACHE HITReuse & generate

Reusing state can reduce repeated work. Any charges follow the billing rules below.

Alibaba Model Studio · Singapore · International

qwen3.7-flash-2026-07-15
Documented
Support evidence (opens in a new tab)
How it works
Explicit cache and automatic implicit cacheSource for How it works (opens in a new tab)
Minimum reusable input
1,024 shared-prefix tokens; eligibility does not guarantee a hitSource for Minimum reusable input (opens in a new tab)
Lifetime & refresh
Explicit: 5 minutes, renewed on hit. Implicit: no guaranteed fixed lifetime.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Reuse identical prefixes for implicit caching. For explicit caching, set cache_control type ephemeral; up to four markers. Modes do not combine.Source for How to enable it (opens in a new tab)
Usage fields
Inspect prompt_tokens_details.cached_tokens for Chat Completions; API-specific usage fields distinguish cache reads and writes.Source for Usage fields (opens in a new tab)
Billing rules
Implicit reads, explicit reads and explicit writes have separate published prices. Output remains billed; batch and caching discounts do not stack.Source for Billing rules (opens in a new tab)
Limits & data boundaries
Exact prefix matching, regional availability and cache minimums apply. Explicit and implicit caching are mutually exclusive.Source for Limits & data boundaries (opens in a new tab)
Cache reads, writes & storage
ChargeApplies toRate / unit
Cache read1Text tokens · Input<=32k$0.006 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 32k<Input<=256k$0.02 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 256k<Input<=1m$0.04 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation2Explicit cache · Input<=32k$0.038 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read2Explicit cache · Input<=32k$0.003 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation3Explicit cache · 32k<Input<=256k$0.125 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read3Explicit cache · 32k<Input<=256k$0.01 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation4Explicit cache · 256k<Input<=1m$0.25 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read4Explicit cache · 256k<Input<=1m$0.02 / 1M tokensPricing evidence (opens in a new tab)

Rate conditions

  1. Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate.
  2. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  4. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.

Observed 14 Oct 2026. Write rates and storage fees are different charges; use the billing rules above.

Caching reviewed 14 Oct 2026

Alibaba Model Studio · China (Beijing)

qwen3.7-flash-2026-07-15
Documented
Support evidence (opens in a new tab)
How it works
Explicit cache and automatic implicit cacheSource for How it works (opens in a new tab)
Minimum reusable input
1,024 shared-prefix tokens; eligibility does not guarantee a hitSource for Minimum reusable input (opens in a new tab)
Lifetime & refresh
Explicit: 5 minutes, renewed on hit. Implicit: no guaranteed fixed lifetime.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Reuse identical prefixes for implicit caching. For explicit caching, set cache_control type ephemeral; up to four markers. Modes do not combine.Source for How to enable it (opens in a new tab)
Usage fields
Inspect prompt_tokens_details.cached_tokens for Chat Completions; API-specific usage fields distinguish cache reads and writes.Source for Usage fields (opens in a new tab)
Billing rules
Implicit reads, explicit reads and explicit writes have separate published prices. Output remains billed; batch and caching discounts do not stack.Source for Billing rules (opens in a new tab)
Limits & data boundaries
Exact prefix matching, regional availability and cache minimums apply. Explicit and implicit caching are mutually exclusive.Source for Limits & data boundaries (opens in a new tab)
Cache reads, writes & storage
ChargeApplies toRate / unit
Cache read1Text tokens · Input<=32k$0.006 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 32k<Input<=256k$0.017 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 256k<Input<=1m$0.033 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation2Explicit cache · Input<=32k$0.034 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read2Explicit cache · Input<=32k$0.003 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation3Explicit cache · 32k<Input<=256k$0.103 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read3Explicit cache · 32k<Input<=256k$0.008 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation4Explicit cache · 256k<Input<=1m$0.206 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read4Explicit cache · 256k<Input<=1m$0.017 / 1M tokensPricing evidence (opens in a new tab)

Rate conditions

  1. Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate.
  2. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  4. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.

Observed 14 Oct 2026. Write rates and storage fees are different charges; use the billing rules above.

Caching reviewed 14 Oct 2026

Alibaba Model Studio · Germany (Frankfurt) · Global

qwen3.7-flash-2026-07-15
Documented
Support evidence (opens in a new tab)
How it works
Explicit cache and automatic implicit cacheSource for How it works (opens in a new tab)
Minimum reusable input
1,024 shared-prefix tokens; eligibility does not guarantee a hitSource for Minimum reusable input (opens in a new tab)
Lifetime & refresh
Explicit: 5 minutes, renewed on hit. Implicit: no guaranteed fixed lifetime.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Reuse identical prefixes for implicit caching. For explicit caching, set cache_control type ephemeral; up to four markers. Modes do not combine.Source for How to enable it (opens in a new tab)
Usage fields
Inspect prompt_tokens_details.cached_tokens for Chat Completions; API-specific usage fields distinguish cache reads and writes.Source for Usage fields (opens in a new tab)
Billing rules
Implicit reads, explicit reads and explicit writes have separate published prices. Output remains billed; batch and caching discounts do not stack.Source for Billing rules (opens in a new tab)
Limits & data boundaries
Exact prefix matching, regional availability and cache minimums apply. Explicit and implicit caching are mutually exclusive.Source for Limits & data boundaries (opens in a new tab)
Cache reads, writes & storage
ChargeApplies toRate / unit
Cache read1Text tokens · Input<=32k$0.006 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 32k<Input<=256k$0.017 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 256k<Input<=1m$0.033 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation2Explicit cache · Input<=32k$0.034 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read2Explicit cache · Input<=32k$0.003 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation3Explicit cache · 32k<Input<=256k$0.103 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read3Explicit cache · 32k<Input<=256k$0.008 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation4Explicit cache · 256k<Input<=1m$0.206 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read4Explicit cache · 256k<Input<=1m$0.017 / 1M tokensPricing evidence (opens in a new tab)

Rate conditions

  1. Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate.
  2. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  4. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.

Observed 14 Oct 2026. Write rates and storage fees are different charges; use the billing rules above.

Caching reviewed 14 Oct 2026

Alibaba Model Studio · US (Virginia) · Global

qwen3.7-flash-2026-07-15
Documented
Support evidence (opens in a new tab)
How it works
Explicit cache and automatic implicit cacheSource for How it works (opens in a new tab)
Minimum reusable input
1,024 shared-prefix tokens; eligibility does not guarantee a hitSource for Minimum reusable input (opens in a new tab)
Lifetime & refresh
Explicit: 5 minutes, renewed on hit. Implicit: no guaranteed fixed lifetime.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Reuse identical prefixes for implicit caching. For explicit caching, set cache_control type ephemeral; up to four markers. Modes do not combine.Source for How to enable it (opens in a new tab)
Usage fields
Inspect prompt_tokens_details.cached_tokens for Chat Completions; API-specific usage fields distinguish cache reads and writes.Source for Usage fields (opens in a new tab)
Billing rules
Implicit reads, explicit reads and explicit writes have separate published prices. Output remains billed; batch and caching discounts do not stack.Source for Billing rules (opens in a new tab)
Limits & data boundaries
Exact prefix matching, regional availability and cache minimums apply. Explicit and implicit caching are mutually exclusive.Source for Limits & data boundaries (opens in a new tab)
Cache reads, writes & storage
ChargeApplies toRate / unit
Cache read1Text tokens · Input<=32k$0.006 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 32k<Input<=256k$0.017 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 256k<Input<=1m$0.033 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation2Explicit cache · Input<=32k$0.034 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read2Explicit cache · Input<=32k$0.003 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation3Explicit cache · 32k<Input<=256k$0.103 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read3Explicit cache · 32k<Input<=256k$0.008 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation4Explicit cache · 256k<Input<=1m$0.206 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read4Explicit cache · 256k<Input<=1m$0.017 / 1M tokensPricing evidence (opens in a new tab)

Rate conditions

  1. Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate.
  2. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  4. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.

Observed 14 Oct 2026. Write rates and storage fees are different charges; use the billing rules above.

Caching reviewed 14 Oct 2026

Alibaba Model Studio · Japan (Tokyo) · Global

qwen3.7-flash-2026-07-15
Documented
Support evidence (opens in a new tab)
How it works
Explicit cache and automatic implicit cacheSource for How it works (opens in a new tab)
Minimum reusable input
1,024 shared-prefix tokens; eligibility does not guarantee a hitSource for Minimum reusable input (opens in a new tab)
Lifetime & refresh
Explicit: 5 minutes, renewed on hit. Implicit: no guaranteed fixed lifetime.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Reuse identical prefixes for implicit caching. For explicit caching, set cache_control type ephemeral; up to four markers. Modes do not combine.Source for How to enable it (opens in a new tab)
Usage fields
Inspect prompt_tokens_details.cached_tokens for Chat Completions; API-specific usage fields distinguish cache reads and writes.Source for Usage fields (opens in a new tab)
Billing rules
Implicit reads, explicit reads and explicit writes have separate published prices. Output remains billed; batch and caching discounts do not stack.Source for Billing rules (opens in a new tab)
Limits & data boundaries
Exact prefix matching, regional availability and cache minimums apply. Explicit and implicit caching are mutually exclusive.Source for Limits & data boundaries (opens in a new tab)
Cache reads, writes & storage
ChargeApplies toRate / unit
Cache read1Text tokens · Input<=32k$0.006 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 32k<Input<=256k$0.017 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 256k<Input<=1m$0.033 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation2Explicit cache · Input<=32k$0.034 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read2Explicit cache · Input<=32k$0.003 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation3Explicit cache · 32k<Input<=256k$0.103 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read3Explicit cache · 32k<Input<=256k$0.008 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation4Explicit cache · 256k<Input<=1m$0.206 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read4Explicit cache · 256k<Input<=1m$0.017 / 1M tokensPricing evidence (opens in a new tab)

Rate conditions

  1. Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate.
  2. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  4. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.

Observed 14 Oct 2026. Write rates and storage fees are different charges; use the billing rules above.

Caching reviewed 14 Oct 2026

Alibaba Model Studio · Hong Kong (China) · Global

qwen3.7-flash-2026-07-15
Documented
Support evidence (opens in a new tab)
How it works
Explicit cache and automatic implicit cacheSource for How it works (opens in a new tab)
Minimum reusable input
1,024 shared-prefix tokens; eligibility does not guarantee a hitSource for Minimum reusable input (opens in a new tab)
Lifetime & refresh
Explicit: 5 minutes, renewed on hit. Implicit: no guaranteed fixed lifetime.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Reuse identical prefixes for implicit caching. For explicit caching, set cache_control type ephemeral; up to four markers. Modes do not combine.Source for How to enable it (opens in a new tab)
Usage fields
Inspect prompt_tokens_details.cached_tokens for Chat Completions; API-specific usage fields distinguish cache reads and writes.Source for Usage fields (opens in a new tab)
Billing rules
Implicit reads, explicit reads and explicit writes have separate published prices. Output remains billed; batch and caching discounts do not stack.Source for Billing rules (opens in a new tab)
Limits & data boundaries
Exact prefix matching, regional availability and cache minimums apply. Explicit and implicit caching are mutually exclusive.Source for Limits & data boundaries (opens in a new tab)
Cache reads, writes & storage
ChargeApplies toRate / unit
Cache read1Text tokens · Input<=32k$0.006 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 32k<Input<=256k$0.017 / 1M tokensPricing evidence (opens in a new tab)
Cache read1Text tokens · 256k<Input<=1m$0.033 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation2Explicit cache · Input<=32k$0.034 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read2Explicit cache · Input<=32k$0.003 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation3Explicit cache · 32k<Input<=256k$0.103 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read3Explicit cache · 32k<Input<=256k$0.008 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Creation4Explicit cache · 256k<Input<=1m$0.206 / 1M tokensPricing evidence (opens in a new tab)
Explicit Cache Read4Explicit cache · 256k<Input<=1m$0.017 / 1M tokensPricing evidence (opens in a new tab)

Rate conditions

  1. Published regional list rates, excluding promotions. K=1,000 and M=1,000,000. Total input length selects the rate for the whole request. Cached input is implicit-cache reads. Explicit cache and batch charges are separate.
  2. Alternative billing mode for this endpoint. Whole-request input tier: Input<=32k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  3. Alternative billing mode for this endpoint. Whole-request input tier: 32k<Input<=256k. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.
  4. Alternative billing mode for this endpoint. Whole-request input tier: 256k<Input<=1m. Explicit cache writes and reads replace the corresponding input-token charge. Batch and cache discounts do not stack; published rounded rates are preserved.

Observed 14 Oct 2026. Write rates and storage fees are different charges; use the billing rules above.

Caching reviewed 14 Oct 2026

What the measurements say

No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.

Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.

The record behind the model

Why it is included

Inference from release-specific Alibaba-managed API documentation and the reviewed official Qwen public-weight inventory. No matching weights are published for this named hosted release in that inventory. Public Qwen3.8-Flash-Next, Qwen3.8-2.4T-A95B and older Qwen-Omni checkpoints are separate identities and are excluded; this is not a blanket classification of the Qwen family.

Classification evidence (opens in a new tab)

Lifecycle dates

Platform release · Singapore / International21 Jul 2026Source (opens in a new tab)
Platform release · US (Virginia) / Global21 Jul 2026Source (opens in a new tab)
Platform release · China (Beijing)21 Jul 2026Source (opens in a new tab)
Platform release · Hong Kong (China) / Global21 Jul 2026Source (opens in a new tab)
Platform release · Germany (Frankfurt) / Global21 Jul 2026Source (opens in a new tab)
Platform release · Japan (Tokyo) / Global21 Jul 2026Source (opens in a new tab)

Sources reviewed