Back to Models

Qwen3.8 Flash

qwenqwen/qwen3.8-flash

Alibaba Qwen's 3.8-generation Flash tier: the cost/latency entry point into the 3.8 line, with a 1M-token context window.

Qwen3.8 Flash is Alibaba Qwen's low-cost 3.8-generation text route exposed in TheRouter as qwen/qwen3.8-flash. The live TheRouter catalog positions it as the cost and latency entry point into the Qwen3.8 line, with the same 1M-token context window and 131K maximum completion cap recorded for the other 3.8 text routes.

Use it as a traffic lane, not as the flagship. It is the right first candidate for classification, extraction, summaries, short agent steps, and long-context text jobs where qwen/qwen3.8-max or qwen/qwen3.8-27b would waste budget. Because the route is text input and text output in TheRouter, visual analysis should stay on qwen/qwen3.8-max or another configured vision model.

This page is intentionally scoped to the TheRouter route. Pricing, context, output limits, modalities, and supported parameters are rendered from standard-models.yaml; the curated layer explains when to choose the route and where upstream or provider documentation should not be over-read into TheRouter behavior.

Best for
  • β€’ High-volume classification, extraction, and routing tasks where Qwen3.8 behavior is useful but Max-tier quality is unnecessary
  • β€’ Long-context text summarization and cleanup where a 1M-token window matters more than top-end reasoning
  • β€’ Agent substeps, draft generation, and structured-output helpers that need tools and response_format at a lower unit price
  • β€’ Fallback lanes from qwen/qwen3.8-27b or qwen/qwen3.8-max after evals prove the request class is simple enough
Reach for something else if
  • β€’ Image, video, OCR, or screenshot understanding through TheRouter; this route is text input and text output
  • β€’ Hard reasoning, architecture review, and complex debugging where qwen/qwen3.8-max or qwen/qwen3.8-27b is worth the extra cost
  • β€’ Strict quality-critical generation until your own evals show the Flash lane matches the required acceptance rate

How TheRouter serves this differently from the vendor

As the vendor operates it

Alibaba Cloud and Qwen materials describe the Qwen3.8 family and provider-side model ids. Provider documentation may include regional pricing, rolling availability, and model-family behavior that changes outside this repository.

On TheRouter

TheRouter currently serves qwen/qwen3.8-flash as a text-input, text-output OpenAI-compatible chat route with catalog pricing and parameters taken from standard-models.yaml.

Context Length
1M
Max Output
131K
Input Priceper 1M tokens
$0.162/ 1M tokens
Output Priceper 1M tokens
$0.5076/ 1M tokens

Modalities

text→text

Pricing Breakdown

TypeRate
Input$0.162 / 1M tokens
Output$0.5076 / 1M tokens

Supported Parameters

temperaturemax_tokenstop_ptoolstool_choiceresponse_formatstop

Specifications

TheRouter route scopeText input and text output in the current TheRouter cataloggithub.com/therouter/ai-router β†—verified
Context window1,000,000 tokens in TheRouter's cataloggithub.com/therouter/ai-router β†—verified
TheRouter max completion131,072 tokensgithub.com/therouter/ai-router β†—verified
Supported request parameterstemperature, max_tokens, top_p, tools, tool_choice, response_format, stopgithub.com/therouter/ai-router β†—verified
TheRouter list pricing$0.15 input / $0.47 output per 1M tokens in the standard cataloggithub.com/therouter/ai-router β†—verified
International provider price cardAlibaba Cloud Model Studio international USD pricing was the source noted for the 3.8 family in TheRouter configalibabacloud.com β†—verified

Benchmarks

BenchmarkDistributionScoreSource
Published Qwen3.8 Flash benchmark table
The scheduled curator run did not execute paid or third-party benchmark verification. Treat vendor-reported numbers as routing context until a funded evaluation ledger exists.
β€”Not publicly disclosedβ€”
TheRouter text routing evals
No internal pass/fail ledger for TheRouter Flash workloads was produced in this no-budget page fill.
β€”Not publicly disclosedβ€”
Latency and throughput
Flash naming is a cost and latency signal, not a TheRouter measurement. Run a workload-specific benchmark before promoting this route to production defaults.
β€”Not publicly disclosedβ€”

API Usage Examples

Use the global api.therouter.ai endpoint shown below for new integrations; the legacy China accelerated endpoint is retired.

cURL
curl https://api.therouter.ai/v1/chat/completions   -H "Content-Type: application/json"   -H "Authorization: Bearer $THE_ROUTER_API_KEY"   -d '{
    "model": "qwen/qwen3.8-flash",
    "messages": [
      {"role": "user", "content": "Summarize the key points from this input."}
    ]
  }'

Chat completion

Use the standard OpenAI-compatible chat route with the public TheRouter model id.

cURL
curl https://api.therouter.ai/v1/chat/completions \
  -H "Authorization: Bearer $THEROUTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"qwen/qwen3.8-flash","messages":[{"role":"user","content":"Summarize this incident report into three action items."}]}'

More from qwen

Similar models

Cross-provider sibling models

News & changes

2026-09-19

TheRouter verifies Qwen3.8 Flash in the deployed Aliyun Bailian route

The standard-models.yaml entry records a live verification against the deployed provider service with the upstream echoing the exact qwen/qwen3.8-flash id. That makes the catalog route a verified TheRouter behavior, not only a vendor listing.

Guides

Frequently asked

When should I choose qwen/qwen3.8-flash?

Choose it when the workload is text-only, cost-sensitive, and likely to pass evals on a Flash-class model. It is a strong first lane for extraction, classification, summarization, and lightweight agent steps before escalating to qwen/qwen3.8-27b or qwen/qwen3.8-max.

Does qwen/qwen3.8-flash support vision through TheRouter?

No. The current TheRouter catalog lists text input and text output for this route. Use qwen/qwen3.8-max or another configured vision route for screenshots, OCR, image review, or video-frame reasoning.

Why does the page still lose completeness points?

The snippets component only increases after a verification ledger record exists. This scheduled run had no paid API budget and did not execute snippets, so the page is expected to remain capped near the non-snippet ceiling until a human approves a funded verification run.

Fact ledger β€” every claim on this page traces here
sourceURLretrieved
TheRouter route scopegithub.com/therouter/ai-router β†—2026-09-22verified
Context windowgithub.com/therouter/ai-router β†—2026-09-22verified
TheRouter max completiongithub.com/therouter/ai-router β†—2026-09-22verified
Supported request parametersgithub.com/therouter/ai-router β†—2026-09-22verified
TheRouter list pricinggithub.com/therouter/ai-router β†—2026-09-22verified
International provider price cardalibabacloud.com β†—2026-09-22verified
Published Qwen3.8 Flash benchmark tableqwen.ai β†—2026-09-22unknown
TheRouter text routing evalsgithub.com/therouter/ai-router β†—2026-09-22unknown
Latency and throughputhelp.aliyun.com β†—2026-09-22unknown
TheRouter verifies Qwen3.8 Flash in the deployed Aliyun Bailian routegithub.com/therouter/ai-router β†—2026-09-22verified
When should I choose qwen/qwen3.8-flash?github.com/therouter/ai-router β†—2026-09-22to verify
Does qwen/qwen3.8-flash support vision through TheRouter?github.com/therouter/ai-router β†—2026-09-22to verify
Why does the page still lose completeness points?github.com/therouter/ai-router β†—2026-09-22to verify
Help & contact