Grok 4.7 Is Live: A 2.1T Base Model at the Same Price

​

Key Takeaways

• New flagship, live now: Grok 4.7 shipped on September 21, 2026 and is live on APIYI as grok-4.7, available in the default / svip / CodexResponses groups
• A bigger base model: 2.1T parameters, about 40% larger than Grok 4.6’s 1.5T, with a longer reinforcement learning run weighted toward tasks that take hours
• Biggest gains in coding agents: independent testing by Artificial Analysis puts Terminal-Bench 4.0 at 33% (up from 18%) and DeepSWE v1.1 at 73% (up from 65%)
• Same price as the last generation: $2 / $6 per million tokens (input / output), $0.50 for cached reads, with a second tier above 200K, matching xAI’s official pricing
• Same unit price, more tokens per task: Artificial Analysis measured roughly twice the output tokens of Grok 4.6 on the same task set, so cost per task goes up

​

Background

​

Detailed Analysis

​

Benchmarks

​

Core Features

​

Specifications

​

Practical Use

​

Recommended Scenarios

• Long-running coding agents: the largest gains are on long-task benchmarks such as Terminal-Bench and SWE-Marathon, a good fit for automation that works in a codebase for hours
• Knowledge-work agents: GDPval-AA and AA-Briefcase both rank second only to Claude Fable 5.1, a good fit for report writing, research, and analysis
• Engineering and hardware questions: training included SpaceX engineering material, and it does well on the EEBench electrical-engineering benchmark
• Codex and other Responses clients: available in the CodexResponses group for use directly in Codex

​

Code Example

import openai

client = openai.OpenAI(
    api_key="sk-your-apiyi-key",
    base_url="https://api.apiyi.com/v1"
)

response = client.chat.completions.create(
    model="grok-4.7",
    messages=[
        {"role": "user", "content": "Read this module, find potential concurrency bugs, and propose fixes"}
    ]
)
print(response.choices[0].message.content)

​

Best Practices

• Pick the reasoning level per task: low or medium saves noticeably on simple Q&A; keep xhigh for long coding chains and complex analysis
• Don’t hard-code reasoning parameters in cross-model code: support for reasoning-effort parameters varies across Grok 4.x models, so shared wrappers should check the model before sending it; see Chat and reasoning
• Watch the 200K tier on long prompts: requests above 200K are billed entirely at the second tier, so split long documents where you can and let prefix caching absorb repeated system prompts

​

Pricing and Availability

​

Pricing

​

Stack With Top-Up Promotions

​

Summary