MiniMax M3 vs Qwen3.8 Max

MiniMax M3 已从我们的目录下线。下方是它最后公布的价格;这个模型已无法调用,对比中的另一个模型仍可正常调用。

vs

什么时候选哪个

minimax-m3 在价目表的每一行都更便宜,输入 $0.3、输出 $1.2,对比 qwen3.8-max 的 $2 和 $6——约低 6.7 倍和 5 倍——而且它还在文本和图像之外接受视频,带 1000000 token 上下文和最多 524288 token 输出,并允许关闭思考。qwen3.8-max 更贵,输出上限 131072 token,上下文 983616 token,所以当你想要阿里更新的 2026 年 8 月模型、在文本和图像工作上带明确视觉标志时用它。大批量、长输出或视频输入的任务,minimax-m3 是划算的选择。

Benchmark 成绩

MiniMax M3:供应商没有公布 benchmark 成绩。

高于同类均值无更高分Qwen3.8 Max31 / 408 / 40
MiniMax M3 Qwen3.8 Max 其他参测模型 同类均值 ★ 没有模型得分更高
SWE-Bench Pro
N/A
67.7%
AndroidBench
N/A
75.1%
Cybergym
N/A
78.5%
HealthBench
N/A
没有模型得分更高 60.2%
JobBench
N/A
53.4%
PLawBench
N/A
没有模型得分更高 73.2%
GPQA Diamond
N/A
92.6%
Agents' Last Exam
N/A
27%

供应商公布: Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Anthropic Anthropic Anthropic Anthropic ByteDance DeepSeek DeepSeek Google Google Google Google MiniMax Moonshot Moonshot OpenAI OpenAI OpenAI OpenAI OpenAI OpenAI OpenAI Tencent Z.ai Z.ai Z.ai Z.ai

价格

MiniMax M3 Qwen3.8 Max Δ
输入 / 1M token $0.3 $2 0.15×
输出 / 1M token $1.2 $6 0.2×
缓存读取 / 1M token $0.06 $0.25 0.24×
缓存写入 不单独收费 1.25x -

价格取自构建时的实时目录,最新价格见各模型页面。

两个模型所处的位置:全部 91 个按同一单位计费的聊天模型的每 1M token 输入价分布(对数刻度)

MiniMax M3 · $0.3 Qwen3.8 Max · $2
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

能力

MiniMax M3 Qwen3.8 Max
工具调用 是 是
思考控制 可配置 是,但供应商未公布调节参数
结构化输出 - 是
提示词缓存 隐式(自动) 隐式 + 显式
缓存有效期 未公布 explicit: 5m, reset on hit
最小缓存前缀 512 个 token 1,024 个 token

规格

MiniMax M3 Qwen3.8 Max
输入模态 文本 图像 视频 文本 图像
输出模态 文本 文本
发布日期 2026-06-01 2026-08-03
上下文窗口 1,000,000 983,616
最大输出 524,288 131,072
思考参数
  • thinking.type
  • reasoning_split
-
可选值
thinking.type
  • adaptive
  • disabled
reasoning_split
  • boolean
-
默认值 adaptive:思考开启,由模型判断何时需要额外推理 -

规格照录自各供应商的文档;供应商没有公布的项目,对应的行直接省略,不做推断。 完整来源: MiniMax M3 · Qwen3.8 Max

同一条提示词,两个模型,经网关实测

提示词 Explain to a CFO, in exactly three sentences, why our LLM bill doubled after we enabled reasoning. 检查 恰好 3 句

MiniMax M3 通过 · 3 sentences

Reasoning models don't just answer — they first generate extensive internal "thinking" tokens to work through the problem step-by-step, and you're billed for all of those tokens even though users never see them. A query that previously cost ~200 tokens may now cost 2,000–10,000 once reasoning is enabled, multiplying per-query spend by roughly 5–50x while the visible output stayed the same size — that's the doubling. The lever is tuning: cap reasoning effort on simple queries, cache the reasoning traces, and reserve the full reasoning model for only your hardest 10–20% of requests, which typically restores 60–80% of the savings.

输出 764 tok (+629 思考) 延迟 3.5 s

Qwen3.8 Max 通过 · 3 sentences

Enabling reasoning makes the model produce additional hidden steps before responding, and those tokens are billable. It also tends to lengthen each interaction because the model works through more possibilities before settling on an answer. Therefore, the bill doubled mainly due to higher compute and token usage per request, not necessarily because the number of requests doubled.

输出 378 tok (+305 思考) 延迟 8.6 s

指令遵循(恰好三句,数得出来)、受众适配(对 CFO 说话的口吻),以及下方 token 计数暴露出的隐藏思考计费差额。

提示词 This function is supposed to return the longest run of consecutive equal items, but callers report it is off by one on single-element inputs and misses runs that end at the last index. Fix it and explain the bug in one paragraph. 检查 修复通过测试

MiniMax M3 通过 · 8/8 cases

