Qwen 3.6 Plus
Qwen 3.6 Plus is the Qwen 3.6 Plus-tier model in Alibaba Cloud's Qwen 3 family, building on the reasoning, instruction following, and agentic capabilities of Qwen3.5-Plus with a context window of 1M tokens. Your use is subject to Alibaba Cloud's Terms & Privacy Policies.
View API reference- Input and output price
- Prices from: Input $0.50, Output $3, Per 1M tokens
- 24h uptime
- Loading AI Gateway uptime
import { streamText } from 'ai'
const result = streamText({ model: 'alibaba/qwen3.6-plus', prompt: 'Why is the sky blue?'})Copy link to headingPlayground
Try out Qwen 3.6 Plus by Alibaba Cloud. Usage is billed to your team at API rates. Free users (those who haven't made a payment) get $5 of credits every 30 days.
Qwen 3.6 Plus
Copy link to headingProviders
Route requests across multiple providers. Copy a provider slug to set your preference. Visit the docs for more info. Using a provider means you agree to their terms, listed under Legal.
| Provider |
|---|
Copy link to headingUptime24 hours
Direct request success rate on AI Gateway and per-provider. Visit the docs for more info.
Copy link to headingThroughput24 hours
P50 throughput on live AI Gateway traffic, in tokens per second (TPS). Visit the docs for more info.
Copy link to headingLatency24 hours
P50 time to first token (TTFT) on live AI Gateway traffic, in milliseconds. View the docs for more info.
Getting started
Call Qwen 3.6 Plus through AI Gateway with the AI SDK generateText and streamText functions, or through the OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages APIs by changing the base URL. AI Gateway authenticates the request and routes it to an available provider.
Install the AI SDK (pnpm add ai dotenv), create an API key from the API Keys page, and set it as AI_GATEWAY_API_KEY in your environment. Full setup is covered in the text generation quickstart.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'alibaba/qwen3.6-plus', prompt: 'Why is the sky blue?', });
console.log(result.text);}
main().catch(console.error);Top-level parameters
The same Qwen 3.6 Plus request in each API format AI Gateway supports.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'alibaba/qwen3.6-plus', system: 'You are a concise technical assistant.', prompt: 'Summarize the tradeoffs between static generation and SSR.', maxOutputTokens: 1024, });
console.log(result.text);}
main().catch(console.error);Standard parameters like prompt, messages, temperature, and tools work as documented in the AI SDK docs. These are the parameters with model-specific behavior.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | Yes | Model ID in the form creator/model, e.g. alibaba/qwen3.6-plus. AI Gateway routes the request to an available provider. |
maxOutputTokens | number | No | Hard cap on generated tokens. Qwen 3.6 Plus supports up to 64,000 output tokens. Reasoning tokens count toward this limit. |
reasoning | 'provider-default' | 'none' | 'minimal' | 'low' | 'medium' | 'high' | 'xhigh' | No | Provider-agnostic reasoning effort, available in AI SDK 7 or later. Maps to the provider’s native reasoning configuration; reasoning settings under providerOptions take precedence when both are set. See the Reasoning section below. |
providerOptions | Record<string, JSONValue> | No | AI Gateway routing options under gateway, plus any provider-native options under the provider’s own namespace — see the table below. |
Input limits
| Input | Formats | Sources | Max count | Max size | Limits |
|---|---|---|---|---|---|
| Text | — | — | — | — | Prompt and response share the 1M-token context window |
| Image | — | URL, base64, Uint8Array | — | — | Sent as image parts in messages; counts as input tokens |
| — | URL, base64, Uint8Array | — | — | Sent as file parts in messages; counts as input tokens |
Provider options
Set AI Gateway routing options under providerOptions.gateway. For provider-specific options, pass them under the provider’s namespace as documented by the AI SDK.
Learn more in the AI SDK alibaba provider docs.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'alibaba/qwen3.6-plus', prompt: 'Why is the sky blue?', providerOptions: { gateway: { only: ['alibaba', 'togetherai'], }, }, });
console.log(result.text);}
main().catch(console.error);These AI Gateway routing options apply to every model. Provider-specific options pass through under the provider’s own namespace (for example providerOptions.anthropic) exactly as documented by the AI SDK.
| Parameter | Type | Required | Description |
|---|---|---|---|
providerOptions.gateway.only | string[] | No | Restrict routing to these provider slugs. Requests fail over only within the listed providers. |
providerOptions.gateway.order | string[] | No | Preferred provider order. Listed providers are tried first; unlisted providers remain available as fallbacks. |
providerOptions.gateway.sort | 'cost' | 'ttft' | 'tps' | No | Rank candidate providers by price, time to first token, or tokens per second instead of the default routing order. |
providerOptions.gateway.zeroDataRetention | boolean | No | Route only to providers with a zero-data-retention policy for this model. |
Routing across providers
AI Gateway serves the same model through multiple providers and fails over automatically. order expresses a preference while keeping every provider eligible; only is a hard allowlist — if none of the listed providers are available the request fails instead of falling back.
Options under a provider's own namespace (for example providerOptions.anthropic) are forwarded to that provider with the request. Providers ignore option namespaces that don't apply to them, so it is safe to set provider options alongside gateway routing options.
Reasoning
AI Gateway bridges reasoning across every API format. The AI SDK exposes a provider-agnostic top-level reasoning level (none, minimal, low, medium, high, or xhigh); the Chat Completions and Responses formats take the same effort under reasoning.effort; and the Anthropic Messages format uses a native thinking token budget. Whichever you send, the gateway maps it to the target model’s native configuration, converting between effort levels and token budgets as needed. Reasoning-related settings under providerOptions take full precedence over the top-level reasoning value and are never merged. Reasoning tokens typically count toward your output-token usage, though how they’re reported and billed varies by provider.
Learn more in the AI Gateway reasoning guide.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'alibaba/qwen3.6-plus', prompt: 'Explain the Monty Hall problem step by step.', reasoning: 'high', });
console.log(result.text);}
main().catch(console.error);Image input
Send images alongside text as message parts. Images count as input tokens.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'alibaba/qwen3.6-plus', messages: [ { role: 'user', content: [ { type: 'text', text: 'Describe this image.' }, { type: 'image', image: 'https://example.com/photo.jpg' }, ], }, ], });
console.log(result.text);}
main().catch(console.error);PDF input
Attach PDFs as file parts. Their contents count as input tokens.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'alibaba/qwen3.6-plus', messages: [ { role: 'user', content: [ { type: 'text', text: 'Summarize this document.' }, { type: 'file', mediaType: 'application/pdf', data: 'https://example.com/document.pdf', }, ], }, ], });
console.log(result.text);}
main().catch(console.error);Tool calling
Expose tools the model can call. Define each tool’s inputs with a Zod schema.
import { generateText, tool } from 'ai';import { z } from 'zod';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'alibaba/qwen3.6-plus', prompt: 'What is the weather in San Francisco?', tools: { getWeather: tool({ description: 'Get the current weather for a location', inputSchema: z.object({ location: z.string() }), execute: async ({ location }) => ({ location, temperatureC: 18 }), }), }, });
console.log(result.text);}
main().catch(console.error);Copy link to headingAbout Qwen 3.6 Plus
Qwen 3.6 Plus is the Qwen 3.6 generation of Alibaba Cloud's Plus-tier hosted models, succeeding Qwen3.5-Plus in the production Qwen 3 lineup. It ships with a context window of 1M tokens and is available through Alibaba Cloud, Together AI on AI Gateway.
The Qwen Plus line targets workloads that need deeper reasoning and stronger instruction adherence than the Flash tier provides. Qwen 3.6 Plus continues that positioning, building on the Qwen 3 architecture's strengths in multi-step reasoning, code generation, and agentic tool use. Like earlier Plus models, it supports structured outputs and tool calling, letting the model decide when to invoke registered functions or external APIs during multi-turn sessions.
For teams already using Qwen3.5-Plus, Qwen 3.6 Plus offers an incremental upgrade path. It slots into existing integrations that reference the Qwen Plus tier without requiring changes to prompt structure or tool-calling configuration. The model is accessible through AI Gateway's unified API, which handles provider routing, retries, and consolidated billing.
Copy link to headingWhat To Consider When Choosing a Provider
- Configuration: As a newer Plus-tier option than Qwen3.5-Plus, monitor the AI Gateway cost dashboard to compare per-token spend and confirm the quality uplift justifies any pricing difference for your workload.
- Zero Data Retention: Zero Data Retention is available for this model. It is offered on a per-provider and model basis. See the documentation for details.
- Authentication: AI Gateway authenticates requests using an API key or OIDC token. You do not need to manage provider credentials directly.
Copy link to headingWhen to Use Qwen 3.6 Plus
Best for
- Deliberate multi-step reasoning: Analytical workflows, structured document processing, and multi-constraint problem solving
- High-fidelity code generation: Refactoring and code work where instruction adherence and accuracy outweigh raw throughput
- Multi-turn agentic pipelines: Tool-calling across many turns where the model plans and invokes external APIs autonomously
- Long-context workloads: Passing full documents or codebases without chunking using the window of 1M tokens
- Upgrading from Qwen3.5-Plus: Teams moving to the Qwen 3.6 Plus tier without changing their integration
Consider alternatives when
- Throughput and cost first: Use a Flash-tier model when deep reasoning isn't required and latency and price dominate
- Multimodal vision input: A VL (vision-language) variant in the Qwen family is more appropriate for image-heavy tasks
- Higher parameter ceiling: Qwen3-235B or similar large MoE models offer more headroom for the most demanding challenges
- Video or image generation: This model generates text, not video or images
Copy link to headingConclusion
Qwen 3.6 Plus extends the Qwen Plus tier with the Qwen 3.6 generation of Alibaba Cloud's reasoning and instruction-following improvements. It's a direct upgrade path from Qwen3.5-Plus, accessible through AI Gateway with the same unified API, provider routing, and billing teams already use.
Copy link to headingFrequently Asked Questions
How does Qwen 3.6 Plus relate to Qwen3.5-Plus?
Qwen 3.6 Plus is the next generation in the Plus tier, succeeding Qwen3.5-Plus. It builds on the same architectural lineage with improvements to reasoning and instruction following.
What is the context window for Qwen 3.6 Plus?
The context window is 1M tokens. This applies to the combined input and output token length.
Does Qwen 3.6 Plus support tool calling and agentic workflows?
Yes. Like other Qwen 3 Plus-tier models, it supports structured tool calling, letting the model invoke registered functions or APIs during multi-turn sessions.
Can I switch from Qwen3.5-Plus to Qwen 3.6 Plus without changing my integration?
Yes. Update the model identifier in your AI Gateway request to `
alibaba/qwen3.6-plus`. No changes to prompt structure or tool-calling configuration are required.How do I access Qwen 3.6 Plus through AI Gateway?
Authenticate with an AI Gateway API key or OIDC token and specify `
alibaba/qwen3.6-plus` as the model. AI Gateway handles provider routing and retries automatically.When should I use a Flash-tier model instead of Qwen 3.6 Plus?
Use Flash when latency and per-token cost are the primary constraints and the task doesn't require deep multi-step reasoning. Plus is better suited for accuracy-first workloads.
What are typical latency characteristics?
This page shows live throughput and time-to-first-token metrics measured across real AI Gateway traffic.