GPT-5.6 Terra vs Hy4
Pricing, context window and real answers (November 2026)
GPT-5.6 Terra (OpenAI) and Hy4 (Tencent), 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
 GPT-5.6 Terra |  Hy4 | |
|---|---|---|
| Provider | OpenAI | Tencent |
| Input (per 1M tokens) | $2.11 | $0.8799 |
| Output (per 1M tokens) | $12.66 | $2.64 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | $8.44 | $2.20 |
| Context window | 1,050,000 tokens | 1,000,000 tokens |
| Release date | 7/9/2026 | 11/4/2026 |
| Input modalities | file, image, text | text |
| Throughput (p50) | 210 tokens/s (n=28) | — |
| Arena · overall | #50 · ELO 1,467 | Unranked |
| Arena · Japanese | #31 · ELO 1,463 | Unranked |
| Arena · coding | #43 · ELO 1,517 | Unranked |
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, 79% less than GPT-5.6 Terra.
- For long documents, GPT-5.6 Terra: a 1,050,000-token context window against 1,000,000 for Hy4.
- 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.
GPT-5.6 Terra
“strawberry” is spelled:
s t **r** a w b e **r** **r** y
There are **3** occurrences of the letter **r**.
3.6s71 output tokens
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
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…
GPT-5.6 Terra
The error means `users` is `undefined` when `UserList` renders, so React tries to evaluate:
```js
users.map(...)
```
But `.map()` only exists on arrays.
Common causes:
- The parent component does not pass a `users` prop.
- The user data is loaded asynchronously and has not arrived on the first render.
- The API response shape differs from what you expect, e.g. data is in `response.data.users` rather than `response.data`.
- The parent initializes its user state as `undefined` or `null`.
## Fix options
### 1. Initialize users as an empty array
In the parent component:
```jsx
const [users, setUsers] = useState([]);
```
Then pass it normally:
```jsx
<UserList users={users} />
```
An e…
5.8s559 output tokens
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
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):…
GPT-5.6 Terra
Here are the main areas to improve:
### Issues in the original code
- **Imports inside the function**: Move `requests` and `time` imports to module scope.
- **Bare `except:`**: This catches everything, including `KeyboardInterrupt` and programming errors. Catch `requests.RequestException` (and possibly JSON decoding errors) instead.
- **Status code check**: Prefer `response.raise_for_status()` or `response.ok` over manually checking only for `200`. Successful responses can include other 2xx status codes.
- **`== True`**: Use `if item.get("active"):` instead.
- **Potential `KeyError`**: `item["name"]`, `item["id"]`, and `item["active"]` can fail if the API response is incomplete. Use `.get(…
10.6s939 output tokens
Hy4
Here are the main improvement areas, followed by a possible rewrite.
## Key issues
### Readability / style
- Move imports to the top of the module.
- Use descriptive names: `response` instead of `r`, `attempt` instead of `i`.
- `if item["active"] == True:` should be `if item.get("active") is True:` or simply `if item.get("active"):`, depending on intent.
- The filtering loop can be a list comprehension.
- Add type hints and a docstring.
### Performance
- Repeated imports are cached by Python, so not a major cost, but top-level imports are cleaner.
- Avoid sleeping after the final failed attempt.
- Use `requests.Session` for connection pooling if this function may be called repeatedly or i…
110.2s10761 output tokens
Frequently asked questions
- Which is cheaper, GPT-5.6 Terra or Hy4?
- Per 1M output tokens, GPT-5.6 Terra is $12.66 and Hy4 is $2.64 on FastMetal (US dollars, before tax), so Hy4 is cheaper.
- How do the context windows of GPT-5.6 Terra and Hy4 compare?
- GPT-5.6 Terra takes 1,050,000 tokens; Hy4 takes 1,000,000.
- Can I use GPT-5.6 Terra and Hy4 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "gpt-5.6-terra" or "hy4" 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 GPT-5.6 Terra and Hy4 from the browser chat and the API. No monthly fee.