xAI Grok 4.7
xAI's flagship Grok model for coding, agentic tasks, and knowledge work, with vision and a 500K-token context window.
Grok 4.7 is a cloud text model built by xAI. It is multimodal: alongside a text prompt it accepts images, then replies with generated text. Its context window handles up to 500K input tokens and up to 450K output tokens, and it supports adjustable reasoning effort for harder problems. Generation can be tuned with system instructions, temperature, and top-p sampling. It runs through OpenRouter and xAI using your own API key, from $1.60 per million input tokens.
- Released
- this month (Sep 2026)
- Pricing
- $1.60 / 1M in · $4.80 / 1M out
- Inputs
- Text, Images
- Context window
- 500K in · 450K out
- Reasoning
- Adjustable effort
- Controls
- System prompt, Temperature, Top-p
Examples
Generated with Grok 4.7 via OpenRouter. The same three prompts run against every text model in the catalog, shown verbatim, so the only thing that changes between two models’ answers is the model.
Explain what an API is to someone who has never written code. Do not use a restaurant or waiter analogy. Plain prose only — no headings, bullet points, or markdown formatting. Maximum 50 words.
An API is a set of rules that lets one piece of software ask another for information or to do something, and get a predictable reply, without either needing to know how the other works inside.
A two-person startup is deciding whether to build their own user authentication or use a hosted provider. Give them a clear recommendation, then the single strongest argument against your own recommendation. Plain prose only — no headings, bullet points, or markdown formatting. Maximum 150 words.
Use a hosted authentication provider. A two-person startup should spend its scarce time on the product users pay for, not on passwords, sessions, recovery flows, and the long tail of security mistakes. A reputable host already handles hashing, multi-factor authentication, social login, and breach response, and it will keep patching those systems after you have moved on. The strongest argument against that choice is loss of control: authentication sits on every request, so an outage, pricing change, data-residency limit, or forced migration can halt the business or trap you in a vendor you cannot cheaply leave.
Write a briefing for a non-technical executive explaining why their company's spending on AI is hard to predict, and what they can do about it. Cover at least three distinct causes. Plain prose only — no headings, bullet points, or markdown formatting. Write exactly 205 words.
Company spending on AI is hard to predict because costs follow usage, vendor terms, and hidden work rather than a stable annual license. One cause is consumption pricing: each prompt, document, and automated action draws paid capacity, and a successful pilot can spread across teams faster than finance expected. A second cause is rapid market change, since model prices, features, and contract minimums move often, turning last quarter’s estimate into a poor guide. A third cause is work that never appears on the model bill, including data preparation, system integration, security checks, and experiments that fail after consuming staff time and cloud capacity. Leaders can make spending more predictable by assigning every initiative a business owner, a monthly cap, and a stated outcome before it begins. Review usage against those caps each month, end trials that miss their goals, and limit the company to a short list of approved tools so charges are visible. Ask finance and technology leaders to forecast a range, not a single number, and revisit that range whenever usage patterns change sharply. Pair cost reports with results so investment decisions rest on evidence rather than enthusiasm. This discipline will not freeze innovation, but it will replace surprise invoices with managed choices.
xAI
xAI builds the Grok family — frontier reasoning LLMs plus Grok Imagine video and voice models, integrated with real-time knowledge from X.
x.ai ↗