Model comparison

Claude Fable 5 vs Ember-1

Pricing, context window and real answers (September 2026)

Claude Fable 5 (Anthropic) and Ember-1 (Fireworks), compared as you can actually call them on FastMetal. Both are served from the same OpenAI-compatible endpoint and API key; switching is a change to the model string.

Specs and pricing

anthropic logoClaude Fable 5Ember-1
ProviderAnthropicFireworks
Input (per 1M tokens)¥1,787¥536.1
Output (per 1M tokens)¥8,935¥2,680.5
Typical cost (1,000 in + 500 out tokens × 1,000 calls)¥6,255¥1,876
Context window1,000,000 tokens1,048,576 tokens
Release date6/9/20269/24/2026
Input modalitiestext, image, filetext, image
Throughput (p50)——
Arena · overall#1 · ELO 1,506Unranked
Arena · Japanese#1 · ELO 1,523Unranked
Arena · coding#1 · ELO 1,552Unranked

Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.

Which should you pick?

  • On price, Ember-1: ¥2,680.5 per 1M output tokens, 70% less than Claude Fable 5.
  • For long documents, Ember-1: a 1,048,576-token context window against 1,000,000 for Claude Fable 5.
  • If in doubt, try both on the same key. Switching is a change to the model string, and each is billed at its own rate.

Real answers to the same prompts

Exactly what the FastMetal gateway returned, side by side. Not benchmark scores: actual output.

Count the number of 'r's in 'strawberry'

Count the number of 'r's in 'strawberry'. Explain your reasoning step by step.

Claude Fable 5

# Counting 'r's in "strawberry" Let me spell out the word letter by letter and check each one: | Position | Letter | Is it 'r'? | |----------|--------|------------| | 1 | s | No | | 2 | t | No | | 3 | **r** | ✅ Yes (1st) | | 4 | a | No | | 5 | w | No | | 6 | b | No | | 7 | e | No | | 8 | **r** | ✅ Yes (2nd) | | 9 | **r** | ✅ Yes (3rd) | | 10 | y | No | ## Reasoning breakdown: - The word "strawberry" can be split into two parts: **straw** + **berry** - "straw" contains one 'r': st**r**aw - "berry" contains two 'r's: be**rr**y (a double-r) ## Answer: **3** There are **three 'r's** in "strawberry."
39.6s354 output tokens

Ember-1

# Counting the 'r's in "strawberry" **Step 1: Write out the word letter by letter** s - t - r - a - w - b - e - r - r - y **Step 2: Examine each letter one at a time** | Position | Letter | Is it 'r'? | |----------|--------|------------| | 1 | s | No | | 2 | t | No | | 3 | r | ✅ Yes (1) | | 4 | a | No | | 5 | w | No | | 6 | b | No | | 7 | e | No | | 8 | r | ✅ Yes (2) | | 9 | r | ✅ Yes (3) | | 10 | y | No | **Step 3: Verify by splitting the word into parts** - "straw" → contains **1** r - "berry" → contains **2** r's - Total: 1 + 2 = **3** ## Answer The word "strawberry" contains **3** r's.
8.2s482 output tokens

Debug This Error

I'm getting the following error in my Node.js application: TypeError: Cannot read properties of undefined (reading 'map') at UserList (/app/components/UserList.js:12:25) at renderWithHooks (/app/node_modules/rea…

Claude Fable 5

## Cause The error means that when `UserList` renders, the `users` prop is `undefined`, so calling `.map()` on it fails. This typically happens for one of these reasons: 1. **The parent isn't passing the prop** (or has a typo in the prop name): ```jsx <UserList /> // users is undefined <UserList user={users} /> // typo: "user" instead of "users" ``` 2. **Data is fetched asynchronously** — the component renders before the API call finishes, and the initial state is `undefined`: ```jsx const [users, setUsers] = useState(); // undefined initially! ``` ## Fixes **Option 1: Default parameter value** (quick fix) ```jsx function UserList({ users = [] }) { re…
51.3s686 output tokens

Ember-1

## The Cause The error means `users` is `undefined` when the component renders, so calling `.map()` on it fails. The component itself is fine — the problem is that the `users` prop isn't being provided (or isn't ready yet). The most common reasons this happens: 1. **Async data hasn't loaded yet** — the parent fetches users from an API, and the component renders before the fetch completes: ```jsx const [users, setUsers] = useState(); // undefined initially! ``` 2. **The prop isn't passed or is misspelled** in the parent: ```jsx <UserList user={users} /> // typo: should be "users" ``` 3. **Wrong data shape** — e.g., passing the whole response object instead of `response…
18.2s960 output tokens

Code Review

Please review the following Python function and suggest improvements for readability, performance, and best practices: def get_data(url, retries=3): import requests import time for i in range(retries):…

Claude Fable 5

# Code Review Your function works, but there are several issues worth addressing. Here's a breakdown by category: ## Issues Found ### 1. **Bare `except:` clause (critical)** This catches *everything*, including `KeyboardInterrupt`, `SystemExit`, and bugs like `KeyError` or `TypeError` in your own parsing code. You'll silently retry on programming errors and mask real problems. ### 2. **Imports inside the function** Imports belong at module level (PEP 8). Function-level imports add overhead on each call and hide dependencies. ### 3. **`== True` comparison** Use truthiness directly: `if item["active"]:` (PEP 8 explicitly recommends this). ### 4. **Silent failures** Returning `[]` on fail…
38.5s1528 output tokens

Ember-1

# Code Review ## Bugs and correctness issues - **Bare `except:`** catches *everything* — including `KeyboardInterrupt` and, critically, `KeyError` from `item["active"]`. A malformed item in the response would be misinterpreted as a network failure, wasting all your retries on a data problem that retrying can't fix. - **Retrying all non-200 statuses** — a 404 or 401 will never succeed on retry. Only transient errors (connection failures, timeouts, 429, 5xx) are worth retrying. - **Wasted sleep on the final attempt** — the loop sleeps 2 seconds even after the last failure, before returning `[]`. - **Ambiguous return value** — `[]` means both "request failed" and "no active items." Callers ca…
95.0s5356 output tokens

Compare on more prompts →

Frequently asked questions

Which is cheaper, Claude Fable 5 or Ember-1?
Per 1M output tokens, Claude Fable 5 is ¥8,935 and Ember-1 is ¥2,680.5 on FastMetal (yen, before tax), so Ember-1 is cheaper.
How do the context windows of Claude Fable 5 and Ember-1 compare?
Claude Fable 5 takes 1,000,000 tokens; Ember-1 takes 1,048,576.
Can I use Claude Fable 5 and Ember-1 with the same API key?
Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "anthropic-claude-fable-5" or "ember-1" as the model. Each is billed at its own rate from the same prepaid balance.

Try both on one API key

Create an account and add credit to call Claude Fable 5 and Ember-1 from the browser chat and the API. No monthly fee.

More comparisons with Claude Fable 5

More comparisons with Ember-1