Claude Fable 5.1 vs Claude Fable 5.2
Claude Fable 5.1 is served by invitation. Its figures below are the live rates, but calls need a workspace grant first; ask us for access before you build on this comparison.
Claude Fable 5.2 is served by invitation. Its figures below are the live rates, but calls need a workspace grant first; ask us for access before you build on this comparison.
Which one, when
These two share their shape: both take text and image in, return text, carry a 1000000-token context with 128000 max output and a 2026-06 knowledge cutoff, and keep thinking always on with no way to disable it. The difference is price: claude-fable-5-2 charges $8 input and $40 output per million tokens against $10 and $50 for claude-fable-5-1, and $0.2 per million cached input tokens against $0.25, a fifth less on every line. claude-fable-5-2 is also the newer release (2026-11-09), so move to it unless your integration is pinned to claude-fable-5-1.
Benchmarks
Claude Fable 5.2: the vendor has not published benchmark scores.
Vendor-published: 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 OpenAI OpenAI OpenAI OpenAI OpenAI OpenAI OpenAI Tencent Z.ai Z.ai Z.ai Z.ai
Pricing
| Claude Fable 5.1 | Claude Fable 5.2 | Δ | |
|---|---|---|---|
| Input / 1M tokens | $10 | $8 | 1.3× |
| Output / 1M tokens | $50 | $40 | 1.3× |
| Cache read / 1M tokens | $0.25 | $0.2 | 1.3× |
| Cache write | 1.25x (5m) / 2x (1h) | 1.25x (5m) / 2x (1h) | - |
Rates from the live catalogue at build time; each model page carries the current rate card.
Where they sit · input price per 1M tokens across all 86 chat models on this billing unit (log scale)
Capabilities
| Claude Fable 5.1 | Claude Fable 5.2 | |
|---|---|---|
| Tool calling | yes | yes |
| Thinking control | always on | always on |
| Structured output | yes | yes |
| Prompt caching | explicit (you mark the prefix) | explicit (you mark the prefix) |
| Cache lifetime | 5m default, 1h option | 5m default, 1h option |
| Minimum cached prefix | 512 tokens | 512 tokens |
Specs
| Claude Fable 5.1 | Claude Fable 5.2 | |
|---|---|---|
| Input modalities | text image | text image |
| Output modalities | text | text |
| Released | 2026-09-01 | 2026-11-09 |
| Knowledge cutoff | 2026-06 | 2026-06 |
| Context window | 1,000,000 | 1,000,000 |
| Max output | 128,000 | 128,000 |
| Thinking parameter | output_config.effort (thinking is adaptive-only and always on) | output_config.effort (thinking is adaptive-only and always on) |
| Accepted values | effort
| effort
both "enabled" and "disabled" return 400 |
| Default | thinking always on (adaptive) effort
| thinking always on (adaptive) effort
|
Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: Claude Fable 5.1 · Claude Fable 5.2
Switch between them with one line
Both ids are in every tab below; the highlighted pair of lines is the only edit. Same endpoint, same key, same request shape.
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="claude-fable-5-2", # uncomment this line, comment the one above
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: "claude-fable-5-2", // uncomment this line, comment the one above
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": "claude-fable-5-2", # uncomment this line, comment the one above
"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: "claude-fable-5-2", // uncomment this line, comment the one above
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("claude-fable-5-2") // uncomment this line, comment the one above
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));FAQ
Which is cheaper, Claude Fable 5.1 or Claude Fable 5.2?
Claude Fable 5.2 is cheaper on the "Input / 1M tokens" row ($8 vs $10, 1.3× apart). Other rows may point the other way; the table above carries the full rate card, and real cost depends on your mix.
Can I A/B test Claude Fable 5.1 against Claude Fable 5.2 without two integrations?
Yes. Both are served through the same OpenAI-compatible endpoint with one API key. Switching is a one-line change to the model id, so you can route a fraction of traffic to each and compare bills directly.
Do Claude Fable 5.1 and Claude Fable 5.2 support prompt caching?
Yes. Both bill cache reads below their input rate, so warm-prefix workloads cost less than the list rates suggest. The exact cache-read rows are in the pricing table above.