Grok 4.7
- Input / 1M tokens
- $2.00
- Output / 1M tokens
- $6.00
- Providers
- 2
- Uptime, 24 h
- 100%
API models · Side by side
Grok 4.7 vs GPT-6.1 Sol
Grok 4.7 and GPT-6.1 Sol start at the same input price, but answer length and document size change the bill. Grok has the lower output rate. Sol offers more than twice the context space, while the two switch to higher prompt rates at different thresholds.
GPT-6.1 Sol
- Input / 1M tokens
- $2.00
- Output / 1M tokens
- $10.00
- Providers
- 3
- Uptime, 24 h
- 100%
The short answer
Start with Grok when shorter prompts and output spending dominate. Consider Sol when you need more context or your application already relies on its Responses API tools. For prompts between the two pricing thresholds, calculate the full request: Sol can be cheaper even though its base output rate is higher.
Estimate your monthly bill
Enter your own usage. We apply each model's current rates, including long-prompt pricing, for a 30-day month.
Try:
Grok 4.7$210.00per month
GPT-6.1 Sol$270.00per month
A token is roughly three-quarters of an English word. Cached input, reasoning tokens, tools and media are not included.
Compare the details
Compare context, supported inputs and usage costs. Highlighted rows show a difference.
| Feature | Grok 4.7 | GPT-6.1 Sol |
|---|---|---|
| Input formats | file, image, text | file, image, text |
| Output formats | text | text |
| Context / position limit | 500,000 | 1,050,000 |
| Endpoint output limit (tokens) | 450,000 | 128,000 |
| Developer features | Reasoning output, logprobs, Output limit, Reasoning controls, Thinking effort, Response format, Seed, Stop sequences, Structured output, Temperature, Tool selection, Tool calling, top k, top logprobs, Sampling controls | Reasoning output, Completion limit, Output limit, Reasoning controls, Thinking effort, Response format, Seed, Structured output, Tool selection, Tool calling, Response length |
| Cached input / 1M tokens | $0.50 | $0.10 |
| Cache write / 1M tokens | Unknown | $2.50 |
| USD input / 1M tokens | $2.00 | $2.00 |
| USD output / 1M tokens | $6.00 | $10.00 |
| Available API providers | 2 | 3 |
| Best provider uptime, last 24 h | 100% | 100% |
| Model identifier | x-ai/grok-4.7 | openai/gpt-6.1-sol |
API pricing
Prices are in USD per million tokens. Input is what you send; output is what the model generates. Chat subscriptions and API usage are billed separately.
Grok 4.7: long-prompt rates
- Long-prompt threshold: 200,000 prompt tokens. Input: $4.00 / 1M. Output: $12.00 / 1M.
GPT-6.1 Sol: long-prompt rates
- Long-prompt threshold: 272,000 prompt tokens. Input: $4.00 / 1M. Output: $15.00 / 1M.
Tools, images and additional reasoning can add charges. The examples below cover input and output tokens only.
Compare local modelsWhat those prices mean in practice
Each example uses the same token budget for both models. These are calculations, not measured workloads. Cache discounts, media, tools and extra reasoning are excluded.
| Workload | Grok 4.7 | GPT-6.1 Sol |
|---|---|---|
| 1,000 short requestsPer request: 2,000 input + 500 output tokens | $7.00 | $9.00 |
| 100 document summariesPer request: 20,000 input + 1,000 output tokens | $4.60 | $5.00 |
| 10 long-document requestsPer request: 300,000 input + 2,000 output tokens | $12.24 | $12.30 |
Estimate = requests × (input tokens × input price + output tokens × output price) ÷ 1,000,000. Long-prompt rates are applied where the pricing data provides them. Real requests can use different amounts of output.
Beyond the price tag
A shorter prompt gives Grok the price advantage
Both models charge $2 per million input tokens at their base tier. Grok charges $6 for output against Sol’s $10. For 1,000 requests with 2,000 input tokens and a 500-token reply each, the totals are $7 and $9. Those are batch totals, not monthly bills. The calculator above multiplies daily requests by 30 to estimate a month.
Between the thresholds, Sol can cost less
Grok’s long-prompt tier starts at 200,000 input tokens in the calculator; Sol’s starts at 272,000. A request with 250,000 input tokens and a 2,000-token reply therefore costs $1.024 on Grok and $0.52 on Sol. Once both higher tiers apply, Grok has the lower output rate again. Count tokens per request, not across the whole account, when deciding which tier applies.
A repository can fit in one model and exceed the other
Sol allows 1,050,000 context tokens; Grok allows 500,000. If your application must send a large repository, several documents and conversation history together, that difference matters before price does. For smaller tasks, sending only the relevant files can reduce cost and make the answer easier to check. A larger window gives you room; it does not establish better use of every line.
Check how the assistant connects to tools
Grok’s developer API offers X search, web search and code execution. Sol supports tool calling through the Responses API; its Chat Completions support does not include tool calling. An editor or agent needs the right integration to use those capabilities. If you switch models, check the API route and tool permissions as well as the name in the settings. A chat response alone does not show whether the application can complete a tool-driven job.
Budget replies separately from reading
Sol has a 128,000-token output limit. Grok’s developer guide describes no separate text-output cap, while the compared hosting endpoint supplies a 450,000-token ceiling. These are service limits, not targets for everyday answers. For a long report or generated codebase, ask for sections you can review independently. Context must still accommodate the request and response, and tool activity or billable reasoning can add to the token calculation.
Choose around the job you repeat
For a customer-support assistant, compare whether both models follow the supplied policy and return an answer that needs little editing. For a coding agent, check the finished change and the number of retries. Keep the inputs and allowed tools consistent. Grok’s cheaper output may suit a reply-heavy feature; Sol’s larger context may suit a document-heavy one. Neither cost difference proves a speed or quality winner.
Common questions
Does a ChatGPT or Grok subscription pay this API bill?
No. This comparison covers API usage. Consumer subscriptions and editor plans have their own billing arrangements.
Can I send audio or video directly?
These compared model endpoints return text and accept text, images and file inputs. They are not direct audio or video input options. A transcription or frame-extraction workflow needs its own processing and budget.
Are the cost examples benchmark results?
No. They apply the same input and output token budget to both models. Actual reply lengths, reasoning and tool use can differ.