
Qwen3-Coder-Next is an open-weight causal language model optimized for coding agents and local development workflows. It uses a sparse MoE design with 80B total parameters and only 3B activated per token, delivering performance comparable to models with 10 to 20x higher active compute, which makes it well suited for cost-sensitive, always-on agent deployment.
The model is trained with a strong agentic focus and performs reliably on long-horizon coding tasks, complex tool usage, and recovery from execution failures. With a native 256k context window, it integrates cleanly into real-world CLI and IDE environments and adapts well to common agent scaffolds used by modern coding tools. The model operates exclusively in non-thinking mode and does not emit <think> blocks, simplifying integration for production coding agents.
Modalities
In / Out Price
$0.12 / $0.80per 1M
Context
262K
Released
Feb 4, 2026
Qwen3-Coder-Next is an open-weight causal language model optimized for coding agents and local development workflows. It uses a sparse MoE design with 80B total parameters and only 3B activated per token, delivering performance comparable to models with 10 to 20x higher active compute, which makes it well suited for cost-sensitive, always-on agent deployment.
Qwen3 Coder Next costs $0.12/M input tokens and $0.80/M output tokens, with separate rates for Cache Read at $0.07/M tokens.
Qwen3 Coder Next has a 262,144 token context window. It supports up to 262,144 completion tokens.
Yes. Qwen3 Coder Next accepts tools and tool_choice for function calling. It also supports structured outputs via a JSON schema in response_format.
Qwen3 Coder Next is served by 4 providers on OpenRouter: Parasail, StreamLake, NovitaAI and Alibaba Cloud Int.. Requests are routed to the best available provider, with automatic failover to the others, and you can pin or exclude providers with provider routing.
Qwen3 Coder Next was released on February 4, 2026.
Different companies host the same model. OpenRouter routes your request to one of them based on the routing mode you pick — Balanced (price + speed), Nitro (fastest), or Exacto (highest tool-calling accuracy).
The average price customers actually pay for this model, next to the prices providers post. Caching and discounts mean the price actually paid is often well below the listed one.
Throughput is how fast the model writes (tokens per second — higher is better). Latency is total round-trip time (lower is better). TTFT is time-to-first-token — how long before you see anything appear (lower is better).
Uptime is the percentage of the past 3 days that at least one provider was responding to requests. Availability is the percentage of time that inference was successfully served. OpenRouter continuously monitors and uses the next-best provider when one returns an error.
Scores on standardized evaluations. Higher percentages are better — and rank percentile shows where this model lands among all models on OpenRouter.
Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for.
Token volume and request traffic to this model over time.
Drop-in code to call this model. OpenRouter's API is OpenAI-compatible — most SDKs work by just swapping the base URL. The only thing that changes between models is the model slug below.
| $0.12 | $0.80 | $0.07 | 0.56s | 57 tps | ||
40% off | $0.30$0.18 | $1.50$0.90 | $0.06$0.036 | 0.63s | 116 tps | |
| $0.20 | $1.50 | -- | 1.70s | 31 tps | ||
| $0.30 | $1.50 | -- | 0.86s | 26 tps |
Throughput
116tok/s
P50, best across providers
Latency
0.56s
P50, best provider
100.00%
99.97%
When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and customization options.
