Beam 1.0 501B A23B vs GLM 5.3 FlashX
Pricing, context window and real answers (October 2026)
Beam 1.0 501B A23B (Reflection AI) and GLM 5.3 FlashX (Z.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 |  GLM 5.3 FlashX | |
|---|---|---|
| Provider | Reflection AI | Z.ai |
| Input (per 1M tokens) | $0.422 | $0.407 |
| Output (per 1M tokens) | $1.27 | $1.38 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | $1.06 | $1.10 |
| Context window | 1,048,576 tokens | 1,048,576 tokens |
| Release date | 10/16/2026 | 9/18/2026 |
| Input modalities | text | text, image, video |
| Throughput (p50) | — | 349 tokens/s (n=20) |
| 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, 8% less than GLM 5.3 FlashX.
- 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
GLM 5.3 FlashX
# Counting 'r's in "strawberry"
**Step 1: Write out each letter with its position**
| Position | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
|----------|---|---|---|---|---|---|---|---|---|----|
| Letter | s | t | r | a | w | b | e | r | r | y |
**Step 2: Check each letter one by one**
- Position 1: **s** → not an 'r'
- Position 2: **t** → not an 'r'
- Position 3: **r** → ✅ 'r' found (count: 1)
- Position 4: **a** → not an 'r'
- Position 5: **w** → not an 'r'
- Position 6: **b** → not an 'r'
- Position 7: **e** → not an 'r'
- Position 8: **r** → ✅ 'r' found (count: 2)
- Position 9: **r** → ✅ 'r' found (count: 3)
- Position 10: **y** → not an 'r'
**Step 3: Tally the results**
The 'r's a…
4.1s549 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
GLM 5.3 FlashX
## What's Happening
The error means `users` is `undefined` at the time `UserList` renders. You're calling `.map()` on `undefined`, which JavaScript doesn't allow. This almost always happens for one of these reasons:
1. **The parent isn't passing the prop** — `<UserList />` with no `users` prop
2. **Data hasn't loaded yet** — you're fetching asynchronously, so the first render happens before the data arrives
3. **Prop name mismatch** — e.g., passing `user` but reading `users`
4. **Parent state initialized to `undefined`** — e.g., `useState()` instead of `useState([])`
## Fixes
### Option 1: Default parameter (simplest)
```jsx
function UserList({ users = [] }) {
return (
<ul>…
6.8s934 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
GLM 5.3 FlashX
# Code Review
The function works, but there are several issues worth addressing — including one subtle bug caused by the bare `except`.
## Correctness issues (most important)
1. **Bare `except:` is dangerous and masks a bug.** It catches *everything*, including `KeyboardInterrupt` and `SystemExit` (so Ctrl+C during a retry sleep is swallowed). Worse: because your data-processing loop sits inside the `try`, a `KeyError` from a malformed item is treated as a network failure — triggering a pointless re-download of the URL and silently discarding the real error. Catch only `requests.RequestException` (and `ValueError` for JSON decode failures).
2. **Silent failure.** Returning `[]` on error…
36.9s5836 output tokens
Frequently asked questions
- Which is cheaper, Beam 1.0 501B A23B or GLM 5.3 FlashX?
- Per 1M output tokens, Beam 1.0 501B A23B is $1.27 and GLM 5.3 FlashX is $1.38 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 GLM 5.3 FlashX compare?
- Beam 1.0 501B A23B takes 1,048,576 tokens; GLM 5.3 FlashX takes 1,048,576.
- Can I use Beam 1.0 501B A23B and GLM 5.3 FlashX with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "beam-1.0" or "glm-5.3-flashx" 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 GLM 5.3 FlashX from the browser chat and the API. No monthly fee.