MODEL PROFILE · OpenAI
GPT-6.1 Sol
A distinct Sol version for text and image-input tasks. Check reasoning and tool-calling compatibility before replacing an earlier endpoint.
Source reviewed: · Language model
Provider documentation summary. No hands-on results or independent ranking are claimed.
Documented facts
The following fields come from the official provider source, reviewed on the date above.
- Identity and API
- gpt-6.1-sol; hosted Responses and Chat Completions. Tool calling requires Responses.
- Modalities
- Text and image inputs; text output. Audio and video are unsupported; image generation is a separate tool.
- Limits
- 1,050,000 context tokens; maximum input 922,000; maximum output 128,000. Knowledge cutoff April 30, 2026.
- Reasoning
- low, medium (default), high, xhigh, max. Neither none nor minimal is supported.
- Standard token pricing
- USD per million tokens: input $2; cached input $0.10; cache writes $2.50; output $10.
- Long requests
- Above 272K input tokens, the full request uses 2× input/cache and 1.5× output rates.
- Processing tiers
- Fast: 2× Standard; Batch/Flex: 50% less. Regional processing: 10% premium where available.
- Restrictions
- Fine-tuning unsupported. US/EU residency supported; Fast unavailable with EU residency. Downloadable weights and weight licensing are not established.
Launch access and version boundary
OpenAI announced GPT-6.1 Sol on September 29 for the API and for Work and Codex on Plus, Pro, Business, Enterprise and Edu. Its announcement explicitly excludes Chat for now and describes Sol Ultrafast as forthcoming. Keep this version separate from GPT-6 Sol and from Astra speed tiers. Official launch and availability.
The practical decision
Treat a version switch as a compatibility change before treating it as a quality upgrade. A caller that previously disabled reasoning must choose a supported setting, and a Chat Completions integration that depends on tool calls needs a different route. First test request construction and tool execution using retained inputs; then compare whether the final answer meets the same acceptance criteria. This sequence helps separate an integration failure from an answer-quality difference. It is an evaluation plan, not a report of tests performed here.
What to record in your own comparison
- Record the exact model identifier, endpoint, reasoning effort and tool configuration alongside each saved output.
- For cost comparisons, count failed attempts and tool usage as well as successful output. Separate cache reads from writes and preserve the input length.
- Use representative document and coding tasks with fixed requirements. A larger context limit does not prove that every detail in a long input will be used correctly.
Limitations and unknowns
This profile reports provider documentation and contains no independent quality, speed or accuracy measurements. Listed token rates are not subscription charges. A supported API feature does not establish that every account, interface or region exposes it. The profile does not infer downloadable weights or an open-source license.
Compare your saved results
Use the DualView editor to inspect files you already have. The accepted-output calculator uses your own rates and counts. Neither link runs a model or purchases generation.