GLM-5.1 vs Qwen3.7 Plus
什麼情況選哪一個
兩者都是輸出文字的推理模型，帶工具、程式碼和可選思考，所以差別主要在價格、脈絡和輸入：qwen3.7-plus 輸入 $0.4、輸出 $1.6，對比 glm-5.1 的 $1.4 和 $4.4，即 Z.ai 這款每輸入 token 貴 3.5 倍、每輸出 token 貴 2.75 倍；而且它還帶 1000000 token 視窗（是 glm-5.1 的 200000 的 5 倍）以及影像和視訊輸入。低成本大批量工作、超大文件，或任何帶影像或視訊的任務選 qwen3.7-plus；需要單次回覆超過 65536 token 時選 glm-5.1，它允許最多 131072。
Benchmark 成績
GLM-5.1：供應商沒有公布 benchmark 成績。
供應商公布： Alibaba (Qwen) Anthropic ByteDance DeepSeek Google MiniMax Moonshot OpenAI Tencent Z.ai
定價
| GLM-5.1 | Qwen3.7 Plus | Δ | |
|---|---|---|---|
| 輸入 / 1M tokens | $1.4 | $0.4 | 3.5× |
| 輸出 / 1M tokens | $4.4 | $1.6 | 2.8× |
| 快取讀取 / 1M tokens | $0.26 | $0.08 | 3.3× |
| 快取寫入 | - | 1.25x | - |
費率取自網站建置時的即時目錄；各模型頁面都列有最新的價目。
兩者的相對位置：每 1M tokens 的輸入價格，涵蓋同一計費單位下全部 76 個聊天模型（對數尺度）
功能
| GLM-5.1 | Qwen3.7 Plus | |
|---|---|---|
| 工具使用 | 是 | 是 |
| 思考控制 | 可設定 | 可設定 |
| 結構化輸出 | 是 | 是 |
| 提示詞快取 | 隱式（自動） | 隱式 + 顯式 |
| 快取存活時間 | 未公布 | explicit: 5m, reset on hit |
| 最小快取前綴 | 未公布 | 1024 個 token |
規格
| GLM-5.1 | Qwen3.7 Plus | |
|---|---|---|
| 輸入模態 | 文字 | 文字 圖像 影片 |
| 輸出模態 | 文字 | 文字 |
| 發布日期 | 2026-04-07 | 2026-06-01 |
| 上下文視窗 | 200K | 1M |
| 最大輸出 | 131K | 66K |
| 思考參數 | thinking.type |
|
| 可接受的值 | thinking.type
| enable_thinking
thinking_budget
preserve_thinking
|
| 預設值 | enabled, and the model automatically determines whether to think | on the Qwen3.7 Plus series is hybrid thinking with thinking enabled by default, and preserve_thinking is off |
規格摘錄自各供應商的文件；供應商沒有公布的項目就直接略過，不自行推測。 完整來源： GLM-5.1 · Qwen3.7 Plus
同一段提示詞，兩個模型，經閘道實測
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
Qwen3.7 Plus 通過 · 3 sentences
Enabling reasoning requires the model to generate extensive internal "thinking" tokens to process complex logic before delivering a final answer. Because our vendor charges us per token consumed, this hidden computational overhead effectively doubles our output volume for the exact same number of user requests. Consequently, our costs have doubled because we are now paying for the model's increased processing time to achieve higher-quality, more accurate results.
輸出 1428 tok (+1345 思考) 延遲 25.2 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
Qwen3.7 Plus 通過 · 8/8 cases
## Fixed Code ```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 else: cur = 1 best = max(best, cur) return best ``` ## Bug Explanation The function has two related bugs rooted in how it counts run lengths. First, `cur` is initialized to `0` and only incremented on matches, so it counts the number of *transitions* between equal elements rather than the total elements in the run—a run of N identical items only reaches `cur = N − 1`, undercounting by one. This also causes the single-element case to return `0`, since the loop never executes and `cur` never increments. […]
輸出 2317 tok (+2005 思考) 延遲 40.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
Qwen3.7 Plus 通過 · 5/5 fields, guidance null
{ "company": "Meridian Robotics", "quarter": "September", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null }
輸出 1807 tok (+1750 思考) 延遲 31.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
Qwen3.7 Plus 通過 · 120 words, 0 banned, 1 question
Introducing PromptCache, our new API gateway feature designed to store and reuse prompts across multiple artificial intelligence providers. Have you ever noticed how repeatedly sending identical queries drains your budget and increases latency? PromptCache solves this by intelligently storing responses at the gateway level. When your application requests the same prompt from a different provider, the system instantly returns the cached result. This drastically reduces API costs and accelerates response times for your users. You can configure custom expiration times and set specific fallback rules for each vendor. You must stop paying twice for the exact same computation. Please upgrade your entire infrastructure today and experience much faster and cheaper integrations without changing a single line of your application code.
輸出 4453 tok (+4312 思考) 延遲 76.8 s
是否遵守限制（字數上限、禁用詞清單、只能有一句問句）、文字風格的特徵，以及長度控制。
改一行程式碼就能在兩者之間切換
下面每個頁籤都列了這兩個模型 ID，要改的只有醒目標示的那兩行。端點、金鑰和請求格式都不變。
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="qwen3.7-plus", # 取消這一行的註解，並把上一行註解掉
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: "qwen3.7-plus", // 取消這一行的註解，並把上一行註解掉
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": "qwen3.7-plus", # 取消這一行的註解，並把上一行註解掉
"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: "qwen3.7-plus", // 取消這一行的註解，並把上一行註解掉
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("qwen3.7-plus") // 取消這一行的註解，並把上一行註解掉
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));常見問題
GLM-5.1 和 Qwen3.7 Plus 哪個比較便宜？
以「輸入 / 1M tokens」來看，Qwen3.7 Plus 比較便宜（$0.4 對 $1.4，相差 3.5×）。其他項目的結果可能相反，完整價目請看上表；實際成本要看你的用量組合。
可以只串接一次，就對 GLM-5.1 和 Qwen3.7 Plus 做 A/B 測試嗎？
可以。兩個模型都走同一個 OpenAI 相容端點，用的也是同一把 API 金鑰，切換時只要改一行裡的模型名稱字串。你可以把一部分流量分別導到兩邊，再直接比較帳單。
GLM-5.1 與 Qwen3.7 Plus 支援提示詞快取嗎？
支援。兩者的快取讀取費率都低於輸入費率，所以前綴已經進快取的工作負載，實際成本會比官網價算出來的低。確切的快取讀取價格請見上方定價表。