Alibaba's flagship reasoning model: 262K context, up to 81,920 thinking tokens, and strong tool-assisted HLE results.
Output Speed *
Intelligence Index *
Context Window *
Input price
Output price
Performance
Where Qwen3 Max Thinking Gains Most: Reasoning That Can Call Tools
Benchmarks
Independent Results: Real Reasoning Gains, Weak Knowledge Reliability
Output Speed
Intelligence Index
MMLU *
GPQA *
HLE *
LiveCodeBench *
Technical Specifications
What the model supports
Limitations & Trade-offs
Best-Fit Workloads
Where this model earns its place
Tool-assisted research analysis
Alibaba's reported 49.8 on HLE with tools, versus 30.2 without, shows the model gains most when it can retrieve information and run code. Adaptive tool use, covering search, memory and a code interpreter, was a headline feature of the launch. It suits research assistants and analyst workflows that gather evidence before answering. Because independent knowledge scores are weak, require source citations and verify retrieved claims.
Hard math and STEM problem solving
Alibaba reports 98.0 on HMMT Feb 25, 87.4 on GPQA and 85.9 on LiveCodeBench v6, all vendor-run. The 81,920-token thinking budget gives room for long derivations. This fits solution generation for tutoring products, scientific analysis, and offline verification of difficult problems. It is a poor fit for interactive use where seconds matter, since reasoning tokens arrive before the answer.
Long-document reasoning
A 262,144-token window with up to 258,048 input tokens lets the model reason across large contracts, specifications or multi-file code excerpts in one request. This suits cross-document reconciliation and structured findings reports. The thinking-mode answer cap of 32,768 tokens limits very long outputs. Inputs beyond roughly 258K tokens need chunking or a larger-context model such as Qwen3.8-Max.
Escalation tier for agent pipelines
Function calling plus a configurable thinking budget make it usable as the planner for hard cases in an agent system. Route routine steps to a lighter model and send ambiguous or multi-step tasks here. Its long reasoning traces and modest independent speed expectations make it a poor default for every step, so reserve it for decisions where reasoning quality outweighs latency.