gpt-6-astra) is the new-generation flagship OpenAI released on September 3, 2026, positioned for computer use, software engineering, science, and long-horizon agent work: 1,050,000-token context, 128,000-token max output, adjustable reasoning effort. APIYI has both the Responses and Chat Completions endpoints open and ran the same 74-check matrix on launch day across three lines: official relay via OpenAI direct, official relay via Azure, and Codex_Reverse.
gpt-6-astra. The default / svip official-relay groups are priced line for line with OpenAI and are served by two official lines, OpenAI direct and Azure; the Codex_Reverse group (Codex reverse-engineered resources) bills at a 0.5x discount. Function calling and the agent toolchain live only on Responses, so start new projects there.Why it stands out
Built to finish tasks
1.05M context, measured
Complete Responses toolchain
web_search and code_interpreter tools work; encrypted reasoning items replay statelessly. Strict JSON Schema output matched the field set exactly.Three lines measured, every deviation attributed
Model information
Measured capability matrix
September 5, 2026, 74 checks per line (the official lines used a 70K-token long-context variant to hold cost down):Reasoning effort
Same river-crossing puzzle on Responses, reasoning_tokens per line:Pricing
Official-relay groups (default / svip)
Two tiers by the input token count of each request; once input passes 272K the whole request bills at tier two, matching OpenAI:
Codex_Reverse group
0.5x the official price: tier one is $5.00 in / $25.00 out / $0.50 cached read / $6.25 cache write.Choosing a group
Examples
Responses endpoint (recommended)
Chat Completions endpoint (migrating existing code, no function tools)
Deviation attribution
Running the same matrix on three lines sorts every deviation into one of three buckets.Upstream limits (identical on all three lines)
Chat Completions has no function tools
Chat Completions has no function tools
tools returns 400 on both official lines, with upstream text telling you to use Responses; omitting reasoning_effort or adding tool_choice: required changes nothing. The Codex_Reverse group passes only because its pipeline converts to Responses internally, so do not treat that as evidence of capability. Use Responses for function calling.reasoning.effort max is echoed as xhigh
reasoning.effort max is echoed as xhigh
max echoed xhigh on all three lines. On the official lines max spends clearly more reasoning tokens than xhigh (OpenAI direct 278 to 379 vs 246, Azure 342 to 516 vs 320), so the level may apply with a normalized echo; on Codex_Reverse there is no difference. We promise four levels.Chat parameters: max_tokens and temperature return 400
Chat parameters: max_tokens and temperature return 400
max_tokens with 400 and ask for max_completion_tokens; temperature returns 400 unsupported, as usual for reasoning models. Codex_Reverse accepts both and ignores them. Strip both when migrating existing code.Codex_Reverse group only (5 items)
1. Chat drops system messages entirely
1. Chat drops system messages entirely
developer message hit 3/3; both official lines pass system 3/3. Use developer on Chat, which works on all three lines.2. None of the three output-cap parameters are enforced
2. None of the three output-cap parameters are enforced
max_output_tokens: 20, max_tokens: 20, or max_completion_tokens: 20, output was 403 tokens, and Responses echoed max_output_tokens: null. The official lines truncate correctly at 20 with incomplete / length. Use the official-relay groups when caps matter for cost control.3. previous_response_id is silently ignored
3. previous_response_id is silently ignored
store: true still echoes false, and the second turn returns 200 with no memory of the first; both official lines recall correctly. In this group keep history on the client and pair it with include: ["reasoning.encrypted_content"] for stateless replay (verified on all three lines). GET /v1/responses/{id} returns 503 everywhere.4. Chat silently drops image URLs
4. Chat silently drops image URLs
Azure line only (1 item)
web_search temporarily disabled
web_search temporarily disabled
web_search / web_search_preview on the Azure line return 400 with a gateway notice that web_search is temporarily disabled while Azure Bing billing is under review, and that other tools are unaffected. The OpenAI direct line and the Codex_Reverse group work normally. This page will be updated when it is restored.Migration guide
From gpt-5.6-sol
From gpt-5.6-sol
model field. On Chat, anything using tools must move to Responses, and strip max_tokens and temperature. The price is 2.5x Sol’s current promotional rate ($4 / $20 → $10 / $50), so run a head-to-head on agent, automation, and complex engineering tasks first; leave everyday chat, classification, and extraction on Terra / Luna.From Chat Completions to Responses
From Chat Completions to Responses
messages → input, reasoning_effort → reasoning: {"effort": ...}, response_format → text: {"format": ...}, system → instructions, max_completion_tokens → max_output_tokens. Tool definitions flatten from {"type": "function", "function": {...}} to {"type": "function", "name": ..., "parameters": ...}. Full mapping in the Responses migration guide.Controlling long-context cost
Controlling long-context cost
Will security tasks be refused?
Will security tasks be refused?