# I Did the Math on Grok 4.5. The $6 Output Price Is the Real Story. > Source: > Published: 2026-07-09 08:57:30+00:00 Grok 4.5 landed, and the takes came fast: "It beats every coding model." "It is just a cheaper Opus." "You can route it everywhere now." Two of those are wrong. One is directionally useful but still too sloppy. I spent the afternoon reading the official xAI docs, the launch post, the pricing page, and gateway listings. The real story is not a clean benchmark crown. It is a pricing attack on coding agents. `grok-4.5` , with Responses API and Chat Completions support.xAI/SpaceXAI now has an official `grok-4.5` docs page, not just a teaser. The page lists: | Field | Grok 4.5 | |---|---| | Model ID | `grok-4.5` | | Context window | 500K tokens | | Input | Text, image | | Output | Text | | APIs | Responses API, Chat Completions | | Reasoning effort | Low, medium, high | | Tools | Function calling, web search, X search, code execution | | Price | $2 input / $6 output per 1M tokens | | Cached input | $0.50 per 1M tokens | That is the confirmed part. xAI also says Grok 4.5 is available in Grok Build, Cursor on all plans, and the xAI console outside the EU. The EU point is not a footnote. If you are building from Europe, it may be the difference between "ship this week" and "wait." Official sources: xAI published benchmark numbers, and they are genuinely interesting. But they do not support the lazy claim that Grok 4.5 is now "the best coding model" in every sense. | Benchmark from xAI launch | Grok 4.5 | What the chart implies | |---|---|---| | DeepSWE 1.0 | 62.0% | Competitive, not first | | DeepSWE 1.1 | 53% | Behind several listed rivals | | SWE Marathon | 29.0% | First in that table | | Terminal Bench 2.1 | 83.3% | Very close to top, not first | | SWE Bench Pro | 64.7% | Strong, but not top | | Avg output tokens on SWE Bench Pro | 15,954 | Big token-efficiency claim | The most important line is not the highest score. It is the token efficiency line. xAI claims Grok 4.5 used 15,954 output tokens on average for SWE Bench Pro tasks, versus 67,020 for Opus 4.8 max in the same chart. If that holds outside xAI's own harness, it matters more than a 1-point benchmark swing. Why? Because coding agents do not just charge you for being smart. They charge you for wandering around. Most model pricing conversations obsess over input. For coding agents, I care more about output. Agent loops produce long traces, tool plans, patches, error explanations, retries, and final summaries. If your agent emits 20M output tokens per month, the output bill alone looks like this: | Output route | Output price / 1M | 20M output tokens | |---|---|---| | Grok 4.5 | $6 | $120 | | $15 output route | $15 | $300 | | $30 output route | $30 | $600 | That is why Grok 4.5 is interesting. Not because it automatically beats everything. Because it gives you flagship-ish coding economics at an output price that is low enough to test seriously. Here is the math I would use before moving traffic. Assume: Cost: ``` 80,000 x $2 / 1,000,000 = $0.160 16,000 x $6 / 1,000,000 = $0.096 total = $0.256 per run ``` At 1,000 runs/month: ``` $0.256 x 1,000 = $256/month ``` That is not cheap-chatbot pricing. But for serious debugging, it is low enough to test. Assume: Cost: ``` 20,000 x $2 / 1,000,000 = $0.040 60,000 x $0.50 / 1,000,000 = $0.030 16,000 x $6 / 1,000,000 = $0.096 total = $0.166 per run ``` At 1,000 runs/month: ``` $0.166 x 1,000 = $166/month ``` The cache saves about $90 per 1,000 runs in this simple scenario. That is why xAI's cache advice matters. They recommend setting a `prompt_cache_key` for Responses API or `x-grok-conv-id` for Chat Completions so repeated context stays cache-friendly. Assume: Token cost: ``` 20,000 x $2 / 1,000,000 = $0.040 4,000 x $6 / 1,000,000 = $0.024 ``` Tool cost: ``` 2 x $5 / 1,000 = $0.010 ``` Total: ``` $0.040 + $0.024 + $0.010 = $0.074 per run ``` At 500 runs/day: ``` $0.074 x 500 x 30 = $1,110/month ``` The lesson: tool calls are not rounding error once you scale. This is how I would decide today: ``` python def should_test_grok_4_5(workload): if workload["region"] == "EU" and workload["needs_xai_console_today"]: return "Wait. xAI says EU API console access is not available yet." if workload["mostly_bulk_summarization"]: return "Probably no. Try cheaper Grok 4.3 or another low-cost route first." if workload["agent_outputs_are_large"] and workload["current_output_price"] >= 15: return "Yes. Grok 4.5's $6/M output price deserves a canary." if workload["reuses_repo_context"]: return "Yes, but only if you set cache keys and measure cache hits." if workload["needs_best_absolute_benchmark_score"]: return "Do not trust the launch chart alone. Run your own eval set." return "Canary 100-300 tasks before migrating production traffic." ``` I would not do a giant migration on day one. I would send it 100 to 300 real tasks and measure: That beats arguing from screenshots. The model exists in xAI docs. That does not mean every gateway already exposes it under the model ID you expect. xAI's docs list model gateways including OpenRouter, Vercel, Cloudflare, Snowflake, and Databricks Mosaic. OpenRouter also has Grok latest pages visible. But when I checked TokenMix's public model catalog on July 9, I found Grok 4.3, Grok 4.20, and Grok 4.1 routes. I did not find a public `xai/grok-4.5` row. That matters because model availability is three separate things: | Layer | Question | |---|---| | Upstream | Does xAI expose the model? | | Gateway | Does your provider route it yet? | | Account | Is your region/account allowed to call it? | Do not put `grok-4.5` into production because a launch blog exists. First confirm the returned model field, pricing, and route status inside your provider. For my full cited breakdown, I put the long version here: [Grok 4.5 review on TokenMix](https://tokenmix.ai/blog/grok-4-5-review-pricing-benchmark-2026). If I were running an engineering team, I would: That is the boring answer. It is also the answer that avoids surprise bills. Grok 4.5 is part of a bigger 2026 pattern: frontier labs are not just competing on intelligence anymore. They are competing on agent economics. The old comparison was: ``` Which model scores higher? ``` The new comparison is: ``` Which model completes the task with fewer retries, fewer output tokens, fewer tool calls, and less human cleanup? ``` That is a better question. It is also harder to answer from public benchmarks. If you want to swap between OpenAI, Anthropic, Google, DeepSeek, Qwen, GLM, and Grok-style routes through one OpenAI-compatible endpoint, that is roughly what [TokenMix](https://tokenmix.ai) does. Disclosure: I work on the research side. The full data-cited version of this Grok 4.5 analysis is on the [original article](https://tokenmix.ai/blog/grok-4-5-review-pricing-benchmark-2026). Grok 4.5 is a real launch, with real API docs and aggressive pricing. But the correct move is not "replace everything." The correct move is "canary the workloads where $6/M output and cache hits can change the bill." Would you test Grok 4.5 first on coding agents, support agents, or office/document automation?