Grok 4.7: What xAI's New Model Changes (Pricing, Benchmarks, API)
Grok 4.7 explained: same $2/$6 pricing as Grok 4.6, 500K context, higher coding scores, the 200K-token price cliff, and how to call it from the API.
Long Nguyen
Lập trình viên Fullstack · Kỹ sư AI · Nhà nghiên cứu
Grok 4.7 at a glance
xAI released Grok 4.7 on . The company (whose site and developer docs now carry the SpaceXAI name) positions it as its most capable model for coding and knowledge work, built on a larger base model than Grok 4.6 with extended reinforcement learning on hard tasks. The official Grok 4.7 announcement is the source for the launch claims and benchmarks below; API numbers come from xAI's developer docs.
The short version for anyone who builds on the API: it costs exactly the same as Grok 4.6, has the same 500K context window and the same rate limits, and scores higher on xAI's coding benchmarks. For most teams that makes it a model-ID swap, not a migration project.
| Spec | Grok 4.7 |
|---|---|
| API model ID | grok-4.7 |
| Release date | September 21, 2026 |
| Knowledge cutoff | May 2026 |
| Context window | 500,000 tokens |
| Input modalities | Text, image |
| Reasoning effort | low, medium, high, xhigh (default: high) |
| Tooling | Function calling, structured outputs |
| Rate limits | 150 requests/second, 50M tokens/minute |
| Batch API | Not supported |
| Where to use it | Grok API, Cursor, Grok Build, Grok iOS/Android apps, third-party harnesses, routers and cloud platforms |
What's new in Grok 4.7 compared with Grok 4.6
xAI's launch post names four changes. Read them as the vendor's claims; independent evaluations usually take a few weeks to appear.
- Bigger base model. Grok 4.7 is not a fine-tune of 4.6; it starts from a larger pretrained model.
- More RL on difficult tasks. Extended reinforcement learning aimed at long, multi-step coding and knowledge-work problems.
- Self-verification and long-context management. The model is trained to check its own work and keep track of state across long sessions, which is exactly where agent loops tend to fall apart.
- Native Grok Bot harness understanding. Better conversational behavior inside xAI's own agent harness.
What did not change matters just as much for production planning:
| Grok 4.6 | Grok 4.7 | |
|---|---|---|
| Input / cached / output (per 1M tokens, <200K) | $2.00 / $0.50 / $6.00 | $2.00 / $0.50 / $6.00 |
| Context window | 500K | 500K |
| Reasoning effort levels | low → xhigh, default high | low → xhigh, default high |
| Rate limits | 150 RPS, 50M TPM | 150 RPS, 50M TPM |
| CursorBench 4.0 (xAI-reported) | 40.4% | 46.3% |
Same price, same limits, same parameters, better score. There is no cost argument for staying on 4.6; the only reason to hold back is if your own evals show a regression on your specific prompts.
Grok 4.7 benchmarks: what the numbers say
All figures below are published by xAI in the launch post. None has been independently replicated at the time of writing.
| Benchmark | What it measures | Grok 4.7 |
|---|---|---|
| CursorBench 4.0 | Real coding tasks inside the Cursor editor | 46.3% (Grok 4.6: 40.4%) |
| DeepSWE v1.1 | Software-engineering agent tasks | 71.0% (high effort) |
| HealthBench | Clinical reasoning | 56.7% |
How to read this: the 5.9-point jump on CursorBench is the one number with a like-for-like 4.6 baseline, and it is roughly a 15% relative improvement on the task type most API customers actually run. The DeepSWE score is reported at high effort, which is also the API default, so you get that configuration without touching any parameter. Treat the rest as directional until third-party leaderboards catch up, and run your own eval set before trusting any vendor chart with a production decision.
Grok 4.7 API pricing, including the 200K-token cliff
The headline price is $2 input / $6 output per million tokens, but the xAI API pricing page has a second tier most launch coverage skips: once a prompt reaches 200K tokens, every rate doubles.
| Per 1M tokens | Prompt below 200K | Prompt at or above 200K |
|---|---|---|
| Input | $2.00 | $4.00 |
| Cached input | $0.50 | $1.00 |
| Output | $6.00 | $12.00 |
Server-side tools are billed per call on top of tokens: web search, X search and code execution each cost $5 per 1,000 calls. The US regional endpoint (us.api.x.ai) runs at 1.1× the global token rates, which matters if you need data residency.
Worked example: one agent step
Take a typical coding-agent turn: a 150K-token prompt (system prompt, tool schemas, repo context) and 8K output tokens.
| Scenario | Cost per call |
|---|---|
| 150K input, no cache hits, 8K output | $0.348 |
| 150K input with 120K served from cache, 8K output | $0.168 |
| 250K input (long-context tier), no cache, 8K output | $1.096 |
| Same 250K split into two 125K calls, 8K output each | $0.596 |
Two takeaways. First, cache hits halve the bill here, so keep your stable prefix (system prompt, tool definitions, pinned files) byte-identical at the front of every request. Second, the 500K window is real but expensive: sending the same 250K tokens in one call costs about 84% more than splitting it into two calls under the line. If your agent can retrieve or summarise instead of stuffing the whole repo in, stay under the line.
Grok 4.7 Fast: same model, twice the speed, twice the price
xAI also ships Grok 4.7 Fast. According to the pricing docs it is the same Grok 4.7 model served on faster infrastructure, at twice the standard token rates ($4 input / $1 cached / $12 output per million below 200K). The catch: it is only available inside Cursor and Grok Build, not on the public API. If you are building your own product, standard grok-4.7 is the only option, and you tune latency with the reasoning-effort setting rather than a faster tier.
How to call Grok 4.7 from the API
xAI's REST API follows the OpenAI specification, so the official OpenAI Python SDK works by pointing it at xAI's base URL. Switching an existing Grok 4.6 integration is a one-line change to the model ID.
from openai import OpenAI
import os
client = OpenAI(
api_key=os.environ["XAI_API_KEY"],
base_url="https://api.x.ai/v1",
)
resp = client.chat.completions.create(
model="grok-4.7",
messages=[
{"role": "system", "content": "You are a senior Django reviewer."},
{"role": "user", "content": "Find the N+1 query in this view: ..."},
],
)
print(resp.choices[0].message.content)
# Reasoning tokens are billed as output tokens; track them per call
usage = resp.usage
print("prompt:", usage.prompt_tokens,
"completion:", usage.completion_tokens,
"reasoning:", usage.completion_tokens_details.reasoning_tokens)
Three production notes the quickstart does not spell out:
- Log reasoning tokens. At the default high effort, hidden reasoning can easily outweigh the visible answer, and it bills at the output rate. The
reasoning_tokensfield is how you find out which endpoints are quietly expensive. - Drop effort for cheap tasks. Classification, extraction and routing rarely need high. Test low or medium on those paths and keep high/xhigh for code generation and multi-step planning.
- No Batch API. Grok 4.7 does not support batch processing, so bulk offline jobs (backfills, large-scale tagging) run at full synchronous prices. Budget for that, or route those jobs to a model that offers batch discounts.
If you are wiring Grok 4.7 into agents, document pipelines or internal tools and want the cost controls built in from day one, that is the kind of work Netalith does under AI automation and workflow development.
Should you switch to Grok 4.7?
| Your situation | Recommendation |
|---|---|
| Already on Grok 4.6 via API | Switch. Identical price and limits; run your eval set first, then change the model ID. |
| Using Cursor or Grok Build for coding | Try Grok 4.7; pick Fast only if latency is costing you more than the 2× token price. |
| Long-document workloads over 200K tokens | Works, but budget for doubled rates. Test chunking or retrieval first. |
| Bulk offline processing | Weak fit because there is no Batch API. |
| Need data in the US region | Use us.api.x.ai and add 10% to your cost model. |
Grok 4.7 is an incremental release, not a new generation, and that is its strength for builders: a measurable coding gain with zero pricing or integration churn. The real work is the same as with any model upgrade: keep an eval set, watch reasoning-token spend, and keep prompts under the 200K cliff unless the task truly needs more.
Not sure whether your product or content is ready for AI assistants like Grok to find and cite it? Book a free AI visibility consultation with Netalith. No cost, no account needed.
CÂU HỎI THƯỜNG GẶP
Câu hỏi thường gặp
When was Grok 4.7 released?
xAI released Grok 4.7 on September 21, 2026. It is available in the Grok API, Cursor, Grok Build, the Grok iOS and Android apps, and through third-party harnesses and cloud platforms.
How much does Grok 4.7 cost?
Grok 4.7 costs $2 per million input tokens, $0.50 per million cached input tokens and $6 per million output tokens for prompts under 200K tokens. At 200K tokens and above the rates double to $4, $1 and $12.
What is the Grok 4.7 context window?
Grok 4.7 has a 500,000-token context window, the same as Grok 4.6. Prompts of 200K tokens or more are billed at the long-context rate.
Is Grok 4.7 better than Grok 4.6?
On xAI's own benchmarks, yes: Grok 4.7 scores 46.3% on CursorBench 4.0 versus 40.4% for Grok 4.6, at the same price and rate limits. Independent results were not yet available at launch.
What is Grok 4.7 Fast?
Grok 4.7 Fast is the same Grok 4.7 model on faster infrastructure at twice the standard token rates. It is only available in Cursor and Grok Build, not on the public xAI API.
What is the Grok 4.7 model ID in the API?
Use the model ID grok-4.7 with xAI's OpenAI-compatible API at https://api.x.ai/v1. Reasoning effort supports low, medium, high and xhigh, with high as the default.