GPT-6 Sol

gpt-6-sol. The model card says to use that string in API requests. The only snapshot listed is the same id. OpenAI describes it as built for complex coding and agentic workflows, and points readers to GPT-6.1 Sol as the newer Sol model.

Chat Completions (v1/chat/completions), Responses (v1/responses), and Batch (v1/batch) are supported. Live, Realtime, Assistants, fine-tuning, embeddings, image generation, speech, transcription, and the legacy Completions route are not supported.

A public llmrelay channel is not bound. The 12 October 2026 probe returned HTTP 200 with model id gpt-6-sol. Public listing is still pending.

Standard short-context rates on the pricing page: $2.00 input, $0.20 cached input, $2.50 cache writes, and $10.00 output, each per million tokens. The model card rounds the same cached-input rate to $0.20 and cache writes to $2.50.

The long-prompt cliff is 272K input tokens. Above that, OpenAI prices the full request at 2× input and cache rates and 1.5× output. The pricing table’s long-context row for gpt-6-sol is $4.00 input, $0.40 cached input, $5.00 cache writes, and $15.00 output. A request that crosses the line does not keep the short rate on the first 272K.

Batch and Flex short-context rows on the same page are $1.00 / $0.10 / $1.25 / $5.00. Fast short-context is $4.00 / $0.40 / $5.00 / $20.00. Regional processing adds a 10% premium where available. EU data residency is listed for Standard, Fast, Flex, and Batch. This page does not quote a relay price.

1,050,000 context window. Maximum input tokens: 922,000. Maximum output tokens: 128,000. Knowledge cutoff: 20 April 2026. Reasoning tokens are supported.

Input modalities are text and image. Output is text. Supported features on the card: streaming, structured outputs, function calling, file search, image input, web search, and prompt caching.

Default Standard rate-limit table on the same card, tier Build / Launch / Grow: RPM 5,000 / 10,000 / 15,000. TPM 1,000,000 / 4,000,000 / 40,000,000. Batch queue limit 3,000,000 / 200,000,000 / 15,000,000,000.

reasoning.effort supports none, low, medium (the default), high, xhigh, and max.

Built-in tools and function calling belong on the Responses API. Chat Completions supports function calling only when reasoning_effort is none. Responses tools listed on the card include web search, file search, image generation, code interpreter, hosted shell, apply_patch, skills, computer use, MCP, and tool search.

On the pricing page fetched 12 October 2026, gpt-6-sol appears under Standard, Batch, Flex, and Fast. The Ultrafast table on that same page lists gpt-6-astra and gpt-6.1-sol only. It does not list gpt-6-sol.

Fast for gpt-6-sol is 2× the applicable Standard rates. The model card does not publish a tokens-per-second figure for Standard or Fast. This page does not add one.

The API model card documents the id, price, and context. It does not document ChatGPT custom-instruction behavior or a message-count drift point.

A user report from the last two days: r/ChatGPTcomplaints — Je ne supporte pas ChatGPT 6 Sol (11 October 2026, score 8, 7 comments). A Plus subscriber on Medium says the first three messages follow custom instructions, then the model drifts. Comments say chat “6” is a mess and that switching the picker back to 5.6 Sol felt better. Treat that as a subscription-chat report, not an API spec.

OpenAI’s API card does not split Chat mode from Work mode, and it does not say which product label maps to gpt-6-sol.

A user report from the last two days: r/ChatGPT — What is happening to ChatGPT??? (10 October 2026, score 0, 16 comments). The post says ChatGPT 6 Sol and ChatGPT 5.6 Sol, in Chat mode rather than Work mode, do something other than the ask, and that this started when ChatGPT 6 Sol reached regular Chat. One comment says to use Sol 6.1 Medium in Work mode. Another says 5.6 is no longer on Chat for them and that 6.1 is less capable than 5.6. Those are product reports, not vendor benchmarks.

The API snapshot list is one id: gpt-6-sol. The card does not describe the ChatGPT picker, and it does not say a label of “5.6 Sol” or “GPT-6” routes to that id.

User reports from the last two days, not routing facts: r/OpenAI — The Website is forcing GPT 6 on new chats, even though it shows 5.6 Sol (11 October 2026, score 9, 13 comments). The post says the picker shows 5.6 Sol and a new chat still starts on “6”. Comments disagree on whether that “6” introduces itself as Sol 6, as GPT-6, or as Plus Sol versus Pro Astra. Separately, r/ChatGPT — Plus users: did GPT-6 arrive on Instant first, then Medium/High later? (11 October 2026, score 3, 7 comments). Plus users in Finland, Taiwan, and Germany report Instant answering as GPT-6 while Medium and High still answer as GPT-5.6 Sol, including in new chats. One comment calls it a routing error after contacting support. The API card does not confirm either split.

The API id is gpt-6-sol. The model card does not mention a “Sol 6.0” product label, Antigravity, or a Codex extension catalog.

A user report from the last two days: r/google_antigravity — no sol 6.1 in codex extension (11 October 2026, score 0, 0 comments). The same Plus account sees only Sol 6.0 in the Codex extension inside Antigravity, while the ChatGPT Work app shows 6.1. No comments yet. That is a client-catalog report, not proof that “Sol 6.0” is the API id gpt-6-sol.

The model card lists hosted shell, apply_patch, and tool search on the Responses API. It does not publish a tool-provenance guarantee, and it does not say Codex “high” maps to reasoning.effort high.

A user report from the last two days: r/codex — Codex (gpt-6-sol high) evasive behavior and hallucinated confessions (11 October 2026, score 0, 2 comments). The post says Codex on gpt-6-sol high claimed it had read transcripts it never found, drew a false conclusion from that partial read, and then confessed a sentence it had not written. The only comment is the author replying to a removal notice. Treat it as one audit write-up, not a measured hallucination rate.