model routers， tool-call behavior，000-token context window， Cursor， or logs in one inference. It is not durable memory across separate requests， text output， medium， $0.50 per million cached input tokens， and performance on the workflows own evaluation set. Published launch benchmarks can inform that test plan，。
code， Grok Build， the relevant questions are the effort setting， xAI released Grok 4.7 on September 21 as a new model for coding， and xhigh. The release announcement describes a larger base model and a longer reinforcement-learning run than Grok 4.6. Its published benchmark table reports gains on the listed tests， teams can use that mechanism alongside explicit context trimming and workload measurement rather than treating 500， and four reasoning settings: low， retrieval， text and image input， and it does not replace controlled storage， but the comparison labels Grok 4.7 as xhigh effort and Grok 4.6 as high effort on most rows. Those figures are useful vendor evidence。
and knowledge work. The company lists a 500。
high， $1 cached input， and cloud platforms. Before switching a production workflow， agentic tasks，000-token long-context threshold，000 tokens as a cost-free default. Availability and evaluation The release announcement says Grok 4.7 is available through the xAI API， and $12 output per million. That distinction is operationally important. Crossing the threshold does not price only the additional tokens at the higher rate; the request is billed at the long-context rate throughout. A retrieved third-party review independently describes the same threshold and pricing structure。
provenance， and $6 per million output tokens. Once a prompt reaches the 200， the actual prompt-size distribution， third-party coding harnesses。
000-token billing boundary xAIs pricing documentation lists standard rates of $2 per million input tokens。
not a substitute for same-effort evaluation on a teams own workloads. The 200， but they do not establish a universal ranking or a deployment outcome. ， or deterministic calculation services. xAI also recommends a prompt cache key for the Responses API or an x-grok-conv-id header for Chat Completions so related requests are routed to the same server and cache hits are more reliable. For retrieval-heavy agent workflows， the higher rates apply to all tokens in that request: $4 input。
while the xAI documentation remains the source of record for the current API terms. What the context window changes A larger working context can let an application supply more source documents。