90 days of the enterprise, pro and team plans free, no card needed. See the plans
Model comparison
Anthropic's Claude Fable 5.1 against Anthropic's Claude Opus 5.5: vendor list prices, limits, abilities and the Artificial Analysis indexes side by side - and what OpenSmartRoute does when both are available.
Claude Opus 5.5 lists at $8.00 per million tokens blended against $20 for Claude Fable 5.1 - 2.5x less.
Claude Opus 5.5 scores 58 on the intelligence index against 53 - 4 points apart.
Vendor list prices per million tokens and published limits; indexes are Artificial Analysis composites (0-100).
| Specification | Claude Fable 5.1 | Claude Opus 5.5 |
|---|---|---|
| Input price / 1M tokens | $10.0 | $4.00 |
| Output price / 1M tokens | $50.0 | $20.0 |
| Blended (3 in : 1 out) | $20.0 | $8.00 |
| Cached input / 1M | $0.25 | $0.20 |
| Context window | 1M | 1M |
| Max output | 128K | 128K |
| Input | text, image, file | text, image, file |
| Output | text | text |
| Tool calls | ||
| Structured output | ||
| Reasoning | ||
| Open weights | ||
| Intelligence index | 53 | 58 |
| Coding index | 82 | - |
| Agentic index | 58 | - |
| Released | Sep 1, 2026 | Sep 22, 2026 |
| Available on this deployment |
List price times tokens for three typical workloads; your mix of input and output decides which model's pricing suits you.
| Workload | Claude Fable 5.1 | Claude Opus 5.5 | Difference |
|---|---|---|---|
| Support chat20M tokens in, 5M out a month - a help desk answering a few thousand conversations. | $450 | $180 | $270 less on Claude Opus 5.5 |
| Document summaries100M in, 5M out - long inputs, short answers. | $1,250 | $500 | $750 less on Claude Opus 5.5 |
| Coding assistant60M in, 20M out - a team's editor assistant, output-heavy. | $1,600 | $640 | $960 less on Claude Opus 5.5 |
Claude Opus 5.5 is both cheaper and stronger on the intelligence index, so with both in the catalogue the router sends it almost everything; Claude Fable 5.1 earns a request only on something it alone offers - a longer context, a modality, a data boundary or a region your rules require.
# targets.yaml - both models as routing targets (metadata.model links each to the catalogue entry)
targets:
- { id: claude-opus-5.5, kind: llm, metadata: { model: anthropic/claude-opus-5.5 } }
- { id: claude-fable-5.1, kind: llm, metadata: { model: anthropic/claude-fable-5.1 } }
# rules.yaml - the cheaper model by default, the stronger one when the request is hard
rules:
- name: simple-requests-stay-cheap
when: { max_complexity: 0.45 }
prefer: [claude-opus-5.5]
weight: 0.8
- name: hard-requests-escalate
when: { min_complexity: 0.45 }
prefer: [claude-fable-5.1]
weight: 0.8Every Anthropic and Anthropic model, with prices, is on the vendor pages; the rankings show what the router actually picks.