Grok 4.7 Release Date: What Is Confirmed?
Is Grok 4.7 out? The status by channel
A model can move through several release stages. An executive announcement, access in the Grok app and a documented developer API are different events. Using it through a gateway such as EvoLink means waiting for one more step: the gateway integration.
| What you want to know | Current situation (September 18, 2026) | What to do |
|---|---|---|
| Is Grok 4.7 real? | Yes. Musk has talked about it publicly several times, and the original posts are available | Worth following; you can start preparing an evaluation now |
| Is there a release date? | Not yet. The first target slipped and no new date has been announced | Do not plan a launch around a date circulating online |
| Can I call it through xAI's API? | Not yet. xAI's official model catalog has no Grok 4.7 entry | Wait for official docs with the model ID and how to call it |
| Is it in the Grok app? | No official information shows it has opened | Even if the app gets it, the API may not open at the same time |
| Can I call it on EvoLink? | Not yet. This page will be updated as soon as it is integrated | Join the update list; do not send requests with a guessed model ID |
This information comes from public sources, checked on September 18, 2026. It does not rule out private testing or a limited rollout that xAI has not announced.
The pre-announcement and delay, with original sources
The source sequence matters more than a countdown copied from another article.
| Source sequence | What the statement adds | What it leaves unresolved |
|---|---|---|
| Initial target | A public intention to ship the candidate | Whether that target will be met |
| Delay explanation | A reason to stop treating the initial window as certain | A firm replacement date |
| Later model comparison | A suggested reference point for evaluation | Reproducible results, final specifications and access |
What remains unconfirmed
There is no official information yet on a formal model ID, Grok 4.7 pricing, supported context, output limits, tools or public benchmark results. Grok 4.6 values cannot fill those fields just because the version numbers are adjacent.
Reports about parameter counts, training data or lower token use may explain the attention around the model. They do not answer whether your application can call it, how a request is billed or whether it finishes your task correctly. Keep those reports out of a production configuration and out of a confirmed specification table.
A third-party SDK entry or reported cloud quota row also needs context. Software libraries and administrative interfaces can prepare for a model before customers can use it. What you are really waiting for is an API stated in the official docs that your account can use, with a clear model ID and applicable terms.
What would confirm a release for your workflow?
Start by matching the evidence to the channel you need. If you are building an API product, app access alone does not resolve your dependency. If you intend to use EvoLink, an upstream launch still means waiting for EvoLink to finish its integration.
Knowing it is really usable comes down to four things: the official model ID, the documented way to call it, access for your account, and usage that reconciles with the applicable price. A first successful response starts the evaluation; it does not prove reliable capacity or compatibility with every tool in your application.
What you can prepare before the date is known
Choose a small set of tasks that exposes a real limitation in your current workflow. Save inputs, expected outcomes, mocked tool responses and acceptance rules together. Record current task completion, elapsed time and cost including retries. That gives you something concrete to compare when Grok 4.7 becomes testable.
Update record
FAQ
When will Grok 4.7 be released?
As of September 18, 2026, there is no official firm release date. Musk first gave a target, then followed it with a delay statement.
Why was Grok 4.7 delayed?
Musk described unfinished work around difficult-task completion and checking results. That is his explanation, not an independently reproduced diagnosis.
Is the ten-day announcement still a useful countdown?
It is useful historical evidence of an intended window. After the delay, it should not be used as a guaranteed future date.
Does a cloud listing mean the API is live?
A listing or quota row alone does not show that the API can be called, who can use it, what the model ID is or how it is billed. Go by the official documentation and the channel you actually use.
Can I use an ID from a third-party SDK?
Do not assume it is an official or working request value. Once the API is officially open, use the model ID given in the official documentation.
Will Grok 4.7 replace Grok 4.6 immediately?
A successor announcement does not establish a retirement or migration requirement. Keep a working 4.6 baseline and test a candidate before moving workloads.
Will xAI app access and EvoLink access arrive together?
That is not known yet. Consumer access, the provider API and EvoLink integration must be tracked separately.
