Claude Fable 5 vs MiniMax M3

MiniMax M3 has been retired from our catalogue. Its figures below are the last published rates; calls to it are no longer served, while the other model in this comparison is.

Claude Fable 5 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.

vs

Which one, when

Both models share a 1000000-token context window and accept text and image input, so the real split is price and shape: minimax-m3 charges $0.3 input and $1.2 output against $10 and $50 for claude-fable-5, roughly 33x and 42x cheaper, and it also takes video input, allows up to 524288 output tokens, and lets thinking be switched off. Pick claude-fable-5 when you want Anthropic's always-on reasoning mode for chat, code and tool use and the higher rate is acceptable; pick minimax-m3 for high-volume, long-context or video work where cost and toggleable thinking matter more.

Benchmarks

MiniMax M3: the vendor has not published benchmark scores.

Above averageNo peer higherClaude Fable 586 / 9740 / 97
Claude Fable 5 MiniMax M3 other models measured peer average ★ no peer scored higher
SWE-Bench Pro
no peer scored higher 80.3%
N/A
BioMysteryBench hard
46.5%
N/A
OSWorld-Verified
no peer scored higher 85%
N/A
Cybergym
83.1%
N/A
HealthBench Professional
60.9%
N/A
Finance Agent v2
56.3%
N/A
Harvey Lab-AA
93.6%
N/A
GPQA Diamond
92.6%
N/A
Blueprint-Bench 2
38.6%
N/A
BrowseComp
87.4%
N/A
CharXiv (RQ) reasoning
no peer scored higher 88.9%
N/A

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 Moonshot OpenAI OpenAI OpenAI OpenAI OpenAI OpenAI OpenAI Tencent Z.ai Z.ai Z.ai Z.ai

Pricing

Claude Fable 5 MiniMax M3 Δ
Input / 1M tokens $10 $0.3 33×
Output / 1M tokens $50 $1.2 42×
Cache read / 1M tokens $1 $0.06 17×
Cache write 1.25x (5m) / 2x (1h) no separate charge -

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 91 chat models on this billing unit (log scale)

Claude Fable 5 · $10 MiniMax M3 · $0.3
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

Capabilities

Claude Fable 5 MiniMax M3
Tool calling yes yes
Thinking control always on configurable
Structured output yes -
Prompt caching explicit (you mark the prefix) implicit (automatic)
Cache lifetime 5m default, 1h option not published
Minimum cached prefix 512 tokens 512 tokens

Specs

Claude Fable 5 MiniMax M3
Input modalities text image text image video
Output modalities text text
Released 2026-06-09 2026-06-01
Knowledge cutoff 2026-01 -
Context window 1,000,000 1,000,000
Max output 128,000 524,288
Thinking parameter output_config.effort (thinking.type is adaptive-only and needs no configuration)
  • thinking.type
  • reasoning_split
Accepted values
effort
  • low
  • medium
  • high
  • xhigh
  • max

both "enabled" and "disabled" return 400

thinking.type
  • adaptive
  • disabled
reasoning_split
  • boolean
Default

thinking always on (adaptive)

effort
  • high
adaptive: thinking on, with the model deciding when extra reasoning helps

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 · MiniMax M3

One prompt, both models, measured through the gateway

PROMPT Explain to a CFO, in exactly three sentences, why our LLM bill doubled after we enabled reasoning. CHECK exactly 3 sentences

Claude Fable 5 passed · 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.

out 228 tok latency 6.7 s

MiniMax M3 passed · 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.

out 764 tok (+629 thinking) latency 3.5 s

Instruction following (exactly three sentences, so countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.

PROMPT This function is supposed to return the longest run of consecutive equal items, but callers report it is off by one on single-element inputs and misses runs that end at the last index. Fix it and explain the bug in one paragraph. CHECK fix passes tests

Claude Fable 5 passed · 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

out 531 tok latency 12.5 s

MiniMax M3 passed · 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.

out 845 tok (+596 thinking) latency 3.5 s

Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.

PROMPT Extract a JSON object with fields {company, quarter, revenue_usd_m, growth_pct, guidance} from this text. Use null for anything not stated; add no other fields. CHECK valid JSON, schema exact

Claude Fable 5 passed · 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.

out 192 tok latency 6.5 s

MiniMax M3 passed · 5/5 fields, guidance null

```json { "company": null, "quarter": "Q3", "revenue_usd_m": 412, "growth_pct": null, "guidance": null } ```

out 1002 tok (+955 thinking) latency 3.6 s

Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.

PROMPT Write a 120-word product announcement for an API gateway feature that caches prompts across providers. Forbidden words: "seamless", "unlock", "game-changer", "revolutionize", "empower". Exactly one sentence must be a question. CHECK 120 words, 0 banned words

Claude Fable 5 passed · 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.

out 1173 tok latency 18.2 s

MiniMax M3 passed · 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.

out 2808 tok (+2656 thinking) latency 6.0 s

Constraint obedience (word budget, banned-word list, the single question), style fingerprint, and length control.

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",
    # model="minimax-m3",  # uncomment this line, comment the one above
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

Get your API key →

FAQ

Which is cheaper, Claude Fable 5 or MiniMax M3?

MiniMax M3 is cheaper on the "Input / 1M tokens" row ($0.3 vs $10, 33× 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 against MiniMax M3 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 and MiniMax M3 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.

Related comparisons

From our measured studies