Beam 1.0 501B A23B vs Fugu Ultra v2
Pricing, context window and real answers (October 2026)
Beam 1.0 501B A23B (Reflection AI) 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
| Beam 1.0 501B A23B | Fugu Ultra v2 | |
|---|---|---|
| Provider | Reflection AI | Sakana AI |
| Input (per 1M tokens) | $0.422 | $5.50 |
| Output (per 1M tokens) | $1.27 | $33.00 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | $1.06 | $22.00 |
| Context window | 1,048,576 tokens | 1,000,000 tokens |
| Release date | 10/16/2026 | 9/11/2026 |
| Input modalities | text | text, image, file |
| Throughput (p50) | — | 22222 tokens/s (n=24) |
| Arena · overall | Unranked | Unranked |
| Arena · Japanese | Unranked | Unranked |
| Arena · coding | Unranked | Unranked |
Prices are FastMetal's rates, before tax.
Rankings: LMArena leaderboard dataset (lmarena-ai/leaderboard-dataset), CC BY 4.0, snapshot 2026-10-15; category names mapped and ratings rounded by FastMetal.
Which should you pick?
- On price, Beam 1.0 501B A23B: $1.27 per 1M output tokens, 96% less than Fugu Ultra v2.
- For long documents, Beam 1.0 501B A23B: 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.
Beam 1.0 501B A23B
The word “strawberry” is spelled:
s - t - r - a - w - b - e - r - r - y
The letter “r” appears in these positions:
- s**r**awberry (1st r)
- strawbe**r**ry (2nd r)
- strawber**r**y (3rd r)
Therefore, there are **3** r's in “strawberry.”
7.6s278 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…
Beam 1.0 501B A23B
The error means `users` is `undefined` when `UserList` renders, so calling `.map` on `undefined` throws.
### Common causes
1. Parent renders `<UserList />` without a `users` prop.
2. Parent passes `users={data}` where `data` is still `undefined` (e.g., fetch not resolved).
3. Destructured prop name mismatch.
### Fixes
**1. Default the prop**
```js
function UserList({ users = [] }) {
return (
<ul>
{users.map(user => <li key={user.id}>{user.name}</li>)}
</ul>
);
}
```
**2. Guard in JSX**
```js
{Array.isArray(users) && users.map(user => <li key={user.id}>{user.name}</li>)}
```
**3. Optional chaining**
```js
{users?.map(user => <li key={user.id}>{user.name}</li>)}
```
Note…
12.8s414 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):…
Beam 1.0 501B A23B
Here are some key issues and improvements:
### Main issues in the original
- **Imports inside the function** run on every call and hurt readability.
- **Bare `except:`** catches `KeyboardInterrupt`, `SystemExit`, and programming errors.
- **Retries every non-200 response**, including `404`/`400`, which usually should not be retried.
- **`item["active"] == True`** can raise `KeyError` and is stricter than necessary unless you truly need exact boolean equality.
- **Fixed sleep and unnecessary final sleep** before returning.
- **Repeated `item["name"]` / `item["id"]`** lookups are slightly slower and less clean than a comprehension.
- No handling/validation for malformed JSON or non-list respo…
16.8s1927 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, Beam 1.0 501B A23B or Fugu Ultra v2?
- Per 1M output tokens, Beam 1.0 501B A23B is $1.27 and Fugu Ultra v2 is $33.00 on FastMetal (US dollars, before tax), so Beam 1.0 501B A23B is cheaper.
- How do the context windows of Beam 1.0 501B A23B and Fugu Ultra v2 compare?
- Beam 1.0 501B A23B takes 1,048,576 tokens; Fugu Ultra v2 takes 1,000,000.
- Can I use Beam 1.0 501B A23B and Fugu Ultra v2 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "beam-1.0" 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 Beam 1.0 501B A23B and Fugu Ultra v2 from the browser chat and the API. No monthly fee.