Early-bird pricing (ends Dec 25), locked in while you stay subscribed: Go $10/mo (normally $20), Plus with Opus 5.5 just $30/mo (normally $50)Subscribe →
Text chat488K context

Grok 4.5

Try Grok 4.5 online for coding, agent workflows, structured analysis, streaming output, prompt caching, and Chat Completions API access.

Price / 1M tokensSave 80%
OfficialAIReiter
Input$2.00$0.40
Output$6.00$1.20
Cache read$0.30$0.06
Readme
Input
Caps the reply length. Reasoning models count their thinking toward it too.
grok-4.5
Output

A codebase you don't know is a risk, not a hurdle. The plan should burn down that risk in order: understand, run, trace, spike, then make the change small enough that "production-ready" is a property you can demonstrate, not a hope.

Here are the first five steps, with the evidence you collect at each.

Step 1 — Get it building and the baseline green (half day)
Read the README, the manifest(s), the CI config, and any architecture docs. Boot the app locally, run the full test suite, run the linter/typechecker.
Evidence: The exact commands that reproduce a clean build and a passing test suite from a fresh checkout (recorded output, not memory of it). A one-page map you wrote yourself: where the entry points are, the layers, the build/test toolchain, and the main risks to your feature (e.g. "this touches cron jobs and payments").

Step 2 — Trace the smallest end-to-end slice that resembles your feature (half day)
Don't start with your feature. Pick a neighboring one that already works and follow it from entry to persistence. Note the conventions along the way: how errors surface, how config is injected, how logging is done, how tests are written.
Evidence: An annotated trace — file → function → what it does — for that slice. A written list of "conventions I must follow" (not intuitions; things you observed in real code). A named shortlist of the 3–5 files you will actually touch. If you can't produce this trace, you're not ready to write code.

Step 3 — Spike the core path (day 2)
Build the ugly version: hardcoded values, no error handling, no tests. The purpose is to confirm the path you traced in step 2 is real and to surface what you didn't know you didn't know.
Evidence: A working spike demonstrating the feature's central data path, alongside a list of every assumption the spike broke and what you corrected. That correction list is the most valuable document in this whole plan.

Step 4 — Write the contract before the code (half of day 2 / day 3)
Once the spike proves the path, pin down what production needs: the inputs/outputs, the error cases, where it sits in the conventions from step 2. Then write the tests — they'll be red, but they're the specification.
Evidence: A one-to-two-page design doc, an agreed interface/API shape (with the team if there is one), and a red test suite that encodes intended behavior. If you can't write the contract without consulting the code, you haven't finished step 2.

Step 5 — Implement in small, verified increments (days 3–4)
Replace the spike with the real thing in small commits, each one keeping the suite green, leaning on the existing patterns. Run lint/tests/typecheck per commit — CI, not just locally — and exercise the actual path against a real instance (staging or a local environment that isn't stubbed).
Evidence: A branch with progressive commits, each green in CI; coverage on the new code; something that proves it works against reality (a test result, a log trace, a screenshot); and a review by at least one person who knows the codebase. The review counts as evidence — an unfamiliar codebase has tribal knowledge you cannot extract from the files alone.

Steps 6+ would be the things that actually make it "shipped": a migration plan and its rollback, feature flagging, observability, the release and post-release verification. But the first five get you to a reviewed, green, working slice in staging — which is the point at which you can say "this will work in production" with evidence behind it, instead of a guess.

Generated in42.7s
Input tokens134
Output tokens2,354
Tokens / sec55.13
TTFT-

Runs in this page. Sign-in and credits are required.

Model details

Use the same model key in Playground, API requests, and internal workflows.

Model ID
grok-4.5
Provider
Grok
Protocol
OpenAI Chat Completions
Context window
500,000 tokens
Max output
8,192 tokens
Input tokens
40 credits / 1M tokens
Output tokens
120 credits / 1M tokens
Cache read
6 credits / 1M tokens
Cache write
-

What You Can Do with Grok 4.5

A coding and agentic workflow model with configurable generation and prompt caching.

Coding and debugging

Review implementation plans, trace defects, explain unfamiliar code, and propose focused fixes.

Agentic workflows

Plan multi-step tasks and evaluate the outputs of tool-driven software and engineering flows.

Structured analysis

Return decisions, risks, and action lists in a format that downstream systems can consume.

Cache-aware API traffic

Reuse stable prompt prefixes and verify savings through prompt_tokens_details.cached_tokens.

Grok 4.5 Use Cases

Best suited to engineering work that benefits from reasoning and iterative refinement.

Pull request review

Find risky assumptions, missing tests, and compatibility problems before a change ships.

Incident investigation

Combine logs, symptoms, and code context into ranked causes and a verification plan.

Developer assistants

Support implementation, documentation, test design, and technical explanations in one workflow.

API automation

Run repeated analysis and transformation tasks with streaming output and visible token usage.

Should You Use Grok 4.5 or Grok 4.6?

Manage API keys →

Keep this page useful for existing Grok 4.5 integrations while making the upgrade path explicit.

01Keep Grok 4.5 when

Your evaluation set already passes, the integration is stable, and changing models would add regression risk.

02Evaluate Grok 4.6 when

You are starting a new coding workflow or want to retest difficult agent tasks against the newer route.

03Do not migrate on a headline

Compare both models on your own code, latency target, cache behavior, and accepted answer rate.

04Use routing when useful

Keep predictable traffic on 4.5 and send only harder or newly evaluated work to 4.6.

Try Grok 4.5 in 3 steps

  1. 01

    Run a representative prompt

    Use real code or workflow context instead of a generic benchmark question.

  2. 02

    Check output and usage

    Inspect completion quality, latency, prompt tokens, output tokens, and cached input tokens.

  3. 03

    Connect Chat Completions

    Call POST https://aireiter.com/api/v1/chat/completions with model "grok-4.5" and stream=true when needed.

FAQ

01Is Grok 4.5 still worth using?

Yes for workloads already validated on it. New integrations should compare it directly with Grok 4.6 before choosing a default.

02Which API protocol does this route use?

Use the OpenAI-compatible Chat Completions endpoint with model "grok-4.5".

03What context window is listed?

The page lists a 500K-token context window. Requests at or above 200K may have different upstream economics, so inspect the current AIReiter rate.

04How do I confirm prompt caching?

Check usage.prompt_tokens_details.cached_tokens. A repeated request without a positive cached token count is not a confirmed hit.

05How should I compare Grok 4.5 and 4.6?

Use the same code task, response limit, and acceptance rubric, then compare pass rate, latency, and actual token usage.