Grok 4.7 Reality Check: Musk Targets About September 12, but xAI Has No Model ID, Price or Benchmark Yet
Elon Musk says Grok 4.7 is due in about 10 days from September 2, but xAI still has no official 4.7 model page, API ID, pricing or benchmark table. We separate founder claims from shipped evidence.
Status on September 9, 2026
Grok 4.7 is not an officially shipped xAI model yet. Elon Musk posted on X on September 2, 2026 that “Grok 4.7 comes out in 10 days,” which points to roughly September 12 if the estimate holds. That is a founder timetable, not an xAI release-note commitment.
Original post:
At verification time, xAI's current developer release notes still list Grok 4.6 as the newest numbered text model, with no Grok 4.7 entry. xAI's official Grok 4.6 page likewise describes 4.6 as its current frontier model and provides a callable model ID, benchmark table, availability and pricing that do not yet exist for 4.7.
Official shipped references:
The practical rule is simple: do not treat a model as generally available until xAI publishes an official model identifier, access route and current documentation or the endpoint is independently callable.
What Musk has claimed about Grok 4.7
The public 4.7 story currently comes from Musk's posts rather than an xAI model card.
On July 28, Musk described Grok 4.7 as a 2.1-trillion-parameter model that would follow Grok 4.6 and said it should be better than 4.6 in every way except serving somewhat more slowly, while using tokens more efficiently. Contemporary reporting preserved that statement, but xAI has not published a 4.7 architecture or parameter-count document.
On August 12, after Grok 4.6 shipped, Musk said Grok 4.7 was significantly better, should be ready in three to four weeks, and that initial training was complete while supplemental training was adding a large amount of SpaceX company data.
Claim-tracking references:
Those details should be labeled founder claims until xAI publishes a technical specification. Parameter count alone also does not establish quality: architecture, active parameters, data, post-training, reasoning policy, serving stack and harness can matter more than a headline total.
The release timetable has moved before
The September 2 “10 days” statement is more specific than the earlier windows, but the historical trail is still important.
Musk first described 4.7 as following 4.6 by a few weeks. On August 12 he gave a three-to-four-week estimate. On September 2 he narrowed that to 10 days. Grok 4.6 itself landed on August 12, later than the earlier around-August-7 target reported in July.
That does not prove the September estimate will slip. It does mean developers should distinguish a target from availability and avoid planning a production migration around an unshipped model.
What is actually known from Grok 4.6
Grok 4.6 is the useful production baseline because xAI has documented it.
The official 4.6 docs list:
- model ID:
grok-4.6 - 500,000-token context window
- text and image input with text output
- reasoning effort levels low, medium, high and xhigh
- short-context API pricing of $2/M input, $0.50/M cached input and $6/M output
- higher pricing above the 200K-prompt threshold: $4/M input, $1/M cached input and $12/M output
- availability through xAI's API plus several partner surfaces
None of those values should be copied to Grok 4.7 unless xAI confirms them.
Musk's statement that 4.7 will be “slightly slower to serve” is not a latency benchmark. No TTFT, output-tokens-per-second distribution, concurrency test or hardware-normalized serving measurement for 4.7 has been published.
Benchmark hygiene: there is no Grok 4.7 scorecard yet
No reliable Grok 4.7 benchmark table was found in xAI's current news, release notes or model documentation at verification time. That means there is no defensible basis yet for a 4.7 ranking against GPT-6 Astra, Claude Fable 5.1, Claude Opus 5, Gemini or other frontier systems.
The distinction between benchmark families matters:
SWE-bench Verified: no Grok 4.7 result was found. Do not infer one from another Grok version or from a different coding benchmark.
SWE-bench Pro: no Grok 4.7 result was found. xAI previously reported a SWE-bench Pro result for Grok 4.5, but that older model's score is not evidence for 4.7.
Terminal-Bench: no Grok 4.7 result was found. xAI's Grok 4.6 launch table reports 26% on Terminal-Bench v3.0. That result belongs to 4.6 and that benchmark revision; it cannot be transferred to 4.7 or compared casually with Terminal-Bench 2.1 or 4.0 results.
DeepSWE: xAI reports 65.9% on DeepSWE v1.1 for Grok 4.6. Again, this is a 4.6 result, not a prediction of 4.7.
A future 4.7 comparison should record the exact benchmark revision, task count, harness, reasoning effort, retry/pass policy, tool access, date, who ran the evaluation and whether the result is vendor-reported or independently reproduced.
Why the SpaceX-data claim needs careful interpretation
Musk says supplemental training is using a large amount of SpaceX company data and has linked that to expected strength in “real-world engineering.” That is a plausible training hypothesis, not evidence of measured engineering superiority.
Until xAI publishes data-governance detail, evaluation methodology and reproducible results, several questions remain open:
- what categories of SpaceX data were included;
- whether data are code, documents, telemetry, design artifacts, communications or some mixture;
- what filtering, deduplication and permission controls were used;
- whether evaluation tasks overlap with training data;
- whether gains generalize beyond aerospace-adjacent engineering.
The correct evidence standard is a pinned benchmark or controlled domain evaluation, not the uniqueness of the training corpus by itself.
Public reaction is mixed and anecdotal
Accessible public discussion shows both anticipation and skepticism, but it is not a benchmark.
A September 2 Reddit thread about the “10 days” post included users excited about a faster xAI release cadence and coding improvements, alongside users pointing to previous missed product timelines. A separate Grok community thread showed enthusiasm for coding but substantial concern that newer releases have become more heavily moderated or less useful for creative use cases.
Primary discussions:
- r/grok: “Elon says Grok 4.7 drops in 10 days” — September 2
- r/grok: Grok 4.7 discussion — September 2
These comments are self-selected anecdotes from a product community. They do not establish average user sentiment, model quality, safety quality or release reliability.
Practical decision: wait for four receipts
For developers and teams, the useful threshold is not another rumor. Wait for four concrete receipts:
- Official identity: an xAI model page or release note with the exact model ID.
- Access and economics: callable API or product access, context limits, pricing, rate limits and region availability.
- Benchmark provenance: separate SWE-bench Verified, SWE-bench Pro and Terminal-Bench evidence where applicable, with harness and revision details.
- Independent reproduction: third-party results or transparent artifacts that can test xAI's claims outside its own launch setup.
Until those appear, Grok 4.7 is best treated as a named upcoming model with a founder target around September 12, not as a released frontier system and not as a benchmark winner.
Bottom line
The strongest verified statement today is narrow: Musk says Grok 4.7 should arrive roughly September 12, while xAI's official developer surfaces still stop at Grok 4.6.
The 2.1T parameter count, improved token efficiency, slower serving and SpaceX-data engineering advantage remain founder-described claims. There is currently no official 4.7 model ID, price, context window, latency measurement, SWE-bench Verified score, SWE-bench Pro score, Terminal-Bench score or independent reproducible evaluation.
That gap is exactly why release tracking should keep identity, availability, benchmark evidence and public reaction as separate evidence states rather than collapsing them into one hype cycle.
This article is built from the source material below. Open the originals for full context and the latest updates.
