Claude Fable 5.1 vs GPT-6 Luna
Claude Fable 5.1 採邀請制提供服務。下方的數據為即時費率,但進行呼叫前需先取得工作區授權;在您基於此比較進行開發之前,請先向我們申請存取權限。
何時用哪一個
兩者皆接受文字與影像輸入並回傳文字,最大輸出限制為 128,000 token,且提供大約一百萬 token 的上下文(claude-fable-5-1 為 1,000,000,gpt-6-luna 為 1,050,000),因此真正的差異在於價格以及對思考功能的控制。gpt-6-luna 每百萬 token 成本為輸入 $0.1 與輸出 $0.5,對比後者的 $10 與 $50,兩端皆便宜了 100x,快取讀取為 $0.01 對比 $0.25,且其思考功能可以關閉,這適合高用量或對延遲敏感的工作。當您想要 Anthropic 常駐開啟的推理模式並願意為此付費時,請選擇 claude-fable-5-1。
Benchmark 成績
廠商公布: Alibaba (Qwen) Anthropic ByteDance DeepSeek Google MiniMax Moonshot OpenAI Tencent Z.ai
定價
| Claude Fable 5.1 | GPT-6 Luna | Δ | |
|---|---|---|---|
| 輸入 / 1M tokens | $10 | $0.1 | 100× |
| 輸出 / 1M tokens | $50 | $0.5 | 100× |
| 快取讀取 / 1M tokens | $0.25 | $0.01 | 25× |
| 快取寫入 | 1.25x (5m) / 2x (1h) | 不額外計費 | - |
費率取自建置時的即時目錄;各模型頁面皆附有目前的費率卡。
它們的相對位置 — 在此計費單位下,所有 74 個 聊天 模型的 每 1M tokens 的輸入價格(對數尺度)
能力
| Claude Fable 5.1 | GPT-6 Luna | |
|---|---|---|
| 工具使用 | 是 | 是 |
| 思考控制 | 常駐開啟 | 可配置 |
| 結構化輸出 | 是 | 是 |
| 提示快取 | 顯式(由您標記前綴) | 隱式(自動) |
| 快取生命週期 | 5m default, 1h option | 5-10m, up to 1h |
| 最小快取前綴 | 1024 個 token | 1024 個 token |
規格
| Claude Fable 5.1 | GPT-6 Luna | |
|---|---|---|
| 輸入模態 | 文字 影像 | 文字 影像 |
| 輸出模態 | 文字 | 文字 |
| 發布日期 | 2026-09-01 | 2026-09-22 |
| 知識截止日期 | 2026-06 | 2026-05 |
| 上下文視窗 | 1M | 1.1M |
| 最大輸出 | 128K | 128K |
| 思考參數 | output_config.effort (thinking is adaptive-only and always on) | reasoning.effort |
| 可接受的值 | effort
| reasoning.effort
|
| 預設值 | thinking always on (adaptive) effort
| medium |
規格摘錄自各供應商的文件;供應商未發布的資料列會直接省略,而非自行推測。 完整來源: Claude Fable 5.1 · GPT-6 Luna
單一提示詞,兩款模型 — 經由閘道測量
Claude Fable 5.1 通過 · 3 sentences
When we enabled reasoning, the model started generating a long chain of internal "thinking" tokens before producing each answer, and we're billed for those tokens at the same output rate even though users never see them. In practice, that hidden reasoning often runs several times longer than the visible response, so the total tokens per request roughly doubled while the number of requests stayed flat. The upside is measurably better accuracy on complex tasks, so the right conversation is whether that quality gain justifies the cost—and if not, we can restrict reasoning to the workflows that actually need it rather than turning it on globally.
輸出 186 tok 延遲 3.2 s
GPT-6 Luna 通過 · 3 sentences
Enabling reasoning typically makes the model process more information and generate more internal tokens before producing its answer. Because usage is billed by tokens—and reasoning may also route requests to a more expensive model—the cost per request can rise sharply. If request volume stayed similar, that higher cost per request could explain why the bill doubled.
輸出 117 tok (+48 思考) 延遲 3.4 s
指令遵循(恰好三句,可數)、受眾適配(面向 CFO 的語氣),以及下方 token 計量所暴露的隱藏思考計費缺口。
Claude Fable 5.1 通過 · 8/8 cases
```python def longest_run(xs): if not xs: return 0 best = cur = 1 for i in range(1, len(xs)): cur = cur + 1 if xs[i] == xs[i - 1] else 1 best = max(best, cur) return best ``` The bug is that `cur` counts *matches between adjacent elements* rather than *elements in the run*: it starts at 0 and only increments when `xs[i] == xs[i-1]`, so a run of length k produces a count of k−1. That's why a single element returns 0 instead of 1, and why every other run also comes out one short — the "misses runs at the end" reports are the same off-by-one seen on inputs like `[1, 2, 2]`, where the trailing run of length 2 is reported as 1 (the original code does update `best` inside the loop, so end-of-list runs aren't actually skipped, just undercounted). […]
輸出 882 tok (+507 思考) 延遲 3.4 s
GPT-6 Luna 通過 · 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 original code counted matching *adjacent pairs* rather than items, so a run of length `n` was reported as `n - 1`, and a single-item input returned `0`. This version counts the current item as part of each run and updates `best` at every index, including the last; it returns `0` for an empty input.
輸出 514 tok (+356 思考) 延遲 6.9 s
修復是否真的正確(可執行)、解釋的資訊密度,以及在一個邊界明確的任務上的 token 效率。
Claude Fable 5.1 通過 · 5/5 fields, guidance null
```json { "company": "Meridian Robotics", "quarter": "Q3 (September quarter)", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null } ``` Notes on judgment calls (not part of the object): - **revenue_usd_m**: The text says "412 for the topline" but never states the currency or that the figure is in millions; it's also on a constant-currency basis and prefaced with "call it," so it's approximate. If you want strict literalism, this should be `null`. - **growth_pct**: "Eleven and change" means slightly above 11%; the exact figure isn't given. - **quarter**: "September quarter" is Q3 on a calendar basis, consistent with the reference to a pending Q4 close. - **guidance**: Explicitly withheld, so `null`.
輸出 633 tok (+349 思考) 延遲 3.8 s
GPT-6 Luna 通過 · 5/5 fields, guidance "Withheld pending the Q4 close"
{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":null,"guidance":"Withheld pending the Q4 close"}
輸出 161 tok (+119 思考) 延遲 21.7 s
schema 服從度(不臆造欄位)、幻覺壓力(guidance 明確被暫緩給出),以及結構化輸出路徑的差異。
Claude Fable 5.1 通過 · 121 words, 0 banned, 1 question
**Introducing Cross-Provider Prompt Caching for the Gateway.** Starting today, your API gateway can cache prompts once and reuse them across OpenAI, Anthropic, Google, and any other provider you route to. Long system instructions, retrieval context, and few-shot examples are stored at the gateway layer, so switching models no longer means paying to resend the same tokens. Why send the same 8,000-token preamble to three different vendors when you could send it once? Our cache normalizes prompt segments, fingerprints them, and serves matching prefixes from memory before the request ever reaches an upstream API. Early customers report token costs falling by 30 to 60 percent on high-volume workloads, with median latency dropping alongside. Available today on all Team and Enterprise plans.
輸出 1722 tok (+1463 思考) 延遲 2.9 s
GPT-6 Luna 通過 · 120 words, 0 banned, 1 question
Introducing Prompt Cache, a new API gateway feature that recognizes repeat prompt prefixes and reuses provider-side cached context across supported models. Teams can route requests to different AI providers while preserving eligible cache hits, reducing redundant input processing and helping lower latency and token costs. Configure cache policies in one place, monitor hit rates by provider, and keep existing client integrations unchanged. The gateway applies provider-specific rules automatically, so developers do not need to build separate caching logic for each endpoint. Which workflows could benefit from faster responses and predictable spend? Prompt Cache is available today in preview for eligible accounts, with usage details, supported providers, and setup guidance in the dashboard. Start with one route, compare results, then expand.
輸出 959 tok (+813 思考) 延遲 14.6 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-1",
# model="gpt-6-luna", # 取消註解此行,並註解上一行
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-1",
// model: "gpt-6-luna", // 取消註解此行,並註解上一行
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-1",
# "model": "gpt-6-luna", # 取消註解此行,並註解上一行
"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-1",
// Model: "gpt-6-luna", // 取消註解此行,並註解上一行
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-1")
// .model("gpt-6-luna") // 取消註解此行,並註解上一行
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));常見問題
Claude Fable 5.1 和 GPT-6 Luna 哪個比較便宜?
GPT-6 Luna 在 輸入 / 1m tokens 上較便宜($0.1 對比 $10,相差 100×)。其他項目可能呈現相反結果 — 上表提供完整資訊,實際成本取決於您的使用組合。
我可以在不進行兩次整合的情況下,對 Claude Fable 5.1 和 GPT-6 Luna 進行 A/B 測試嗎?
可以。兩者皆透過同一個相容 OpenAI 的端點提供服務,並使用同一把 API 金鑰 — 切換只需更改一行的模型字串,因此您可以將部分流量分別導向兩者並直接比較帳單。
Claude Fable 5.1 與 GPT-6 Luna 支援提示快取嗎?
是的 — 兩者的快取讀取費率皆低於其輸入費率,因此具有暖前綴的工作負載成本會低於牌價所示。確切的快取讀取列請見上方的定價表。