GPT Image 2.5 Flare & Sunburst are live on EvoLinkTry GPT Image 2.5

GPT-6 Sol API

OpenAILanguage ModelAvailability watch
Access unverifiedPrice unpublishedModel ID unverifiedLaunch alerts
EvoLink access
Not verified
Official model ID
Not found in checked catalog
Pricing
Not published
Last checked
2026-09-20

Can you use the GPT-6 Sol API?

As of September 20, 2026, GPT-6 Sol is not listed in the OpenAI model catalog or pricing page we checked. EvoLink access has not been verified. For teams using GPT-5.6 Sol, this page tracks the integration contract to check before moving agent traffic: exact identity, supported controls, billing and a tested fallback.

GPT-6 Sol access status

Checked September 20, 2026. Product announcements, upstream API access and EvoLink access are separate milestones.

We will update the integration status when model-specific documentation and EvoLink request and billing verification are available.

Get the GPT-6 Sol API availability alert

Get notified when EvoLink access is verified. An upstream announcement alone does not activate this route.

Register your email

EvoLink product alerts. No access, capacity or release date is guaranteed.

Follow product updates EvoLink Discord

Know what you can actually call

The launch update should include the verified route, current rate and integration documentation so you can evaluate the model with your own tasks.

Prepare to evaluate GPT-6 Sol

These are preparation steps, not confirmed capabilities or benchmark results for the candidate.

1

Save a Sol baseline

Keep a fixed repository revision, issue, test command and tool permissions for each task. Record whether GPT-5.6 Sol produces an accepted patch, how often a reviewer intervenes and the total billed usage.

2

Inventory your request contract

List the endpoint, reasoning effort, structured output schema, streaming events and tools your agent actually uses. Check each against the new route when documentation and access become available.

3

Define an upgrade threshold

Choose your acceptance tests and maximum cost per accepted task before evaluating a candidate. Separate patch quality from time to the first token; a quick answer can still leave an unfinished repair.

4

Keep rollback independent

Store model selection outside prompts. Keep the measured existing route available and require review before replaying any tool operation that could already have changed external state.

GPT-6 Sol pricing and request contract

FieldCurrent statusBefore switching
Exact request IDNot verifiedDocumented ID and returned model identity
EvoLink pricingNot verifiedToken categories, cache, tools and billing record
Endpoint and controlsNot verifiedRequired tools, streaming, schema and reasoning settings
Limits and reliabilityNot verifiedContext, output, concurrency, retry and fallback behavior

While waiting for GPT-6 Sol: three model options

Keep work moving with a model matched to the task: retain your Sol baseline, evaluate Astra for difficult end-to-end work, or test Luna for routine preprocessing. Use the linked product pages for current EvoLink access and pricing, and compare cost per accepted task before changing traffic.

GPT-5.6 Sol · Keep your agent baseline

Use your existing Sol workflow for repository fixes, code review and tasks with several tool steps. Save the same repository revision, tool permissions and acceptance tests for the future GPT-6 Sol trial. Measure accepted patches, reviewer interventions and total cost including retries.

View GPT-5.6 models and pricing

GPT-6 Astra · Evaluate difficult tasks

Consider Astra when a task needs complex reasoning, coding and research across several steps. Trial the failures your current Sol workflow cannot resolve, then compare completion quality and total cost. Astra is a separate model; its availability and results do not establish anything about GPT-6 Sol.

View GPT-6 Astra access and pricing

GPT-5.6 Luna · Test routine preprocessing

Test Luna for issue classification, extracting fields from logs and organizing inputs before the main agent task. Validate those outputs before passing them to Sol, and send ambiguous cases to review. Measure whether the extra routing step reduces total cost without increasing downstream errors.

View GPT-5.6 tiers and pricing

GPT-6 Sol: next steps

GPT-6 Sol API FAQ

What is the GPT-6 Sol API model ID?

No GPT-6 Sol request ID was found in the OpenAI catalog checked on September 20, 2026. This page address is not a verified API ID. Use only the exact identifier published for your chosen provider after access is verified.

What will GPT-6 Sol cost on EvoLink?

No verified EvoLink rate is available for this model. GPT-5.6 Sol and GPT-6 Astra prices do not determine a future Sol rate. Check this page for the model-specific rate after verification.

Can I keep my current OpenAI-compatible client?

EvoLink provides a unified API gateway, but this candidate route has no verified request contract yet. Confirm the endpoint, streaming events, tool arguments and supported controls before assuming client compatibility.

Will my existing Sol tools and reasoning effort work?

That remains unverified for GPT-6 Sol. Record your current settings now, then test each required feature on the exact candidate route. Upstream feature listings do not automatically prove gateway support.

Does subscribing grant early access?

No. The form registers an EvoLink availability alert. It does not grant OpenAI access, reserve capacity or guarantee a launch date.

How should I compare it with GPT-5.6 Sol?

Use the same repository tasks, permissions and acceptance tests. Compare complete task success, reviewer interventions, latency and cost including failed attempts. The linked upgrade guide supplies an evaluation plan, not new-model benchmark results.