Ember-1 vs Fugu Ultra v2
Pricing, context window and real answers (September 2026)
Ember-1 (Fireworks) 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
| Ember-1 | Fugu Ultra v2 | |
|---|---|---|
| Provider | Fireworks | Sakana AI |
| Input (per 1M tokens) | ¥536.1 | ¥893.5 |
| Output (per 1M tokens) | ¥2,680.5 | ¥5,361 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥1,876 | ¥3,574 |
| Context window | 1,048,576 tokens | 1,000,000 tokens |
| Release date | 9/24/2026 | 9/11/2026 |
| Input modalities | text, image | text, image, file |
| Throughput (p50) | — | — |
| Arena · overall | Unranked | Unranked |
| Arena · Japanese | Unranked | Unranked |
| Arena · coding | Unranked | Unranked |
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, 50% less than Fugu Ultra v2.
- For long documents, Ember-1: a 1,048,576-token context window against 1,000,000 for Fugu Ultra v2.
- 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.
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
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…
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
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):…
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
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, Ember-1 or Fugu Ultra v2?
- Per 1M output tokens, Ember-1 is ¥2,680.5 and Fugu Ultra v2 is ¥5,361 on FastMetal (yen, before tax), so Ember-1 is cheaper.
- How do the context windows of Ember-1 and Fugu Ultra v2 compare?
- Ember-1 takes 1,048,576 tokens; Fugu Ultra v2 takes 1,000,000.
- Can I use Ember-1 and Fugu Ultra v2 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "ember-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 Ember-1 and Fugu Ultra v2 from the browser chat and the API. No monthly fee.