GPT-5.6 Terra vs Mercury 2.5
Pricing, context window and real answers (September 2026)
GPT-5.6 Terra (OpenAI) and Mercury 2.5 (Inception), 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 | Mercury 2.5 | |
|---|---|---|
| Provider | OpenAI | Inception |
| Input (per 1M tokens) | ¥357.4 | ¥6.77 |
| Output (per 1M tokens) | ¥2,144.4 | ¥25.38 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥1,430 | ¥19 |
| Context window | 1,050,000 tokens | 260,000 tokens |
| Release date | 7/9/2026 | 9/8/2026 |
| Input modalities | file, image, text | text |
| Arena · overall | #43 · ELO 1,466 | Unranked |
| Arena · Japanese | #18 · ELO 1,474 | Unranked |
| Arena · coding | #31 · ELO 1,519 | Unranked |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, Mercury 2.5: ¥25.38 per 1M output tokens, 99% less than GPT-5.6 Terra.
- For long documents, GPT-5.6 Terra: a 1,050,000-token context window against 260,000 for Mercury 2.5.
- 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
Mercury 2.5
To determine the number of 'r's in the word "strawberry", we can examine each letter in sequence:
1. **s** - Not 'r'
2. **t** - Not 'r'
3. **r** - First 'r' found
4. **a** - Not 'r'
5. **w** - Not 'r'
6. **b** - Not 'r'
7. **e** - Not 'r'
8. **r** - Second 'r' found
9. **r** - Third 'r' found
10. **y** - Not 'r'
Counting these occurrences, there are **3** 'r's in "strawberry".
1.8s968 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
Mercury 2.5
This error occurs because the `users` prop is `undefined` when the component renders. Since the code calls `.map()` on `users`, JavaScript throws a TypeError when `users` is not an array.
Here is how to fix it:
1. **Set a Default Value**
Update the function signature to default `users` to an empty array if it is not provided:
```javascript
function UserList({ users = [] }) {
// ...
}
```
2. **Add a Conditional Check**
If `users` might be null or undefined during data loading, guard the map operation:
```javascript
{users && users.map(user => <li key={user.id}>{user.name}</li>)}
```
3. **Verify Parent Props**
Ensure the parent component pas…
2.4s1028 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
Mercury 2.5
Here is a review of the function with suggestions for improvement.
### Key Observations
1. **Imports:** Libraries should be imported at the module level, not inside functions.
2. **Exception Handling:** Bare `except:` clauses catch system exits and interrupts. Use specific exceptions like `requests.exceptions.RequestException`.
3. **Logic & Pythonicity:**
* Avoid `== True`; rely on truthiness or `item.get("active")`.
* List comprehensions are more concise and efficient than manual appending.
4. **Retry Strategy:** Implement exponential backoff instead of fixed sleeps, and avoid sleeping after the final failed attempt.
5. **Documentation:** Add type hints and a docstring fo…
4.6s1999 output tokens
Frequently asked questions
- Which is cheaper, GPT-5.6 Terra or Mercury 2.5?
- Per 1M output tokens, GPT-5.6 Terra is ¥2,144.4 and Mercury 2.5 is ¥25.38 on FastMetal (yen, before tax), so Mercury 2.5 is cheaper.
- How do the context windows of GPT-5.6 Terra and Mercury 2.5 compare?
- GPT-5.6 Terra takes 1,050,000 tokens; Mercury 2.5 takes 260,000.
- Can I use GPT-5.6 Terra and Mercury 2.5 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "gpt-5.6-terra" or "mercury-2.5" 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 Mercury 2.5 from the browser chat and the API. No monthly fee.