Qwen 3.7 Max: Alibaba's May 2026 Flagship Guide

Alibaba's Qwen team has been the most active frontier-model shipper of 2026, and Qwen 3.7 Max is the clearest statement yet of where they're aiming: not a one-shot chat champion, but an agent — a model designed to keep working autonomously for hours, fire thousands of tool calls, and finish actual software-engineering tasks without a human in the loop.

This guide walks through what shipped, what the benchmarks actually say, how it compares to the rest of the May 2026 frontier, and when (and when not) to pick it for your stack.

What is Qwen 3.7 Max?

Qwen 3.7 Max is the top-tier variant of Alibaba's Qwen 3.7 family, launched on May 19, 2026, when API access landed on DashScope, with the formal Alibaba Cloud Summit keynote following on May 20. It's positioned as Alibaba's most capable agent model to date — designed for long-running, multi-step workflows rather than single-prompt question answering.

Three things matter about the launch:

• 1M-token context window. A step up from Qwen 3.5's 256K native window, with reworked long-context attention so retrieval at the tail of the window stays useful rather than degrading into noise.
• Native extended-thinking mode. The model generates an internal chain of thought before producing a final answer, optimized for high-difficulty logical reasoning, scientific computation, and expert-level queries. This is on by default for Max and tunable per-request.
• Agent-first design. Alibaba's internal demo had the model run autonomously for 35 hours while writing software for their new in-house Zhenwu M890 AI accelerator — over 1,000 tool calls and iterative code edits to optimize a kernel, with a claimed ~10x inference-speed improvement on the resulting code versus the previous baseline.

If you've been tracking Qwen, this is the same trajectory that started with Qwen 3.5 (the previous flagship) and accelerated through the 3.6 generation: thinking modes, sparse Mixture-of-Experts (MoE) routing, and ever-longer context. Qwen 3.7 Max is the agent-tuned culmination.

How does Qwen 3.7 Max compare to Qwen 3.5?

Qwen 3.5 was the previous flagship and is still the most-deployed open-weights Qwen variant in production right now. The jump to 3.7 Max is real but uneven — mostly concentrated in agentic and long-horizon tasks, less so in pure single-turn chat.

On Artificial Analysis's Intelligence Index, Qwen 3.7 Max scored 56.6, about 4.8 points above Qwen 3.6 Max Preview's 51.8 (Alibaba did not publish a direct head-to-head against the older 3.5 on this index). The gain comes mostly from:

• Stronger tool-calling reliability across hundreds of sequential calls
• Better long-horizon planning — the model now backs out of dead ends instead of getting stuck
• Improved math and scientific reasoning, especially when extended thinking is enabled
• Sharper coding diff edits (less hallucinated file paths, fewer phantom imports)

What did not change dramatically:

• Multilingual performance — Qwen 3.5 was already strong here, and 3.7 is incrementally better but not transformative
• Short-form chat quality — the difference is small enough that most casual users won't notice
• Pricing tier — broadly comparable on DashScope (see pricing section below)

If you're running an agent platform, 3.7 Max is a real upgrade. If you're using a Qwen model as a chat backbone, the jump from 3.5 is incremental.

What are the architecture and parameter count?

Alibaba has not officially disclosed the parameter count or detailed architecture for Qwen 3.7 Max. What we know:

• It is closed-weights and API-only. There is no GGUF, no Hugging Face checkpoint, no local-runnable version. (At launch, one was rumored to follow within 1–2 months matching the 3.6 release cadence; it never did — the open release skipped to Qwen 3.8 in August 2026.)
• It follows the same sparse Mixture-of-Experts (MoE) family pattern as Qwen 3.6 Max Preview (estimated ~1T total parameters in that earlier variant), with only a fraction of experts active per token to keep inference cost manageable.
• The 1M-token context window is enabled by a reworked attention scheme — Alibaba hasn't published a paper yet but third-party reviewers have measured solid recall at the 800K-token mark, which is meaningfully better than most nominal-only 1M-context claims from competitors.

Be honest with yourself here: if you need to inspect, audit, or self-host the weights for compliance reasons, Qwen 3.7 Max is not an option today. The mid-tier 3.7 release this paragraph originally told you to wait for never came — use Qwen3.8-27B (Apache-2.0, open since August 14, 2026) instead, with Qwen 3.5/3.6 as prior-generation options.

Is Qwen 3.7 Max open-weight or API-only?

API-only as of late May 2026. Both Qwen 3.7 Max and the smaller Qwen 3.7 Plus are closed-weights, accessible only through Alibaba Cloud's DashScope and Model Studio platforms (plus third-party aggregators like OpenRouter). Qwen3.7-Plus, the sibling model, adds vision input (Vision Arena #16) — the multimodal endpoint of the 3.7 lineup.

Forecast, as originally published: smaller open-weights variants expected Jun–Jul 2026 based on the Qwen 3.6 cadence, with the closed flagship (Max) staying API-only indefinitely and an Apache-2.0 mid-tier following within 1–3 months.

