Grok 4.7 API pricing

xAI's newest Grok release. Available at listed at platform rate (no published official USD price).

USD, standard tier, verified 2026-09-26.

Specifications

What Grok 4.7 costs at your volume

Calculated at $1 input / $3 output per 1M tokens, assuming a 5:1 input-to-output ratio. Your ratio decides the real number — run your own figures through the cost calculator.

When Grok 4.7 is the right call

At $1 per million input tokens this sits in the mid-range band. It is a good fit for the everyday mix — agent loops, chat assistants, code editing, and anything interactive where latency and quality both matter.

It is usually the wrong call for either extreme: trivial bulk jobs that a cheaper model handles identically, or the hardest reasoning tasks where a flagship earns its premium.

Where Grok 4.7 sits in the index

One model, three rankings — because the model that is cheapest per input token is frequently not the cheapest per task. Output tokens cost a median of 4.0× what input costs across these 216 models, so a workload that generates more than it reads flips the order. Percentile is the share of models that cost more than this one.

On an agent mix the lowest blended rate in the same index is Gemma2 9B It at $0.01 per 1M tokens — about 250.0× less than this model at the same ratio. That gap is what the re-ranked index exists to show: sorting by input price alone can put a model 68 places out.

Inside xAI's 27 listed models, Grok 4.7 is 18 of 27 on the same agent mix, between Grok 4 1 Fast Non Reasoning at $0.2125 and Grok 2 Vision 1212 at $10.00 per 1M blended tokens. Most real decisions are made inside one vendor's range rather than across the whole index — see the full xAI range.

Similarly priced alternatives

Blended comparison (input + output per 1M). Price is one axis — the models above are not interchangeable, they are the ones worth testing side by side at this budget.

Calling Grok 4.7

The identifier you send is grok-4.7 — copy it exactly, because a mismatch returns a model error rather than a connection error, which sends most people to debug the wrong thing. Everything else is a base URL argument; official SDKs work unchanged.

from openai import OpenAI

client = OpenAI(base_url="https://aicomp.ai/v1", api_key="sk-...")

resp = client.chat.completions.create(
    model="grok-4.7",
    messages=[
        {"role": "system", "content": "Answer in one short paragraph."},
        {"role": "user", "content": "Explain what changed in this release."},
    ],
    max_tokens=300,
)

# prompt_tokens / completion_tokens 是真实账单的唯一依据 —— 记下来，别猜
print(resp.usage.prompt_tokens, resp.usage.completion_tokens)

Log the usage object on every call, not just while you are optimising. Rates follow vendor promotions and can move without notice, so a per-call record is the only thing that tells you later whether a price change actually hit you — and in which direction.

import json

# 把每次调用的 usage 落盘，一周后你就有了自己的 in:out 比例。
# 拿这个比例去 /calculator/ 比价，比对着价目表猜准得多 ——
# output 单价是 input 的好几倍，猜错方向就是往贵了算。
with open("usage.jsonl", "a") as fh:
    fh.write(json.dumps({
        "model": model,
        "in": resp.usage.prompt_tokens,
        "out": resp.usage.completion_tokens,
    }) + "\n")

Setting it up

Pointing an existing integration at this model is a base URL change, not a rewrite. Pick your tool:

• Claude Code — set the base URL via environment variables
• Cursor — override the API endpoint in settings
• OpenAI / Anthropic SDK — one base_url argument
• Python — sync, streaming and async examples
• Cutting the bill — eight levers ranked by effect

FAQ

Get Grok 4.7 access