The bug is that the loop starts at index 1 and treats `cur` as the number of *equal transitions* rather than the run length, so a run of *k* consecutive equal items is reported as `k − 1`, and a single-element list (where the loop body never executes) returns 0 instead of 1. A correct version tracks the actual run length by seeding `cur = 1` and resetting it to 1 (not 0) on a mismatch: ```python def longest_run(xs): if not xs: return 0 best = cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 if cur > best: best = cur return best ``` Now `[5]` returns `1`, `[1,1,1]` returns `3`, and a run like `[1,2,2,2]` that ends at the last index is correctly captured as `3` because `cur` is updated before `best` is compared on every iteration, including the final one.

输出 845 tok (+596 思考) 延迟 3.5 s

Qwen3.8 Max 通过 · 8/8 cases

```python def longest_run(xs): if not xs: return 0 best = cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 best = max(best, cur) return best ``` The bug is that the original code starts `best` and `cur` at `0`, so it counts adjacent equal *transitions* rather than the number of items in the run. A run of length `n` has only `n - 1` equal-neighbor transitions, so single-element inputs return `0`, and runs that reach the end are undercounted by one. Initializing the current run to `1` for the first element, resetting it to `1` on a break, and updating `best` from that count fixes the off-by-one.

输出 1616 tok (+1411 思考) 延迟 34.7 s

修复是否真的正确(能运行)、解释的信息密度,以及在一个范围明确的任务上的 token 效率。

提示词 Extract a JSON object with fields {company, quarter, revenue_usd_m, growth_pct, guidance} from this text. Use null for anything not stated; add no other fields. 检查 合法 JSON,严格符合 schema

MiniMax M3 通过 · 5/5 fields, guidance null

```json { "company": null, "quarter": "Q3", "revenue_usd_m": 412, "growth_pct": null, "guidance": null } ```

输出 1002 tok (+955 思考) 延迟 3.6 s

Qwen3.8 Max 通过 · 5/5 fields, guidance null

{ "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null }

输出 1199 tok (+1141 思考) 延迟 24.4 s

是否严守 schema(不臆造字段)、能否顶住幻觉压力(原文明说暂不给出 guidance),以及结构化输出路径的差异。

提示词 Write a 120-word product announcement for an API gateway feature that caches prompts across providers. Forbidden words: "seamless", "unlock", "game-changer", "revolutionize", "empower". Exactly one sentence must be a question. 检查 120 词,0 个禁用词

MiniMax M3 通过 · 121 words, 0 banned, 1 question

Introducing PromptCache, our intelligent caching layer for the API gateway. Tired of paying twice for identical requests? The feature stores prompt-response pairs across every connected provider, returning cached results instead of hitting costly endpoints. Deployment requires only a single configuration flag, and semantic similarity detection happens automatically. Latency drops up to 70% on repeated traffic while costs follow the same downward curve. Developers access detailed cache hit metrics, eviction logs, and provider breakdowns through the dashboard. Whether routing to OpenAI, Anthropic, or local models, every cached token saves time and money. The cache respects TTL policies, supports manual purging, and encrypts stored content. Available today for Pro and Enterprise tiers—enable PromptCache on existing endpoints and watch inference bills shrink immediately.

输出 2808 tok (+2656 思考) 延迟 6.0 s

Qwen3.8 Max 通过 · 120 words, 0 banned, 1 question

Today, our API gateway adds prompt caching across major model providers. It stores prompts and responses in one fast cache layer. Teams can lower token spend, reduce latency, and repeat reliable answers. The feature supports OpenAI, Anthropic, Google, and Mistral through one configuration. You can set retention rules, scope access, and invalidate entries quickly. How does your team maintain consistent results during provider outages? Approved cached responses keep applications stable while fallback routes recover. The dashboard shows hit rates, savings, latency, and provider usage. Engineers receive audit trails for every cached prompt, enabling safer testing. Product managers can compare cost trends before and after cache adoption. Start with a small route, then safely expand caching to production traffic right now.

输出 2744 tok (+2591 思考) 延迟 46.3 s

是否守住约束(字数预算、禁用词表、只能有一个问句)、文风特征,以及长度控制。

改一行代码就能在两个模型之间切换

下方每个标签页里都有两个模型 ID,高亮的那两行是唯一要改的地方。端点不变,API key 不变,请求结构也不变。

from openai import OpenAI

client = OpenAI(
    base_url="https://synthorai.io/v1",
    api_key="sk-syn-...",
)

resp = client.chat.completions.create(
    model="minimax-m3",
    # model="qwen3.8-max",  # 取消注释此行,注释上一行
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

获取 API key →

常见问题

MiniMax M3 和 Qwen3.8 Max 哪个更便宜?

按「输入 / 1M token」算,MiniMax M3 更便宜($0.3 对 $2,相差 6.7×)。其他计费项的结论可能相反,完整价格见上方表格,实际成本取决于你的用量构成。

不用分别集成两次,就能对 MiniMax M3 和 Qwen3.8 Max 做 A/B 测试吗?

可以。两个模型走同一个 OpenAI 兼容端点,用同一个 API key,切换时只要改一行里的模型名,所以可以给两个模型各分一部分流量,直接对比账单。

MiniMax M3 和 Qwen3.8 Max 支持提示词缓存吗?

支持。两个模型的缓存读取价都低于各自的输入价,所以前缀能反复命中缓存的负载,实际成本会比按官网价估算的低。具体的缓存读取价见上方价格表。

相关对比

我们的实测研究