API429 / gpt-5.6-terra

GPT-5.6 Terra API: pricing, integration and limits

GPT-5.6 Terra through API429 costs $0.75 per 1M input and $4.50 per 1M output tokens — 62% below the official OpenAI rate of $2 / $12.

GPT-5.6 Terra: record labels, supporting quotes and missing fields. Plan a small control task, retain input and accepted results, and verify access under your key. Manufacturer specifications and the client request contract are separate checks.

GPT-5.6 Terra API by OpenAI: access through API429
GPT-5.6 Terra (gpt-5.6-terra) is a text model by OpenAI, available through the OpenAI-compatible API429 with one key.

Read in Russian

Published: · Updated:

Exact ID: gpt-5.6-terra. Models available to your key: GET /v1/models.

GPT-5.6 Terra API pricing

API429 priceOfficial OpenAI price (Standard)
$0.937500000000 / 1,000,000 cache-write input tokens · Context up to 272,000 tokens inclusive
$1.875000000000 / 1,000,000 cache-write input tokens · Context over 272,000 tokens
$0.075000000000 / 1,000,000 cached input tokens · Context up to 272,000 tokens inclusive
$0.150000000000 / 1,000,000 cached input tokens · Context over 272,000 tokens
$0.750000000000 / 1,000,000 input tokens · Context up to 272,000 tokens inclusive
$1.500000000000 / 1,000,000 input tokens · Context over 272,000 tokens
$4.500000000000 / 1,000,000 output tokens · Context up to 272,000 tokens inclusive
$6.750000000000 / 1,000,000 output tokens · Context over 272,000 tokens
$3.000000000000 / 1,000 web-search calls
$2 / $12 per 1M ordinary input / output tokens

Standard; input ≤272,000 tokens

Manufacturer sourceChecked: Oct 24, 2026. Cache, tools and special modes are excluded from this rate pair.

API429 prices as of the catalog dated .

Cost calculator for GPT-5.6 Terra

API429$3.75
Manufacturer$10
Difference from manufacturer price62.5%API429 costs less for this workload

Manufacturer maximum input: 922,000 tokens per request. Effective API429 limits are unknown.

Ordinary input and output are counted, excluding cache, tools, fees and repeated calls. This estimates spending; it does not validate whether a request is accepted. RUB results use only your entered rate; they are neither a bank quote nor a top-up amount.

Context and capabilities of GPT-5.6 Terra

The manufacturer specifies a shared context window of 1,050,000 and a maximum output of 128,000 tokens; maximum input of 922,000 tokens for its own API (specification: OpenAI, checked Oct 24, 2026, 6:11 AM UTC). These are manufacturer limits, not verified effective API429 limits: test very long contexts on your own request.

API429 capabilities published for this exact ID: chat . Test any mode missing from this list on your own request.

Practical task: repeatable record extraction and classification

Define allowed categories and required fields before sending the first request. Permit an unknown result when no category fits. Your application should validate structure, required fields and consistency with the source text after receiving an answer. Include ambiguous and empty records in the evaluation set, rather than only straightforward examples.

Exact version and lifecycle

The release date is July 9, 2026. Terra and Sol are distinct exact IDs; a shared GPT-5.6 prefix is insufficient to transfer prices. The example requests ordinary text and does not establish native structured-output support or identical parameter behavior across manufacturer APIs.

Context, output and ordinary token budget

According to OpenAI documentation reviewed on 2026-10-24, the manufacturer shared window is 1,050,000 tokens, with an independent 922,000 input cap and 128,000 output cap. All three limits must be checked separately. Standard is $2/$12 per million input/output tokens at input <=272,000 tokens. Above 272,000, the entire request uses $4/$18. Validation failures followed by another request increase actual spending even if the final accepted record is short.

Alternatives for a controlled comparison

gemini-2.5-flash-lite is a candidate for maintaining a budget baseline. gemini-3.1-pro-preview is a candidate for preview prompt stability evaluation. claude-opus-4-6 is a candidate for a coding review baseline.

Speed and errors of GPT-5.6 Terra over 24 hours

Over the last 24 hours: mean successful response time — 6.1 s; service error rate — 0%. Data as of .

Source: public 24-hour statistics. The mean is neither a median nor a response time guarantee.

How to connect GPT-5.6 Terra: curl, Python, JavaScript

Create a key, check your balance and set API429_API_KEY on the server. The request is paid from your balance; Python and JavaScript first check that the model is available to your key.

curl

Before generation, check the exact ID in the response from GET https://gateway.api429.com/v1/models using the same Bearer key.

curl --fail-with-body https://gateway.api429.com/v1/chat/completions \
  -H "Authorization: Bearer $API429_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"gpt-5.6-terra","messages":[{"role":"user","content":"Categories: billing, error, other. Record: After payment, the start button does not work. Give one category, the supporting quote and missing information; do not invent an order number."}],"max_tokens":512,"stream":false}'

Python 3

import json
import os
import urllib.request

