Model comparison

GPT-5.6 Terra vs GPT-6 Astra

Pricing, context window and real answers (September 2026)

GPT-5.6 Terra (OpenAI) and GPT-6 Astra (OpenAI), 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

openai logoGPT-5.6 Terraopenai logoGPT-6 Astra
ProviderOpenAIOpenAI
Input (per 1M tokens)¥357.4¥1,717.72
Output (per 1M tokens)¥2,144.4¥8,588.62
Typical cost (1,000 in + 500 out tokens × 1,000 calls)¥1,430¥6,012
Context window1,050,000 tokens1,050,000 tokens
Release date7/9/20269/4/2026
Input modalitiesfile, image, textfile, image, text
Arena · overall#43 · ELO 1,466Unranked
Arena · Japanese#18 · ELO 1,474Unranked
Arena · coding#31 · ELO 1,519Unranked

Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.

Which should you pick?

  • On price, GPT-5.6 Terra: ¥2,144.4 per 1M output tokens, 75% less than GPT-6 Astra.
  • 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

GPT-6 Astra

“strawberry” is spelled **s-t-r-a-w-b-e-r-r-y**. The letter **r** appears in positions **3, 8, and 9**, so there are **3 r’s**.
3.8s85 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

GPT-6 Astra

The error means **`users` is `undefined` when React renders `UserList`**, so calling `users.map(...)` fails. This commonly happens when the parent doesn’t pass the prop or when data hasn’t finished loading. ### 1. Default `users` to an empty array If an absent prop should mean “no users,” use a default value: ```jsx function UserList({ users = [] }) { return ( <ul> {users.map(user => ( <li key={user.id}>{user.name}</li> ))} </ul> ); } ``` This handles a missing or `undefined` prop, but **not `null` or other non-array values**. ### 2. Check where the prop comes from Make sure the parent passes an array. For data loaded asynchronously, initialize state to…
6.7s380 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

GPT-6 Astra

The function is compact, but its biggest issue is that **all failures silently become `[]`**, making an unavailable API indistinguishable from a successful response with no active items. ### Suggested improvements - **Move imports to module scope** for clarity and conventional organization. - **Avoid bare `except:`.** It catches everything, including `KeyboardInterrupt`, and hides bugs such as missing dictionary keys. - **Retry only transient failures**, such as connection errors, timeouts, rate limiting, and selected server errors. Retrying a `401` or `404` usually won’t help. - **Don’t sleep after the final failed attempt.** Use exponential backoff rather than a fixed delay. - **Use desc…
19.2s965 output tokens

Compare on more prompts →

Frequently asked questions

Which is cheaper, GPT-5.6 Terra or GPT-6 Astra?
Per 1M output tokens, GPT-5.6 Terra is ¥2,144.4 and GPT-6 Astra is ¥8,588.62 on FastMetal (yen, before tax), so GPT-5.6 Terra is cheaper.
How do the context windows of GPT-5.6 Terra and GPT-6 Astra compare?
GPT-5.6 Terra takes 1,050,000 tokens; GPT-6 Astra takes 1,050,000.
Can I use GPT-5.6 Terra and GPT-6 Astra with the same API key?
Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "gpt-5.6-terra" or "gpt-6-astra" 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 GPT-6 Astra from the browser chat and the API. No monthly fee.

More comparisons with GPT-5.6 Terra

More comparisons with GPT-6 Astra