Claude Fable 5 vs MiniMax M3
MiniMax M3 已從我們的目錄下架。下方是它最後公布的費率;它已經無法呼叫,這組比較裡的另一個模型則仍可呼叫。
Claude Fable 5 採邀請制。下方的數字是即時費率,但要先取得工作空間的授權才能呼叫;如果你打算依據這份比較來開發,請先向我們申請開通。
什麼情況選哪一個
兩種模型皆具備 1000000-token 的上下文視窗並接受文字與圖片輸入,因此真正的差異在於價格與形式:minimax-m3 的收費為輸入 $0.3 與輸出 $1.2,對比 claude-fable-5 的 $10 與 $50,大約便宜 33x 與 42x,且它還接受影片輸入、允許最高 524288 輸出 token,並允許關閉思考功能。當你想要 Anthropic 適用於對話、程式碼與工具使用的常駐推理模式且可接受較高費率時,請選擇 claude-fable-5;針對成本與可切換的思考功能更為重要的高用量、長上下文或影片工作,請選擇 minimax-m3。
Benchmark 成績
MiniMax M3:供應商沒有公布 benchmark 成績。
供應商公布: 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
定價
| Claude Fable 5 | MiniMax M3 | Δ | |
|---|---|---|---|
| 輸入 / 1M tokens | $10 | $0.3 | 33× |
| 輸出 / 1M tokens | $50 | $1.2 | 42× |
| 快取讀取 / 1M tokens | $1 | $0.06 | 17× |
| 快取寫入 | 1.25x (5m) / 2x (1h) | 不額外計費 | - |
費率取自網站建置時的即時目錄;各模型頁面都列有最新的價目。
兩者的相對位置:每 1M tokens 的輸入價格,涵蓋同一計費單位下全部 91 個聊天模型(對數尺度)
功能
| Claude Fable 5 | MiniMax M3 | |
|---|---|---|
| 工具使用 | 是 | 是 |
| 思考控制 | 一律開啟 | 可設定 |
| 結構化輸出 | 是 | - |
| 提示詞快取 | 顯式(由你標記前綴) | 隱式(自動) |
| 快取存活時間 | 5m default, 1h option | 未公布 |
| 最小快取前綴 | 512 個 token | 512 個 token |
規格
| Claude Fable 5 | MiniMax M3 | |
|---|---|---|
| 輸入模態 | 文字 圖像 | 文字 圖像 影片 |
| 輸出模態 | 文字 | 文字 |
| 發布日期 | 2026-06-09 | 2026-06-01 |
| 知識截止日期 | 2026-01 | - |
| 上下文視窗 | 1,000,000 | 1,000,000 |
| 最大輸出 | 128,000 | 524,288 |
| 思考參數 | output_config.effort (thinking.type is adaptive-only and needs no configuration) |
|
| 可接受的值 | effort
both "enabled" and "disabled" return 400 | thinking.type
reasoning_split
|
| 預設值 | 思考始終開啟(自適應);effort 為 high | 自適應:思考開啟,由模型判斷何時需要額外推理 |
規格摘錄自各供應商的文件;供應商沒有公布的項目就直接略過,不自行推測。 完整來源: Claude Fable 5 · MiniMax M3
同一段提示詞,兩個模型,經閘道實測
Claude Fable 5 通過 · 3 sentences
When we enabled reasoning, the model began generating extensive internal "thinking" tokens before each answer, and those tokens are billed as output even though users never see them. Output tokens typically cost several times more than input tokens, so adding thousands of hidden reasoning tokens per request effectively multiplied our per-query cost. In short, we're paying for a much longer response behind the scenes in exchange for higher answer quality, and we can manage this by tuning reasoning effort levels or reserving reasoning mode for complex tasks only.
輸出 228 tok 延遲 6.7 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 計量顯示出的隱藏思考計費落差。
Claude Fable 5 通過 · 8/8 cases
## Fixed code ```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 ``` ## Explanation The original function counts **adjacent equal pairs** rather than **items in a run**: a run of length *n* contains only *n − 1* equal neighbor pairs, so every result is off by one — a single-element list yields 0 instead of 1, and `[1, 2, 2]` yields 1 instead of 2 (which callers perceive as "missing" the run at the end). The fix is to initialize both `cur` and `best` to 1 (any nonempty list has a run of at least length 1), reset `cur` to 1 rather than 0 when
輸出 531 tok 延遲 12.5 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 效率。
Claude Fable 5 通過 · 5/5 fields, guidance null
```json { "company": "Meridian Robotics", "quarter": "Q3 (September quarter)", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null } ``` Notes on interpretation: "up eleven and change" is rendered as 11 (the precise figure isn't stated), and guidance is null because it was explicitly withheld.
輸出 192 tok 延遲 6.5 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),以及結構化輸出路徑的差異。
Claude Fable 5 通過 · 120 words, 0 banned, 1 question
**Introducing Cross-Provider Prompt Caching for our API Gateway** Starting today, your repeated prompts are cached once and reused across OpenAI, Anthropic, Google, and any other provider you route through the gateway. Instead of paying full token costs every time your application sends the same system prompt or context block, the gateway detects matching prefixes and serves cached results in milliseconds. Why keep spending money and latency on identical requests? Early adopters report cost reductions of up to 60 percent on high-volume workloads, along with faster median response times. Configuration is simple: enable caching in your dashboard, set a TTL, and choose which routes participate. Cache entries are encrypted at rest and never shared between accounts. Available now on all plans.
輸出 1173 tok 延遲 18.2 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,要改的只有醒目標示的那兩行。端點、金鑰和請求格式都不變。
from openai import OpenAI
client = OpenAI(
base_url="https://synthorai.io/v1",
api_key="sk-syn-...",
)
resp = client.chat.completions.create(
model="claude-fable-5",
# 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: "claude-fable-5",
// 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": "claude-fable-5",
# "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: "claude-fable-5",
// 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("claude-fable-5")
// .model("minimax-m3") // 取消這一行的註解,並把上一行註解掉
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));常見問題
Claude Fable 5 和 MiniMax M3 哪個比較便宜?
以「輸入 / 1M tokens」來看,MiniMax M3 比較便宜($0.3 對 $10,相差 33×)。其他項目的結果可能相反,完整價目請看上表;實際成本要看你的用量組合。
可以只串接一次,就對 Claude Fable 5 和 MiniMax M3 做 A/B 測試嗎?
可以。兩個模型都走同一個 OpenAI 相容端點,用的也是同一把 API 金鑰,切換時只要改一行裡的模型名稱字串。你可以把一部分流量分別導到兩邊,再直接比較帳單。
Claude Fable 5 與 MiniMax M3 支援提示詞快取嗎?
支援。兩者的快取讀取費率都低於輸入費率,所以前綴已經進快取的工作負載,實際成本會比官網價算出來的低。確切的快取讀取價格請見上方定價表。