key = os.environ["API429_API_KEY"]
base = "https://gateway.api429.com/v1"
headers = {"Authorization": "Bearer " + key, "Content-Type": "application/json"}
models_request = urllib.request.Request(base + "/models", headers=headers)
with urllib.request.urlopen(models_request, timeout=30) as response:
    available = {item["id"] for item in json.load(response)["data"]}
model = "gpt-5.6-terra"
if model not in available:
    raise ValueError("Model is unavailable to this key")
payload = json.loads("{\"model\":\"gpt-5.6-terra\",\"messages\":[{\"role\":\"user\",\"content\":\"Categories: billing, error, other. Record: After payment, the start button does not work. Give one category, the supporting quote and missing information; do not invent an order number.\"}],\"max_tokens\":512,\"stream\":false}")
request = urllib.request.Request(base + "/chat/completions",
    data=json.dumps(payload).encode("utf-8"), headers=headers, method="POST")
with urllib.request.urlopen(request, timeout=60) as response:
    result = json.load(response)
choice = result["choices"][0]
if choice.get("finish_reason") != "stop" or not choice.get("message", {}).get("content"):
    raise ValueError("Incomplete or empty response")
print(choice["message"]["content"])
print(result.get("usage"))

JavaScript: Node.js 18+

const key = process.env.API429_API_KEY;
if (!key) throw new Error("Set API429_API_KEY");
const base = "https://gateway.api429.com/v1";
const headers = { Authorization: "Bearer " + key, "Content-Type": "application/json" };
const model = "gpt-5.6-terra";
const available = await fetch(base + "/models", { headers, signal: AbortSignal.timeout(30000) });
if (!available.ok) throw new Error("Models HTTP " + available.status);
if (!(await available.json()).data.some(item => item.id === model)) throw new Error("Model unavailable to this key");
const response = await fetch(base + "/chat/completions", {
  method: "POST", headers, signal: AbortSignal.timeout(60000),
  body: JSON.stringify({"model":"gpt-5.6-terra","messages":[{"role":"user","content":"Categories: billing, error, other. Record: After payment, the start button does not work. Give one category, the supporting quote and missing information; do not invent an order number."}],"max_tokens":512,"stream":false})
});
if (!response.ok) throw new Error("Generation HTTP " + response.status);
const result = await response.json();
const choice = result.choices?.[0];
if (choice?.finish_reason !== "stop" || !choice?.message?.content) throw new Error("Incomplete or empty response");
console.log(choice.message.content);
console.log(result.usage);

The examples use basic fields from the published API contract.

GPT-5.6 Terra in n8n: HTTP Request

  1. Create an HTTP Request with method POST and URL https://gateway.api429.com/v1/chat/completions.
  2. Store the Bearer key in credentials; add Content-Type: application/json. Do not put the key in an exported workflow example.
  3. Send the JSON from curl: the exact model gpt-5.6-terra, messages, max_tokens and stream=false.
  4. After the HTTP node, check choices, finish_reason and the response content before writing the result to your production system.

HTTP Request documentation.

Alternatives to GPT-5.6 Terra: similar models and prices

Compare them on the same task. Prices apply to a short text request; see the catalog for full pricing.

ModelAPI429: input / output per 1M tokens
Gemini 2.5 Flash Litegemini-2.5-flash-lite$0.03 / $0.12
Gemini 3.1 Pro Previewgemini-3.1-pro-preview$0.6 / $3.6
Claude Opus 4.6claude-opus-4-6$1.5 / $7.5

Version and release date

Manufacturer API release date, OpenAI: . The exact predecessor has not been established in the reviewed sources.

Payment and a $10 test

  • Russian bank card. Top up your balance in the account.
  • Invoice for companies. Bank transfer with closing documents.
  • USDT and TON. Top up in crypto.

$10 test credit. Subscribe to our Telegram channel through the bot and get $10 on your balance for the first requests. Get $10 in the bot

Frequently asked questions

Which category fits payment followed by a broken button?

Define a rule for multi-topic records in advance. If a post-payment malfunction takes priority, expect error with the exact button-related quote. The example does not establish a universal classification: acceptance depends on your own documented support-routing policy.

Does textual labeling guarantee native structured output?

No. The Terra example requests ordinary text containing a category, quote and missing information. Validate allowed labels and supporting evidence in your application. Establish native response-schema support separately through the public contract; a request for a format in a prompt is insufficient evidence.

How should I budget batches above 272,000 input tokens?

According to OpenAI documentation reviewed on 2026-10-24, standard is $2/$12 per million input/output tokens through 272,000 inclusive. At 272,001 and above, the whole request uses $4/$18. Before combining records, compare fewer requests with the tier change and the cost of repeating an unsuccessful combined packet.

How does a Terra evaluation differ from the Sol briefing task?

Terra is evaluated here on a record with an allowed label, supporting quote and correctly identified missing data. Sol is used for an evidence-based briefing. Measure field accuracy separately from long-form writing quality because they require different acceptance criteria.

Sources and review

Editorial review: . Pricing and general calculator · Getting started · Compare the family: OpenAI

Telegram