How that resolved (August 2026): both halves broke, in opposite directions.

• The open-weight mid-tier 3.7 never happened. Jun–Jul came and went with no weights; the 3.7 generation was skipped entirely for open release. The mid-tier slot was eventually filled by Qwen3.8-27B (August 14, 2026, Apache-2.0, native vision, 262K context).
• "Stays API-only indefinitely" was falsified at the next generation. On August 12, 2026 Alibaba released the open weights of Qwen3.8-2.4T-A95B — the open variant of Qwen3.8-Max and the first Qwen-Max-class model ever published, under a custom revenue-gated licence rather than Apache. Qwen 3.7 Max itself remains API-only.

For a broader read on which Chinese and US labs are shipping open weights right now and how to think about the trade-offs, see our open-source LLMs landscape 2026 guide.

How does Qwen 3.7 Max stack up against frontier models?

Here's the head-to-head against the May 2026 frontier on the benchmarks Alibaba and third-party reviewers have published. Important caveat: Terminal-Bench 2.0 and SWE-Pro results are from Alibaba's own published table, third-party-verified for Qwen and Claude but not for every entry. Treat the headline numbers as directional, not gospel.

Note: the "~" numbers in the comparator rows reflect Alibaba's launch-slide table (Qwen3.7-Max benchmark vs Claude Opus 4.6 Max, DeepSeek-V4-Pro Max, K2.6 Thinking); GPT-5.5 and Gemini 3.5 Flash numbers are third-party-aggregated. Qwen3.7-Max also reports the lowest hallucination rate among frontier models at 22.9%.

Reading the table honestly:

• Qwen 3.7 Max is genuinely competitive at the frontier on coding-agent benchmarks. Its SWE-Pro and Terminal-Bench numbers are within noise of Claude Opus 4.6 Max (the comparator in Alibaba's launch table above) and GPT-5.5, and ahead of DeepSeek V4 Pro on the same suite.
• It's not the absolute best at any single thing — GPT-5.5 still edges it on raw reasoning, Claude Opus 4.6 Max still feels better in real-world coding sessions according to most reviewers, and Gemini 3.5 Flash beats it on pure context length.
• The compelling angle is the combination: 1M context + extended thinking + frontier-tier coding scores + an aggressive price.

What does Qwen 3.7 Max cost on DashScope?

Pricing on Alibaba Cloud DashScope (and mirrored on OpenRouter for non-China customers):

• Input tokens: $2.50 / 1M tokens
• Output tokens: $7.50 / 1M tokens

Concretely:

• A typical coding request (2K input, 1K output): about $0.0125
• A heavy agent session (100K input, 50K output): about $0.625
• A long-horizon run that fills the full 1M context (1M input, 100K output): about $3.25

For comparison: Claude Opus 4.7 is roughly $15 / $75 per 1M, GPT-5.5 is around $10 / $30, DeepSeek V4 hovers around $0.30 / $1.20, and Gemini 3.5 Flash is the cheapest mainstream option at well under $1 combined. So Qwen 3.7 Max slots into the mid-tier of price-per-token, top tier on capability-per-dollar for agentic workloads.

There is no free tier on DashScope, but new accounts typically get a small trial credit. OpenRouter often has temporary promotional pricing on newly-launched models — worth checking on launch week.

How do you actually use Qwen 3.7 Max?

Three practical entry points, in order of how quickly you can be running real traffic:

1. Qwen Chat (no code, evaluation)

Sign in at chat.qwen.ai and pick Qwen3.7-Max from the model dropdown. Good for kicking the tires on reasoning quality before committing API spend. The chat UI exposes extended thinking as a toggle.

2. DashScope / Model Studio (native API)

Create an account at dashscope.aliyuncs.com, generate an API key, and call the OpenAI-compatible endpoint:

curl https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions \
  -H "Authorization: Bearer $DASHSCOPE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "qwen3.7-max",
    "messages": [{"role":"user","content":"Explain MoE routing in one paragraph."}],
    "enable_thinking": true
  }'

The OpenAI SDKs work unchanged — point base_url at the DashScope endpoint and the rest of your code stays the same. This is the path Alibaba recommends for production.

3. OpenRouter, Together AI, Fireworks, ModelScope (third-party aggregators)

If you're outside China and don't want a direct Alibaba Cloud relationship, OpenRouter resells the same model under qwen/qwen3.7-max with a small per-token margin. Together AI has a first-party Qwen/Qwen3.7-Max endpoint with US-region hosting, and Fireworks AI plus ModelScope also list the model. Easier billing, faster onboarding, slightly higher cost — pick Together AI if data residency outside China matters.

When should you pick Qwen 3.7 Max over Claude or GPT?

Honest, opinionated picks:

