Compare / Qwen4-Max vs GPT-6.1 Sol
Qwen4-Max vs GPT-6.1 Sol
Which is cheaper, which is more capable, and which does better at each kind of work, from 78 results on 4 sources that measured both models.
Of the 78 results both models have, the better value on each. Results whose reported ranges overlap are too close to call.
Results as of 16 November 2026 (catalogue release 2026-11-16-49bdfa045dee). See also Alibaba vs OpenAI, every model from both labs.
Qwen4-Max or GPT-6.1 Sol? The short answer
Pick GPT-6.1 Sol: it scores higher (Spring Prompt overall 80 against 56) at about the same price.
- Spring Prompt overall: Qwen4-Max 56, GPT-6.1 Sol 80 (out of 100; how the score works).
- They cost about the same to run: $0.007 and $0.008 per product listing on CatalogBench.
- On our own benchmarks, on the results both models have: Qwen4-Max does better for decks from an analysis; GPT-6.1 Sol for product listings and speed under pressure.
Head to head
Every fact side by side
| Qwen4-Max | GPT-6.1 Sol | |
|---|---|---|
| Price per million tokens | $1.50 in · $4.50 out | $2.00 in · $10.00 out |
| Blended (3 in : 1 out) | $2.25 | $4.00 |
| Cheapest host, blended | – | $4.00 (Amazon Bedrock) |
| Cost per product listing (CatalogBench) | $0.007 | $0.008 |
| Cached input, per million | – | $0.10 cached input |
| Intelligence Index | – | 51.8 |
| Spring Prompt overall | 56 | 80 |
| Output speed, tokens a second | – | 53 |
| Context window | 1,000,000 tokens | 1,050,000 tokens |
| Released | – | 29 Sep 2026 |
| Weights | Closed | Closed |
| Developer based in | China | the US |
Prices are the developer's list price where we have read it, otherwise the typical host on OpenRouter; see every model's price. Intelligence and speed from Artificial Analysis.
Which is better for what
Each model's rank among the models on sale today, for each kind of work, from our own benchmarks and licensed sources. Further right is better; the better rank is in green.
From our research
Every shared result
Each model's best result on every measure both have, grouped by benchmark, with the setting that produced it. Under each measure, every model that benchmark has measured is a grey tick, best to the right, so you can see where the two sit in the field. The headline measures of each benchmark come first; the rest are under "Show all". Green marks the better value; where a source reports ranges that overlap, neither is marked.
| Measure | Qwen4-Max | GPT-6.1 Sol |
|---|---|---|
| BulletBench measured by Spring Prompt · 3 results | ||
| Cost per game · Blitz 3+2US dollars, lower is better 7 · 10 of 20 measured | $0.0400 | $0.0767 |
| Cost per game · Bullet 60sUS dollars, lower is better 42 · 50 of 59 measured | $0.0150low reasoning | $0.0210 |
| Ladder Elo · Bullet 60sladder Elo, higher is better 51 · 2 of 59 measured | 147low reasoning | 928Ultrafast (low reasoning) |
| CatalogBench measured by Spring Prompt · 3 results | ||
| Cost per productUS dollars, lower is better 13 · 16 of 33 measured | $0.0069 | $0.0084 |
| Reliably publish-ready% of products, higher is better 19 · 1 of 32 measured | 39.3% | 75.0% |
| Reliably publish-ready · sales brief% of products, higher is better 21 · 2 of 32 measured | 8.9% | 67.9% |
| DeckBench measured by Spring Prompt · 3 results | ||
| Cost per deckUS dollars, lower is better 23 · 21 of 33 measured | $0.18 | $0.15 |
| Deck ratingrating, higher is betterThe rating weighs each win by how strong the other deck was; the win rate counts wins against whichever decks a model happened to meet, so the two can disagree. 1 · 5 of 33 measured | 1,585 | 1,391 |
| Accurate decks% of tasks, higher is better 19 · 1 of 33 measured | 33.3% | 100.0% |
| SurveyBench measured by Spring Prompt · 3 results | ||
| Analysis ratingrating, higher is betterThe rating weighs each win by how strong the other analysis was; the win rate counts wins against whichever analyses a model happened to meet, so the two can disagree. 5 · 3 of 24 measured | 1,395 | 1,432 |
| Cost per taskUS dollars, lower is better 17 · 16 of 24 measured | $0.20 | $0.14 |
| Analysis scorepoints of 100, higher is better 8 · 2 of 24 measured | 88.9 | 96.6 |
Show all 78 results (66 more)
| Measure | Qwen4-Max | GPT-6.1 Sol |
|---|---|---|
| BulletBench measured by Spring Prompt · 7 results | ||
| Games lost on time · Blitz 3+2% of games, lower is better 20 · 1 of 20 measured | 87.5% | 0.0%Ultrafast |
| Games lost on time · Bullet 60s% of games, lower is better 54 · 31 of 59 measured | 87.5%low reasoning | 25.0%Ultrafast (low reasoning) |
| Invalid moves · Blitz 3+2% of moves, lower is better 1 · 1 of 20 measured | 0.0% | 0.0% |
| Invalid moves · Bullet 60s% of moves, lower is better 1 · 1 of 59 measured | 0.0%low reasoning | 0.0% |
| Ladder Elo · Blitz 3+2ladder Elo, higher is better 20 · 5 of 20 measured | 147 | 927Ultrafast |
| Median move time · Blitz 3+2milliseconds, lower is better 20 · 6 of 20 measured | 8.6 s | 2.1 sUltrafast |
| Median move time · Bullet 60smilliseconds, lower is better 58 · 37 of 59 measured | 4.4 slow reasoning | 1.4 sUltrafast (low reasoning) |
| CatalogBench measured by Spring Prompt · 28 results | ||
| Channel compliance% of products, higher is better 1 · 1 of 33 measured | 100.0% | 100.0% |
| Channel rules broken% of products, lower is better 1 · 1 of 33 measured | 0.0% | 0.0% |
| Channel rules broken · sales brief% of products, lower is better 25 · 1 of 33 measured | 1.2% | 0.0% |
| Claims to check% of products, lower is better 27 · 1 of 31 measured | 1.8% | 0.0% |
| Claims to check · sales brief% of products, lower is better 23 · 1 of 31 measured | 3.0% | 0.0% |
| Conflicts caught% of conflicts, higher is better 1 · 1 of 33 measured | 100.0% | 100.0% |
| Content quality% of checks, higher is better 15 · 3 of 33 measured | 97.5% | 98.6% |
| Content quality · sales brief% of checks, higher is better 12 · 2 of 33 measured | 97.9% | 98.8% |
| Decision accuracy% of decisions, higher is better 17 · 3 of 33 measured | 96.8% | 98.7% |
| Failed outputs% of products, lower is better 1 · 1 of 33 measured | 0.0% | 0.0% |
| Failed outputs · sales brief% of products, lower is better 1 · 1 of 33 measured | 0.0% | 0.0% |
| Field accuracy% of missing fields, higher is better 21 · 8 of 33 measured | 92.9% | 94.4% |
| Invented values% of filled values, lower is better 27 · 25 of 33 measured | 2.9% | 2.2% |
| Missing UK information% of products, lower is better 1 · 1 of 33 measured | 0.0% | 0.0% |
| Missing UK information · sales brief% of products, lower is better 1 · 1 of 33 measured | 0.0% | 0.0% |
| Not findable% of products, lower is better 9 · 19 of 33 measured | 3.0% | 4.8% |
| Not findable · sales brief% of products, lower is better 20 · 22 of 33 measured | 4.2% | 5.4% |
| Publish-ready listings% of products, higher is better 20 · 3 of 33 measured | 56.6% | 78.0% |
| Publish-ready listings · sales brief% of products, higher is better 20 · 5 of 33 measured | 25.6% | 72.0% |
| Time per productseconds, lower is better 21 · 11 of 33 measured | 20.9 | 10.2 |
| Unsupported claims% of products, lower is better 20 · 1 of 33 measured | 22.0% | 0.0% |
| Unsupported claimsclaims per product, lower is better 20 · 1 of 33 measured | 0.70 | 0.00 |
| Unsupported claims · sales brief% of products, lower is better 22 · 5 of 33 measured | 70.2% | 3.6% |
| Unsupported claims · sales briefclaims per product, lower is better 23 · 2 of 33 measured | 2.56 | 0.07 |
| Wrong attributes% of products, lower is better 26 · 16 of 33 measured | 20.2% | 16.7% |
| Wrong attributes · sales brief% of products, lower is better 27 · 20 of 33 measured | 21.4% | 19.1% |
| Wrong category or variant% of products, lower is better 6 · 6 of 33 measured | 1.8% | 1.8% |
| Wrong category or variant · sales brief% of products, lower is better 18 · 6 of 33 measured | 2.4% | 1.8% |
| DeckBench measured by Spring Prompt · 14 results | ||
| Caveat dropped% of tasks, lower is better 15 · 1 of 33 measured | 16.7% | 0.0% |
| Clean layout% of tasks, higher is better 24 · 3 of 33 measured | 16.7% | 83.3% |
| Design quality% of the maximum, higher is better 4 · 12 of 33 measured | 83.4% | 71.4% |
| Draft figure quoted% of tasks, lower is better 13 · 1 of 33 measured | 16.7% | 0.0% |
| Findings missing% of tasks, lower is better 1 · 1 of 33 measured | 0.0% | 0.0% |
| Head-to-head win rate% of comparisons, higher is betterThe rating weighs each win by how strong the other deck was; the win rate counts wins against whichever decks a model happened to meet, so the two can disagree. 3 · 5 of 33 measured | 86.3% | 81.0% |
| Layout defects% of tasks, lower is better 24 · 3 of 33 measured | 83.3% | 16.7% |
| Misleading metric used% of tasks, lower is better 1 · 1 of 33 measured | 0.0% | 0.0% |
| Presentable decks% of tasks, higher is better 15 · 3 of 33 measured | 0.0% | 50.0% |
| Recommendation late or wrong% of tasks, lower is better 1 · 1 of 33 measured | 0.0% | 0.0% |
| Slides needing work% of tasks, lower is better 10 · 17 of 33 measured | 33.3% | 50.0% |
| Time per deckseconds, lower is better 31 · 22 of 33 measured | 489 | 179 |
| Unsupported claims% of tasks, lower is better 24 · 1 of 33 measured | 33.3% | 0.0% |
| Unsupported numbers% of tasks, lower is better 26 · 1 of 33 measured | 16.7% | 0.0% |
| SurveyBench measured by Spring Prompt · 17 results | ||
| Head-to-head win rate% of comparisons, higher is betterThe rating weighs each win by how strong the other analysis was; the win rate counts wins against whichever analyses a model happened to meet, so the two can disagree. 5 · 2 of 24 measured | 69.9% | 78.2% |
| Leading or double-barrelled questions% of tasks, lower is better 3 · 1 of 24 measured | 11.1% | 0.0% |
| Mistaken next steps% of tasks, lower is better 5 · 5 of 24 measured | 11.1% | 11.1% |
| Numbers right% of answers, higher is better 16 · 1 of 24 measured | 99.0% | 100.0% |
| Objectives unanswerable% of tasks, lower is better 1 · 1 of 24 measured | 0.0% | 0.0% |
| Precision ignored% of tasks, lower is better 1 · 1 of 24 measured | 0.0% | 0.0% |
| Research scorepoints of 100, higher is better 8 · 2 of 24 measured | 90.8 | 97.0 |
| Sound research% of tasks, higher is better 4 · 1 of 24 measured | 33.3% | 66.7% |
| Stakeholder's view presumed% of tasks, lower is better 1 · 1 of 24 measured | 0.0% | 0.0% |
| Survey plan scorepoints of 100, higher is better 5 · 1 of 24 measured | 95.2 | 97.8 |
| Survey structure% of tasks, lower is better 11 · 3 of 24 measured | 22.2% | 11.1% |
| Time per taskseconds, lower is better 23 · 15 of 24 measured | 690 | 222 |
| Traps handled% of traps, higher is better 2 · 5 of 24 measured | 98.6% | 95.7% |
| Traps missed% of tasks, lower is better 2 · 6 of 24 measured | 11.1% | 33.3% |
| Unsupported findings% of tasks, lower is better 11 · 1 of 24 measured | 55.6% | 0.0% |
| Wrong numbers% of tasks, lower is better 13 · 1 of 24 measured | 11.1% | 0.0% |
| Wrong recommendation% of tasks, lower is better 12 · 5 of 24 measured | 22.2% | 11.1% |
Compare them with other models
- Alibaba vs OpenAIEvery model from both labs, best against best
- Qwen4-Max vs GPT-6.1 TerraHighest-scoring overall at $1–3 per million tokens
- Qwen4-Max vs Claude Fable 5.2Highest-scoring overall available today
- Qwen4-Max vs Gemini 3.8 FlashJust above overall
- Qwen4-Max vs Gemini 4 CarbonJust below overall
- GPT-6.1 Sol vs Claude Opus 5.5Most intelligent at $3–10 per million tokens
- GPT-6.1 Sol vs Muse Spark 1.3Cheapest with similar intelligence
Quick answers
Is Qwen4-Max better than GPT-6.1 Sol?
Pick GPT-6.1 Sol: it scores higher (Spring Prompt overall 80 against 56) at about the same price.
Which is cheaper, Qwen4-Max or GPT-6.1 Sol?
They cost about the same to run: $0.007 and $0.008 per product listing on CatalogBench.
Which is better for product listings, Qwen4-Max or GPT-6.1 Sol?
GPT-6.1 Sol ranks 2 of 32 models on sale for turning a sparse product feed and photos into listings that can go live, against 19 for Qwen4-Max.
Which is better for decks from an analysis, Qwen4-Max or GPT-6.1 Sol?
Qwen4-Max ranks 1 of 32 models on sale for turning a finished analysis into a deck you could present as it is, against 5 for GPT-6.1 Sol.
Which is better for user surveys, Qwen4-Max or GPT-6.1 Sol?
GPT-6.1 Sol ranks 3 of 23 models on sale for planning a user survey and reading its results without being misled, against 5 for Qwen4-Max.
Which is better for speed under pressure, Qwen4-Max or GPT-6.1 Sol?
GPT-6.1 Sol ranks 3 of 35 models on sale for good decisions against a real clock (fast chess), against 26 for Qwen4-Max.
Which has the bigger context window, Qwen4-Max or GPT-6.1 Sol?
GPT-6.1 Sol: 1,050,000 tokens, against 1,000,000 for Qwen4-Max.
Run Qwen4-Max and GPT-6.1 Sol on your own prompt.
Benchmarks aren't your task. Test both side by side on your prompt, with every answer checked against your rules and the cost of each one.