Claude Fable 5.1 vs Fugu Ultra v2
Pricing, context window and real answers (September 2026)
Claude Fable 5.1 (Anthropic) and Fugu Ultra v2 (Sakana AI), 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
 Claude Fable 5.1 | Fugu Ultra v2 | |
|---|---|---|
| Provider | Anthropic | Sakana AI |
| Input (per 1M tokens) | ¥1,787 | ¥893.5 |
| Output (per 1M tokens) | ¥8,935 | ¥5,361 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥6,255 | ¥3,574 |
| Context window | 1,000,000 tokens | 1,000,000 tokens |
| Release date | 9/1/2026 | 9/11/2026 |
| Input modalities | text, image, file | text, image, file |
| Throughput (p50) | — | — |
| Arena · overall | #5 · ELO 1,498 | Unranked |
| Arena · Japanese | Unranked | Unranked |
| Arena · coding | #32 · ELO 1,519 | Unranked |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, Fugu Ultra v2: ¥5,361 per 1M output tokens, 40% less than Claude Fable 5.1.
- 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.1
**Step 1: Write out the word letter by letter.**
s - t - r - a - w - b - e - r - r - y
**Step 2: Number each position.**
1. s
2. t
3. **r**
4. a
5. w
6. b
7. e
8. **r**
9. **r**
10. y
**Step 3: Identify which positions contain 'r'.**
- Position 3: r (in "str-")
- Position 8: r (in "-ber-")
- Position 9: r (in "-rry")
**Step 4: Count them.**
3 + 1 + 1 = **3**
**Answer: There are 3 'r's in "strawberry."**
A helpful way to check: split the word into its parts — "straw" (1 r) + "berry" (2 r's) = 3 r's total.
7.9s259 output tokens
Fugu Ultra v2
**Answer: 3**
**Step-by-step reasoning:**
1. **Write out the word letter by letter**, assigning each a position:
| Position | Letter | Is it 'r'? |
|---|---|---|
| 1 | s | no |
| 2 | t | no |
| 3 | **r** | ✅ yes |
| 4 | a | no |
| 5 | w | no |
| 6 | b | no |
| 7 | e | no |
| 8 | **r** | ✅ yes |
| 9 | **r** | ✅ yes |
| 10 | y | no |
2. **Tally the matches:** positions 3, 8, and 9 are 'r'.
3. **Sanity check by chunks:** "straw" contains one 'r' (str**a**w → the r in "str"), and "berry" contains two 'r's (be**rr**y). 1 + 2 = 3.
4. **Verify length:** the letters counted total 10, which matches the length of "strawberry" — so no letter was skipped or double-counted.
**Conclusion:** There a…
10.2s435 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.1
The error means that when `UserList` rendered, the `users` prop was `undefined`, so calling `.map()` on it failed. This typically happens because:
1. **The parent isn't passing the prop** (or misspelled it, e.g. `<UserList user={...} />`), or
2. **The data hasn't loaded yet.** A common pattern is fetching users in a `useEffect` and storing them in state whose initial value is `undefined` (e.g. `useState()`), so the first render happens before the data arrives.
**Fixes**
Give the prop a default value so the component is safe to render with no data:
```jsx
function UserList({ users = [] }) {
return (
<ul>
{users.map(user => <li key={user.id}>{user.name}</li>)}
</ul>
);
}…
10.8s564 output tokens
Fugu Ultra v2
## What the error means
`TypeError: Cannot read properties of undefined (reading 'map')` means that when `UserList` rendered, `users` was `undefined`, and JavaScript can't read the `.map` property off `undefined`.
The important detail: **the bug isn't really in `UserList`** — that's just where it surfaces. Destructuring `function UserList({ users })` does *not* throw when the prop is missing; it silently gives you `undefined`. The crash is deferred to the first property access, which is `.map` on line 12.
So the real question is: why is `props.users` not an array?
## Why `users` is undefined
**1. Async data hasn't arrived yet — by far the most common cause.**
```jsx
const [users, setUs…
70.8s5286 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.1
Here's a review of the function organized by category, followed by a refactored version.
## Issues
### Correctness / robustness
1. **Bare `except:`** — This catches *everything*, including `KeyboardInterrupt`, `SystemExit`, and bugs like `KeyError` from `item["active"]`. A malformed response would be silently retried three times and then swallowed. Catch `requests.RequestException` (and `ValueError` for bad JSON) specifically.
2. **Retrying non-retryable errors** — A 404 or 400 will never succeed on retry. Only retry on transient failures (timeouts, connection errors, 5xx, 429).
3. **Silent failure** — Returning `[]` after exhausting retries is indistinguishable from "the endpoint legitima…
27.7s2028 output tokens
Fugu Ultra v2
# Final Code Review: `get_data`
The function is compact and its intent is clear, but as written it will **fail silently in production**. Two defects dominate everything else:
1. The bare `except:` swallows every error — including `KeyboardInterrupt` and genuine logic bugs.
2. A total failure and a legitimately empty dataset both return `[]`, so callers cannot tell "the service is down" from "there are no active records."
Together these mean an outage looks exactly like a successful empty response. Everything else below is meaningful improvement; those two are the difference between code that fails loudly and code that fails invisibly.
---
## 1. Correctness and error handling
### 1.1 `e…
281.1s23317 output tokens
Frequently asked questions
- Which is cheaper, Claude Fable 5.1 or Fugu Ultra v2?
- Per 1M output tokens, Claude Fable 5.1 is ¥8,935 and Fugu Ultra v2 is ¥5,361 on FastMetal (yen, before tax), so Fugu Ultra v2 is cheaper.
- How do the context windows of Claude Fable 5.1 and Fugu Ultra v2 compare?
- Claude Fable 5.1 takes 1,000,000 tokens; Fugu Ultra v2 takes 1,000,000.
- Can I use Claude Fable 5.1 and Fugu Ultra v2 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "anthropic-claude-fable-5-1" or "fugu-ultra-v2" 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.1 and Fugu Ultra v2 from the browser chat and the API. No monthly fee.