• Pick Qwen 3.7 Max for long-horizon coding agents. The combination of 1M context, sustained tool-call reliability, and aggressive pricing makes it the most economically viable choice for run-it-overnight workflows. Codex-style agents, repo-wide refactors, long-running debug loops — this is the sweet spot.
• Pick Claude Opus 4.7 for interactive coding. If a human is reading and accepting each diff, Opus still feels noticeably more aligned to engineering taste and is less likely to drift mid-session. The premium is real but so is the quality gap on subjective measures.
• Pick GPT-5.5 for raw reasoning and multimodal. If your workload mixes vision, complex math, and product-grade reliability, GPT-5.5 is still the safest default.
• Pick DeepSeek V4 for cost-sensitive open-weights deployments. If you need to self-host or want sub-cent-per-call economics, DeepSeek V4 is competitive and ships with weights. Qwen 3.7 Max wins on capability; DeepSeek V4 wins on TCO when you can run it yourself.
• Pick Gemini 3.5 Flash for ultra-long context + speed. 2M context, the lowest price, fast first-token latency — great for document-heavy summarization. Coding agents though, not so much.

There's also a non-technical consideration worth being explicit about: Qwen is an Alibaba model. Data routed through DashScope's China region is subject to PRC data laws; OpenRouter and Singapore-region DashScope endpoints route differently, but if you're in a US-regulated industry (healthcare, defense, finance) your compliance team will probably want to vet this carefully. Many enterprises end up using Qwen via OpenRouter or a third-party gateway specifically to keep one hop of plausible deniability between their data and a Chinese-jurisdiction endpoint. Not a deal-breaker, just something to plan for.

What are Qwen 3.7 Max's real weaknesses?

The honest list:

• No open weights. If you need on-prem, air-gapped, or audit-the-model deployments, you're stuck waiting for the eventual mid-tier release.
• English-coding tone. The model's natural-language explanations of code sometimes feel slightly translated — technically correct but stylistically off compared to Claude or GPT. Not a functional issue, but worth noting if you're shipping user-visible AI output.
• Tooling ecosystem is thinner. The Claude and OpenAI SDKs have years of community-maintained wrappers, integrations, and prompt libraries. Qwen via DashScope works fine through OpenAI-compatible mode, but the surrounding ecosystem (Anthropic Workbench, OpenAI's Codex, Cursor's deep integrations) doesn't natively favor it.
• LMArena ranking is good, not dominant. #13 overall is solid but reminds us this isn't a category-king-by-every-measure model — it's a category-leader on agent benchmarks specifically.
• Geopolitical risk. Sanctions, export controls, and corporate procurement policies in some jurisdictions complicate adopting a Chinese-lab model as your default backbone.

FAQ

When was Qwen 3.7 Max released?

Qwen 3.7 Max launched on May 19, 2026, when API access landed on DashScope; the formal announcement followed at the Alibaba Cloud Summit on May 20, 2026.

Is Qwen 3.7 Max open source?

No — and resolved August 2026: no open 3.7 ever followed. Qwen 3.7 Max and Qwen 3.7 Plus stayed closed, and the generation was skipped for open release. Alibaba instead open-weighted Qwen 3.8: the 2.4T-A95B flagship on August 12, 2026 (custom licence) and Qwen3.8-27B on August 14 (Apache-2.0).

How much does Qwen 3.7 Max cost?

On Alibaba Cloud DashScope: $2.50 per million input tokens and $7.50 per million output tokens. A typical 2K-input / 1K-output coding request costs about $0.0125. There's no free tier, but it's substantially cheaper than Claude Opus 4.7 or GPT-5.5.

What's the context window?

1 million tokens, with reworked long-context attention. Third-party reviewers measured solid recall at the 800K mark, which is meaningfully better than nominal-only 1M-context claims from some competitors.

How does Qwen 3.7 Max compare to DeepSeek V4?

On agentic coding benchmarks (SWE-Pro, Terminal-Bench 2.0), Qwen 3.7 Max scores slightly higher. DeepSeek V4 wins on per-token pricing and the fact that it ships open weights you can self-host. Use Qwen if you want the strongest agent capability via API; use DeepSeek V4 if cost or self-hosting matters more.

Can I run Qwen 3.7 Max locally?

No — and no 3.7 weights ever shipped. If you need a local Qwen, the best option since August 14, 2026 is Qwen3.8-27B (Apache-2.0, native vision, ~17GB at Q4_K_M on a single 24GB GPU — see how to run Qwen 3.8 locally), with the Qwen 3.5 and 3.6 checkpoints as prior-generation fallbacks.

Does it support tool calling and function calling?

Yes, natively. The OpenAI-compatible API supports the same tools and tool_choice parameters you'd use with GPT-5.5. Agent workflows with hundreds of sequential tool calls are explicitly the target use case.

What's the difference between Qwen 3.7 Max and Qwen 3.7 Plus?

Max is the frontier-tier, agent-tuned, extended-thinking flagship. Plus is a smaller, faster, cheaper variant aimed at high-volume routine chat and lighter agentic work. Pick Max when capability matters more than latency or cost; pick Plus for production workloads where you'd otherwise reach for GPT-5.5 mini or Claude Haiku.