Qwen3.6 27B
alibaba/qwen3-6-27bVon Alibaba (Qwen) · Familie: qwen · veröffentlicht 2026-04-22
Prices in USD per 1M tokens. Unknown means the provider does not publish per-token pricing.
Fähigkeiten
Model fit scores
0–100 · higher is betterThese scores reward declared capabilities, context size, price and provider availability — they are not benchmark results. Use them as a directional signal alongside your own evaluation.
Coding88
- Tool calling40/40
- Structured output20/20
- Reasoning10/10
- Context window (100K → 1M)8/20
- Provider availability10/10
Agents100
- Tool calling35/35
- Structured output25/25
- Reasoning15/15
- Output token limit15/15
- Provider availability10/10
JSON / structured output92
- Structured output / JSON mode50/50
- Tool calling20/20
- Temperature control10/10
- Price-friendly for high-volume12/20
Cost efficiency47
- Headline price (log-scaled)47/95
- Has prompt-cache pricing0/5
Long context61
- Context window (100K → 2M)51/90
- Has published price for full window10/10
Vision91
- Accepts image input50/50
- Context window (10K → 1M)21/30
- Has published price10/10
- Provider availability10/10
Production-readiness94
- Number of independent providers40/40
- Has published per-token price20/20
- Context window ≥ 8K15/15
- No data inconsistencies across providers4/10
- Official model (not derivative)15/15
Cost Efficiency Index
Open full calculator →Estimated cost using the recommended provider's headline rate. Each scenario fixes average input/output tokens — the assumptions are shown in the third column.
| Scenario | Cost | Assumption |
|---|---|---|
RAG answer per 1,000 RAG answers | $4.80 < $0.01 per request | 5K input tokens (query + 4 retrieved chunks of ~1K each) and a 500-token answer. Typical SaaS knowledge-base bot. |
Support ticket triage per 10,000 tickets | $9.60 < $0.01 per request | 1K input tokens (ticket body + system prompt) and a 100-token JSON classification reply. High-volume customer support. |
Data extraction per 1,000 documents | $3.00 < $0.01 per request | 2K input tokens (a single document page) and a 500-token JSON extraction. ETL / invoice / form pipelines. |
Code review per 1,000 PRs | $8.40 < $0.01 per request | 8K input tokens (diff + surrounding files) and a 1K-token review comment. PR-bot workloads. |
Agent step per 1,000 steps | $9.36 < $0.01 per request | 12K input tokens (long-running tool history) and a 600-token tool-call decision. Cost per agent step. |
Preis-Details
Empfohlene Preise von alibaba · qwen3.6-27b
Günstigster Anbieter: crof · $0.200 Eingabe + $1.50 Ausgabe
Bei 11 Anbietern verfügbar
| Anbieter | Anbieter-Modell-ID | Eingabe / 1M | Ausgabe / 1M | Kontext | Veröffentlicht |
|---|---|---|---|---|---|
| Alibaba alibaba | qwen3.6-27b | $0.600 | $3.60 | 262K | 2026-04-22 |
| OpenRouter openrouter | qwen/qwen3.6-27b | $0.260 | $2.38 | 262K | 2026-04-22 |
| Vercel AI Gateway vercel | alibaba/qwen3.6-27b | $0.600 | $3.60 | 256K | 2026-04-22 |
| Hugging Face huggingface | Qwen/Qwen3.6-27B | $0.470 | $3.19 | 262K | 2026-04-22 |
| Venice AI venice | qwen3-6-27b | $0.325 | $3.25 | 256K | 2026-04-24 |
| SiliconFlow siliconflow | Qwen/Qwen3.6-27B | $0.300 | $3.20 | 262K | 2026-04-22 |
| OVHcloud AI Endpoints ovhcloud | qwen3.6-27b | $0.470 | $3.19 | 262K | 2026-06-01 |
| Kilo Gateway kilo | qwen/qwen3.6-27b | $0.325 | $3.25 | 256K | 2026-04-27 |
| CrofAI crof | qwen3.6-27b | $0.200 | $1.50 | 262K | 2026-04-22 |
| routing.run routing-run | route/qwen3.6-27b | $1.10 | $3.30 | 202K | 2026-04-22 |
| NanoGPT nano-gpt | alibaba/qwen3.6-27b | $0.203 | $2.24 | 260K | 2026-04-23 |
Datenunterschiede zwischen Anbietern
- context_window varies: 202000, 256000, 260096, 262140, 262144
- release_date varies (span 40d): 2026-04-22, 2026-04-23, 2026-04-24, 2026-04-27, 2026-06-01
- modalities varies across offerings
Anbieter melden unterschiedliche Werte für dieses Modell. Die Schnellinfos oben nutzen den repräsentativen Anbieter; pro Anbieter siehe Tabelle.
Frequently asked questions
How much does Qwen3.6 27B cost?
Qwen3.6 27B costs $0.600 per 1M input tokens and $3.60 per 1M output tokens, sourced from alibaba. Cache reads, audio tokens and >200K-context tiers (where applicable) are listed in the Pricing detail block above.
What is the context window of Qwen3.6 27B?
Qwen3.6 27B has a context window of 262K tokens, with a max output of 66K tokens per reply. This is the total combined size of prompt + completion.
Does Qwen3.6 27B support tool calling?
Yes. Qwen3.6 27B supports tool calling (function calling). This makes it suitable for production agent and automation workloads where the model has to invoke external functions reliably.
Does Qwen3.6 27B support structured output / JSON mode?
Yes. Qwen3.6 27B supports structured output / JSON-schema-constrained decoding. This makes it suitable for production agent and automation workloads where the model has to invoke external functions reliably.
Can Qwen3.6 27B accept image input?
Yes. Qwen3.6 27B accepts both text and image input. Vision pricing per image is usually billed on top of the regular token rate — check Alibaba (Qwen)'s docs for the exact rule.
Is Qwen3.6 27B open-weight?
Yes. Qwen3.6 27B's weights are publicly available, so you can self-host or fine-tune. Note that open weights ≠ open source — the training data and code are typically not released.
What are the best alternatives to Qwen3.6 27B?
If Qwen3.6 27B doesn't fit, consider Qwen3.5 397B-A17B, Qwen3 32B, Qwen3.7 Max. Each one targets the same use case — see the Related links below for direct head-to-head pages.
Where does this data come from?
All numbers are normalised into a single canonical model record and reconciled with each provider's official documentation. We re-pull daily and write any changes (price, context, capability) to the /changelog page.
Explore more
More Alibaba (Qwen) models
- Qwen3.5 397B-A17B$0.60 in / $3.60 out
- Qwen3 32B$0.70 in / $2.80 out
- Qwen3.7 Max$2.50 in / $7.50 out
- Qwen3.6 Plus$0.50 in / $3.00 out
- Qwen3 235B A22B Instruct 2507$0.10 in / $0.10 out
Capability lists this model is in
Zuletzt aktualisiert:
Pricing and capabilities are refreshed daily and reconciled against each provider's official documentation. Always verify critical production decisions with the provider directly.