Model ID and API Format
As of July 28, 2026, no GPT-6 request ID is documented in OpenAI's public model catalog or API docs. Treat unverified `gpt-6` strings in code samples as placeholders, not production configuration.
EvoLink plans to add GPT-6 after OpenAI publicly releases the model and the route passes verification. Join the launch alert for the confirmed model ID, pricing, limits, and access details. OpenAI has not announced a product named GPT-6, so no callable route is available today.
GPT-6 API is coming soon to EvoLink as a planned route, pending public release and verification. This independent alert is not an OpenAI waitlist, early-access application, API allocation, or guarantee of access.
EvoLink product launch alerts only. No OpenAI affiliation, early-access promise, access guarantee, or spam.
Want faster updates? Join the EvoLink Discord
After EvoLink verifies and approves a public route, this page will publish the request model ID, live EvoLink pricing, API compatibility, regions, limits, and migration guidance for the unified API.
These are the fields developers need before integration. None has been published; every circulating figure — 1.5M context, 10T-scale training, specific prices — is an unconfirmed leak. EvoLink will fill these fields only after official publication and route-level verification.
As of July 28, 2026, no GPT-6 request ID is documented in OpenAI's public model catalog or API docs. Treat unverified `gpt-6` strings in code samples as placeholders, not production configuration.
No GPT-6 pricing exists. The only verified OpenAI flagship reference is GPT-5.6: Sol $5/$30, Terra $2.50/$15, Luna $1/$6 per 1M tokens.
Leaks claim 1.5M+ tokens; no official context length, maximum output, or effective long-context result exists.
Regions, concurrency, quotas, rate limits, and 429 behavior require a callable production route.
As of July 28, 2026, EvoLink found no verifiable GPT-6 route in OpenAI's public docs or the major aggregator catalogs reviewed. Require public model documentation and a reproducible successful request before treating any offer as GPT-6.
Only real workloads on a real API route can answer that. These six user-demand metrics are what EvoLink will verify after access opens; they are not confirmed GPT-6 capabilities.
Measure whether bug fixes, multi-file refactors, and test tasks actually pass instead of judging one response.
Track argument errors, repeated calls, unproductive loops, and how often a person must take over.
Test whether the model keeps constraints, finds evidence, and completes work deep inside large repositories and documents.
Long-term memory is the direction OpenAI leadership has emphasized for the next generation, but no API-level memory specification exists to test yet.
Evaluate time to first token, end-to-end speed, capacity, error rate, and peak-hour 429 responses.
Include token use, retries, failed runs, and human correction instead of comparing list prices alone.
There is no verified GPT-6 API, price, or test result, and even the name is unconfirmed. Secondary coverage associated codename Spud with an expected GPT-6 before that model launched as GPT-5.5; OpenAI did not confirm the label. Teams should not delay a project that can ship on GPT-5.6 today.
If delivery matters now, establish a real baseline on the documented and callable GPT-5.6 route — Sol, Terra, or Luna by workload.
Upgrade only when your workloads show a verified improvement in completion rate, reliability, or cost per accepted task on a real route.
Keep the current model behind EvoLink's unified API, then add GPT-6 by configuration after validation without rebuilding another provider integration.
Check the release evidence and decide whether to wait or build on today's models.
The verified OpenAI signal timeline, graded rumors, and debunked fakes — updated as evidence changes.
Why building on GPT-5.6 now with a configurable model ID beats waiting for an unannounced date.
How the rumored next OpenAI flagship stacks up against Anthropic's shipping frontier model.
No. As of July 28, 2026 there is no announcement, model card, or API documentation. OpenAI has confirmed only that a stronger unnamed pre-release model exists.
Unconfirmed. Secondary coverage associated codename Spud with an expected GPT-6 before the model launched as GPT-5.5 in April 2026; OpenAI did not publicly confirm that label. This page treats GPT-6 as a search term, not a settled product name.
No. EvoLink has not published a callable route, model ID, pricing, or production support claim for GPT-6.
EvoLink plans to add a GPT-6 route after OpenAI publicly releases the model and the route passes compatibility, pricing, limit, and production checks. Coming Soon does not mean the API is callable today.
No public OpenAI GPT-6 enrollment or waitlist has been identified. EvoLink's form is an independent release alert, not an OpenAI waitlist, early-access application, API allocation, or guarantee of access.
No official date exists. Leaks and prediction-market contracts offer changing, conflicting windows; none is an OpenAI schedule.
As of July 28, 2026, no GPT-6 request ID is documented in OpenAI's public model catalog or API docs. Do not infer one from this page's URL or use an unverified sample ID in production.
Pricing is not published. This page will use EvoLink's live pricing module only after the route and SKUs are approved. The verified reference today is GPT-5.6's three tiers.
Memory and personalization are the direction OpenAI leadership has publicly emphasized, but no GPT-6 memory specification, retention policy, or API detail exists.
No. Keep the supported GPT-5.6 route until GPT-6 has comparable verified facts and passes offline, shadow, canary, and rollback gates.
An independent notification after EvoLink verifies a public release, model ID, pricing, route behavior, and access state. It does not provide or guarantee OpenAI early access.