Qwen: Qwen3.5 397B A17B

qwen/qwen3.5-397b-a17b

Created Feb 16, 2026262,144 context

$0.60/M input tokens$3.60/M output tokens

The Qwen3.5 series 397B-A17B native vision-language model is built on a hybrid architecture that integrates a linear attention mechanism with a sparse mixture-of-experts model, achieving higher inference efficiency. It delivers state-of-the-art performance comparable to leading-edge models across a wide range of tasks, including language understanding, logical reasoning, code generation, agent-based tasks, image understanding, video understanding, and graphical user interface (GUI) interactions. With its robust code-generation and agent capabilities, the model exhibits strong generalization across diverse agent.

Providers for Qwen3.5 397B A17B

OpenRouter routes requests to the best providers that are able to handle your prompt size and parameters, with fallbacks to maximize uptime.

Performance for Qwen3.5 397B A17B

Compare different providers across OpenRouter

Apps using Qwen3.5 397B A17B

Top public apps this month

Recent activity on Qwen3.5 397B A17B

Total usage per day on OpenRouter

Prompt

510M

Reasoning

277M

Completion

28.2M

Prompt tokens measure input size. Reasoning tokens show internal thinking before a response. Completion tokens reflect total output length.

Uptime stats for Qwen3.5 397B A17B

Uptime stats for Qwen3.5 397B A17B across all providers

Sample code and API for Qwen3.5 397B A17B

OpenRouter normalizes requests and responses across providers for you.

OpenRouter supports reasoning-enabled models that can show their step-by-step thinking process. Use the reasoning parameter in your request to enable reasoning, and access the reasoning_details array in the response to see the model's internal reasoning before the final answer. When continuing a conversation, preserve the complete reasoning_details when passing messages back to the model so it can continue reasoning from where it left off. Learn more about reasoning tokens.

In the examples below, the OpenRouter-specific headers are optional. Setting them allows your app to appear on the OpenRouter leaderboards.

Using third-party SDKs

For information about using third-party SDKs and frameworks with OpenRouter, please see our frameworks documentation.

See the Request docs for all possible fields, and Parameters for explanations of specific sampling parameters.