Hy4 vs Qwen3.8 Max
Pricing, context window and real answers (November 2026)
Hy4 (Tencent) and Qwen3.8 Max (Qwen), 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
 Hy4 |  Qwen3.8 Max | |
|---|---|---|
| Provider | Tencent | Qwen |
| Input (per 1M tokens) | $0.8799 | $2.11 |
| Output (per 1M tokens) | $2.64 | $6.33 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | $2.20 | $5.28 |
| Context window | 1,000,000 tokens | 1,000,000 tokens |
| Release date | 11/4/2026 | 8/3/2026 |
| Input modalities | text | text, image |
| Throughput (p50) | — | 84 tokens/s (n=28) |
| Arena · overall | Unranked | #24 · ELO 1,482 |
| Arena · Japanese | Unranked | #25 · ELO 1,475 |
| Arena · coding | Unranked | #29 · ELO 1,525 |
Prices are FastMetal's rates, before tax.
Rankings: LMArena leaderboard dataset (lmarena-ai/leaderboard-dataset), CC BY 4.0, snapshot 2026-10-28; category names mapped and ratings rounded by FastMetal.
Which should you pick?
- On price, Hy4: $2.64 per 1M output tokens, 58% less than Qwen3.8 Max.
- 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.
Hy4
The word **“strawberry”** is spelled:
**s t r a w b e r r y**
Step by step:
1. Check each letter: s, t, **r**, a, w, b, e, **r**, **r**, y
2. Mark the **r**’s: one after **t**, and two near the end before **y**.
3. Count them: 1 + 1 + 1 = **3**
So, there are **3** ‘r’s in **“strawberry”**.
4.2s343 output tokens
Qwen3.8 Max
The word **strawberry** is spelled:
**s t r a w b e r r y**
Now count the letter **r**:
1. s
2. t
3. **r** ← first r
4. a
5. w
6. b
7. e
8. **r** ← second r
9. **r** ← third r
10. y
There are **3** letters **r** in **strawberry**.
3.5s156 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…
Hy4
The error is caused by this line:
```js
{users.map(user => <li key={user.id}>{user.name}</li>)}
```
At render time, `users` is `undefined`. Since `.map()` only exists on arrays, JavaScript tries to read `map` from `undefined` and throws:
```txt
Cannot read properties of undefined (reading 'map')
```
Even though this is in a Node.js app, this specific error is happening during React rendering, likely server-side rendering or a Node-based build/render process.
Common causes:
1. The parent component is not passing `users`.
2. The prop name is misspelled.
3. `users` comes from async data and is `undefined` on the first render.
4. Your API returns something like `{ users: [...] }`, but you…
20.3s1951 output tokens
Qwen3.8 Max
The error means `users` is `undefined` when `UserList` tries to render:
```js
{users.map(user => ...)}
```
JavaScript cannot call `.map()` on `undefined`, so React throws:
```text
Cannot read properties of undefined (reading 'map')
```
## Most likely cause
The parent component is rendering `UserList` without passing a valid `users` array, or it is passing `users` before the data has loaded.
For example:
```jsx
<UserList />
```
or:
```jsx
<UserList users={undefined} />
```
or:
```jsx
const [users, setUsers] = useState(); // undefined initially
```
Then later:
```jsx
<UserList users={users} />
```
On the first render, `users` is still `undefined`.
---
## Fix 1: Give `users` a d…
17.7s1020 output tokens
Professional Email
Write a professional email to a client explaining that the project delivery will be delayed by two weeks due to unexpected technical challenges discovered during integration testing. The tone should be apologetic but con…
Hy4
**Subject:** Revised Delivery Timeline for [Project Name]
Dear [Client Name],
I’m writing to let you know that we need to adjust the delivery date for [Project Name] by two weeks, from [Original Delivery Date] to [Revised Delivery Date].
During integration testing, we identified unexpected technical challenges that require additional remediation before we can move confidently into final acceptance and deployment. These issues primarily affect [briefly describe affected area, e.g., data synchronization between systems / third-party API handling / environment configuration], and resolving them properly is essential to ensure the solution performs reliably in your production environment.
I…
25.0s2350 output tokens
Qwen3.8 Max
Subject: Revised Project Delivery Timeline – Updated Schedule and Next Steps
Dear [Client Name],
I hope this message finds you well.
I am writing to provide an update on the current status of the project and to inform you that, during our recent integration testing phase, we encountered several unexpected technical challenges that will impact the original delivery timeline. After careful review with the technical team, we now anticipate the revised delivery date will be [insert date – two weeks from original delivery date].
Please accept my sincere apologies for this delay. We understand the importance of this project and the expectations tied to the original schedule. While this situati…
11.9s547 output tokens
Frequently asked questions
- Which is cheaper, Hy4 or Qwen3.8 Max?
- Per 1M output tokens, Hy4 is $2.64 and Qwen3.8 Max is $6.33 on FastMetal (US dollars, before tax), so Hy4 is cheaper.
- How do the context windows of Hy4 and Qwen3.8 Max compare?
- Hy4 takes 1,000,000 tokens; Qwen3.8 Max takes 1,000,000.
- Can I use Hy4 and Qwen3.8 Max with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "hy4" or "qwen3.8-max" 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 Hy4 and Qwen3.8 Max from the browser chat and the API. No monthly fee.