DeepSeek V4 Pro (0813) vs Qwen3.8 Flash
何時用哪一個
兩款模型皆具備 1000000 token 的上下文視窗,並涵蓋聊天、程式碼、推理與工具,因此真正的差異在於價格、輸出長度與輸入:deepseek-v4-pro-0813 每百萬輸入收取 $1.32,每百萬輸出收取 $3.96,大約是 qwen3.8-flash($0.15 與 $0.47)的 8.8x 與 8.4x。當您需要極長的單次回覆時(高達 393216 token 對比 131072),請選擇 deepseek-v4-pro-0813。對於大量的文字工作、圖像與影片輸入,或者當您想在較簡單的呼叫中停用思考時,請選擇 qwen3.8-flash。
Benchmark 成績
廠商公布: Alibaba (Qwen) Anthropic ByteDance DeepSeek Google MiniMax Moonshot OpenAI Tencent Z.ai
定價
| DeepSeek V4 Pro (0813) | Qwen3.8 Flash | Δ | |
|---|---|---|---|
| 輸入 / 1M tokens | $1.32 | $0.15 | 8.8× |
| 輸出 / 1M tokens | $3.96 | $0.47 | 8.4× |
| 快取讀取 / 1M tokens | $0.132 | $0.016 | 8.3× |
| 快取寫入 | 不額外計費 | 1.25x | - |
費率取自建置時的即時目錄;各模型頁面皆附有目前的費率卡。
它們的相對位置 — 在此計費單位下,所有 71 個 聊天 模型的 每 1M tokens 的輸入價格(對數尺度)
能力
| DeepSeek V4 Pro (0813) | Qwen3.8 Flash | |
|---|---|---|
| 工具使用 | 是 | 是 |
| 思考控制 | 常駐開啟 | 可配置 |
| 結構化輸出 | 是 | 是 |
| 提示快取 | 隱式(自動) | 隱式 + 顯式 |
| 快取生命週期 | no fixed TTL (evicted when unused) | explicit: 5m, reset on hit |
| 最小快取前綴 | 未公開 | 1024 個 token |
規格
| DeepSeek V4 Pro (0813) | Qwen3.8 Flash | |
|---|---|---|
| 輸入模態 | 文字 | 文字 影像 影片 |
| 輸出模態 | 文字 | 文字 |
| 發布日期 | 2026-08-13 | 2026-08-27 |
| 上下文視窗 | 1M | 1M |
| 最大輸出 | 393K | 131K |
| 思考參數 | reasoning_effort |
|
| 可接受的值 | reasoning_effort
| enable_thinking
thinking_budget
preserve_thinking
|
| 預設值 | - | on qwen3.8-flash is hybrid thinking with thinking enabled by default, thinking_budget defaults to the 262,144-token chain maximum, and preserve_thinking is off |
規格摘錄自各供應商的文件;供應商未發布的資料列會直接省略,而非自行推測。 完整來源: DeepSeek V4 Pro (0813) · Qwen3.8 Flash
單一提示詞,兩款模型 — 經由閘道測量
DeepSeek V4 Pro (0813) 通過 · 3 sentences
Enabling reasoning causes the model to generate a hidden chain-of-thought with many additional tokens before producing the final answer, which sharply increases compute consumption per request. Those extra reasoning tokens are billed at the same or higher rates, so total usage doubled even though the volume of final outputs stayed similar. We can control this by adjusting reasoning effort, setting token limits, or routing only complex requests through reasoning mode.
輸出 308 tok (+226 思考) 延遲 5.1 s
Qwen3.8 Flash 通過 · 3 sentences
Enabling reasoning makes the model spend additional output tokens to plan and validate answers before responding, and those tokens are billed. It also increases compute and latency per request, so each task consumes more capacity than a non-reasoning call. As a result, billable tokens and compute roughly doubled, directly driving the higher invoice.
輸出 330 tok (+262 思考) 延遲 8.9 s
指令遵循(恰好三句,可數)、受眾適配(面向 CFO 的語氣),以及下方 token 計量所暴露的隱藏思考計費缺口。
DeepSeek V4 Pro (0813) 通過 · 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 else: cur = 1 best = max(best, cur) return best ``` The bug is that `cur` was initialized to `0` and only counted adjacent matching pairs, so a run of length `n` produced `n - 1` (or `0` for a single element) instead of `n`. The code also reset to `0` on a change, when the new run should start at length `1`. Initializing `cur` and `best` to `1` fixes both the single-element case and runs ending at the last index.
輸出 1315 tok (+1130 思考) 延遲 16.9 s
Qwen3.8 Flash 通過 · 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 else: cur = 1 best = max(best, cur) return best ``` The bug is that the original version counts adjacent equal pairs rather than items in a run, starting both `cur` and `best` at `0`, and it resets `cur` to `0` after a mismatch, thereby discarding the first element of the new run. That makes single-element inputs return `0`, and because every run is effectively measured in “steps” between equal elements, the last element is not counted—particularly noticeable when the longest run ends at the final index.
輸出 2123 tok (+1933 思考) 延遲 43.8 s
修復是否真的正確(可執行)、解釋的資訊密度,以及在一個邊界明確的任務上的 token 效率。
DeepSeek V4 Pro (0813) 通過 · 5/5 fields, guidance null
{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":11.0,"guidance":null}
輸出 2155 tok (+2121 思考) 延遲 26.0 s
Qwen3.8 Flash 通過 · 5/5 fields, guidance null
{ "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null }
輸出 519 tok (+463 思考) 延遲 10.5 s
schema 服從度(不臆造欄位)、幻覺壓力(guidance 明確被暫緩給出),以及結構化輸出路徑的差異。
DeepSeek V4 Pro (0813) 通過 · 121 words, 0 banned, 1 question
Introducing cross-provider prompt caching in our API gateway. Send a prompt once, and the gateway stores its computed prefix across Anthropic, OpenAI, and other LLM providers. Subsequent requests with the same prompt hit the cache, cutting latency and token costs while keeping outputs consistent across routing decisions and provider failovers. Teams can route identical prompts between providers without reprocessing shared context or lengthy system instructions. How much could you save on repeated prompt prefixes? The cache respects provider-specific key formats, handles TTLs automatically, and works with streaming and batch requests. Enable it with one configuration flag—no changes to your application code. Available today on all plans. Monitor cache hit rates, token savings, and provider-specific performance metrics in the live dashboard.
輸出 2845 tok (+2694 思考) 延遲 25.5 s
Qwen3.8 Flash 通過 · 120 words, 0 banned, 1 question
We are announcing prompt caching across providers in our API gateway. Store approved prompt outputs once and reuse them across supported model providers, cutting latency, cost, and duplicate token spend. The feature matches identical requests, checks validity, and returns cached results while preserving routing controls. Developers keep existing endpoints; the gateway manages storage, invalidation, and provider differences. This reduces noisy repeat calls, improves steady responses, and frees teams to focus on better agent workflows. OpenAI, Anthropic, Google, Mistral, and custom routes are supported. Cache hits appear in analytics with latency, token, and cost reductions visible. Check retention and privacy rules before enabling it. Ready to add cache controls to your gateway? Enable it in settings and watch spend drop now.
輸出 5958 tok (+5805 思考) 延遲 88.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="deepseek-v4-pro-0813",
# model="qwen3.8-flash", # 取消註解此行,並註解上一行
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: "deepseek-v4-pro-0813",
// model: "qwen3.8-flash", // 取消註解此行,並註解上一行
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": "deepseek-v4-pro-0813",
# "model": "qwen3.8-flash", # 取消註解此行,並註解上一行
"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: "deepseek-v4-pro-0813",
// Model: "qwen3.8-flash", // 取消註解此行,並註解上一行
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("deepseek-v4-pro-0813")
// .model("qwen3.8-flash") // 取消註解此行,並註解上一行
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));常見問題
DeepSeek V4 Pro (0813) 和 Qwen3.8 Flash 哪個比較便宜?
Qwen3.8 Flash 在 輸入 / 1m tokens 上較便宜($0.15 對比 $1.32,相差 8.8×)。其他項目可能呈現相反結果 — 上表提供完整資訊,實際成本取決於您的使用組合。
我可以在不進行兩次整合的情況下,對 DeepSeek V4 Pro (0813) 和 Qwen3.8 Flash 進行 A/B 測試嗎?
可以。兩者皆透過同一個相容 OpenAI 的端點提供服務,並使用同一把 API 金鑰 — 切換只需更改一行的模型字串,因此您可以將部分流量分別導向兩者並直接比較帳單。
DeepSeek V4 Pro (0813) 與 Qwen3.8 Flash 支援提示快取嗎?
是的 — 兩者的快取讀取費率皆低於其輸入費率,因此具有暖前綴的工作負載成本會低於牌價所示。確切的快取讀取列請見上方的定價表。