GLM-5.1 vs MiniMax M3
MiniMax M3 已从我们的目录下线。下方是它最后公布的价格;这个模型已无法调用,对比中的另一个模型仍可正常调用。
什么时候选哪个
纸面上 minimax-m3 更宽也更便宜:1000000 token 上下文对 200000、524288 最大输出 token 对 131072、在文本之外接受图像和视频输入,输入价格约低 4.7 倍、输出约低 3.7 倍(每百万 $0.3/$1.2 对 $1.4/$4.4)。超大文档、超长生成,或任何带图像或视频的请求选 minimax-m3;专门想要 Z.ai 的文本模型且 200000 token 窗口够用时选 glm-5.1。两者都覆盖对话、代码、推理、工具和长上下文,也都可以关闭思考。
价格
| GLM-5.1 | MiniMax M3 | Δ | |
|---|---|---|---|
| 输入 / 1M token | $1.4 | $0.3 | 4.7× |
| 输出 / 1M token | $4.4 | $1.2 | 3.7× |
| 缓存读取 / 1M token | $0.26 | $0.06 | 4.3× |
| 缓存写入 | - | 不单独收费 | - |
价格取自构建时的实时目录,最新价格见各模型页面。
两个模型所处的位置:全部 91 个按同一单位计费的聊天模型的每 1M token 输入价分布(对数刻度)
能力
| GLM-5.1 | MiniMax M3 | |
|---|---|---|
| 工具调用 | 是 | 是 |
| 思考控制 | 可配置 | 可配置 |
| 结构化输出 | 是 | - |
| 提示词缓存 | 隐式(自动) | 隐式(自动) |
| 缓存有效期 | 未公布 | 未公布 |
| 最小缓存前缀 | 未公布 | 512 个 token |
规格
| GLM-5.1 | MiniMax M3 | |
|---|---|---|
| 输入模态 | 文本 | 文本 图像 视频 |
| 输出模态 | 文本 | 文本 |
| 发布日期 | 2026-04-07 | 2026-06-01 |
| 上下文窗口 | 200,000 | 1,000,000 |
| 最大输出 | 131,072 | 524,288 |
| 思考参数 | thinking.type |
|
| 可选值 | thinking.type
| thinking.type
reasoning_split
|
| 默认值 | enabled,由模型自动判断是否思考 | adaptive:思考开启,由模型判断何时需要额外推理 |
规格照录自各供应商的文档;供应商没有公布的项目,对应的行直接省略,不做推断。 完整来源: GLM-5.1 · MiniMax M3
同一条提示词,两个模型,经网关实测
GLM-5.1 通过 · 3 sentences
Enabling reasoning shifts the LLM from generating quick answers to producing hidden "chain-of-thought" tokens that systematically explore multiple solution paths before responding. Because billing is based on total tokens processed, these invisible reasoning tokens drastically increase input and output volume per query, often adding thousands of compute-intensive tokens to a single prompt. Consequently, our bill doubled not from higher per-token rates or increased user volume, but from the exponentially deeper computational work required to deliver higher-quality, more reliable outputs.
输出 98 tok 延迟 7.8 s
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
指令遵循(恰好三句,数得出来)、受众适配(对 CFO 说话的口吻),以及下方 token 计数暴露出的隐藏思考计费差额。
GLM-5.1 通过 · 8/8 cases
```python def longest_run(xs): if not xs: return 0 best = 1 cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 best = max(best, cur) else: cur = 1 return best ``` **Explanation:** The original function initialized `cur` and `best` to `0` and only incremented `cur` when a duplicate was found. This counts the number of *extra* equal items in a run rather than the total run length, so every run is reported as one shorter than it actually is—returning `0` for single-element lists and `L-1` for a run of length `L` (including those ending at the last index). The fix initializes `cur` and `best` to `1` (when the list is non‑empty) and resets `cur` to `1` on a mismatch, so `cur` tracks the full length of the current run and `best` records the true maximum.
输出 3823 tok (+3585 思考) 延迟 49.7 s
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
修复是否真的正确(能运行)、解释的信息密度,以及在一个范围明确的任务上的 token 效率。
GLM-5.1 通过 · 5/5 fields, guidance "withheld pending the Q4 close"
```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": "eleven and change", "guidance": "withheld pending the Q4 close" } ```
输出 1091 tok (+1028 思考) 延迟 15.2 s
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
是否严守 schema(不臆造字段)、能否顶住幻觉压力(原文明说暂不给出 guidance),以及结构化输出路径的差异。
GLM-5.1 通过 · 120 words, 0 banned, 1 question
We are excited to introduce Prompt Cache for our API Gateway. This new feature stores responses for identical prompts, routing subsequent requests directly to the cache instead of calling the underlying AI provider. Are you tired of paying multiple times for the exact same query? Prompt Cache solves this by recognizing duplicate inputs across all supported providers, drastically reducing latency and operational costs. When a user submits a request that matches a previously cached prompt, the gateway returns the stored answer instantly. You can configure cache expiration and scope rules via your dashboard to maintain data freshness. Stop wasting budget on redundant computational work. Upgrade to the latest gateway tier today to start saving time and money on every call.
输出 3935 tok (+3802 思考) 延迟 41.1 s
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
是否守住约束(字数预算、禁用词表、只能有一个问句)、文风特征,以及长度控制。
改一行代码就能在两个模型之间切换
下方每个标签页里都有两个模型 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="glm-5.1",
# model="minimax-m3", # 取消注释此行,注释上一行
messages=[{"role": "user", "content": "Summarize this diff"}],
reasoning_effort="medium",
)
print(resp.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://synthorai.io/v1",
apiKey: "sk-syn-...",
});
const resp = await client.chat.completions.create({
model: "glm-5.1",
// model: "minimax-m3", // 取消注释此行,注释上一行
messages: [{ role: "user", content: "Summarize this diff" }],
reasoning_effort: "medium",
});
console.log(resp.choices[0].message.content);curl https://synthorai.io/v1/chat/completions \
-H "Authorization: Bearer sk-syn-..." \
-H "Content-Type: application/json" \
-d '{
"model": "glm-5.1",
# "model": "minimax-m3", # 取消注释此行,注释上一行
"messages": [{"role": "user", "content": "Hello"}],
"reasoning_effort": "medium"
}'package main
import (
"context"
"fmt"
"github.com/openai/openai-go/v3"
"github.com/openai/openai-go/v3/option"
)
func main() {
client := openai.NewClient(
option.WithBaseURL("https://synthorai.io/v1"),
option.WithAPIKey("sk-syn-..."),
)
resp, _ := client.Chat.Completions.New(context.TODO(), openai.ChatCompletionNewParams{
Model: "glm-5.1",
// Model: "minimax-m3", // 取消注释此行,注释上一行
Messages: []openai.ChatCompletionMessageParamUnion{
openai.UserMessage("Summarize this diff"),
},
ReasoningEffort: openai.ReasoningEffortMedium,
})
fmt.Println(resp.Choices[0].Message.Content)
}import com.openai.client.OpenAIClient;
import com.openai.client.okhttp.OpenAIOkHttpClient;
import com.openai.models.chat.completions.*;
import com.openai.models.ReasoningEffort;
OpenAIClient client = OpenAIOkHttpClient.builder()
.baseUrl("https://synthorai.io/v1")
.apiKey("sk-syn-...")
.build();
ChatCompletion resp = client.chat().completions().create(
ChatCompletionCreateParams.builder()
.model("glm-5.1")
// .model("minimax-m3") // 取消注释此行,注释上一行
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));常见问题
GLM-5.1 和 MiniMax M3 哪个更便宜?
按「输入 / 1M token」算,MiniMax M3 更便宜($0.3 对 $1.4,相差 4.7×)。其他计费项的结论可能相反,完整价格见上方表格,实际成本取决于你的用量构成。
不用分别集成两次,就能对 GLM-5.1 和 MiniMax M3 做 A/B 测试吗?
可以。两个模型走同一个 OpenAI 兼容端点,用同一个 API key,切换时只要改一行里的模型名,所以可以给两个模型各分一部分流量,直接对比账单。
GLM-5.1 和 MiniMax M3 支持提示词缓存吗?
支持。两个模型的缓存读取价都低于各自的输入价,所以前缀能反复命中缓存的负载,实际成本会比按官网价估算的低。具体的缓存读取价见上方价格表。