GPT-6.1 Sol API pricing and cost calculator
By TechCompare · Updated · How we check
Sol's base rates make a 100K-input, 5K-output request $0.25 without cache hits or $0.155 with half the input cached. Check the long-prompt tier before scaling that estimate.
Calculator
Cost Comparison
Based on 100,000 input tokens (50% cached), 5,000 output tokens, and 100 requests.Prices come live from OpenRouter at each maker's own price where it's listed. Temporary deals are left out.
GPT-6.1 Sol's standard base rates are $2 per million input tokens and $10 per million output tokens. Cache reads cost $0.10 per million, so repeated prompt prefixes can make a meaningful difference to a session's input bill. The larger budgeting question is how many calls, output tokens, and retries a completed task needs. This page works through those token costs and the prompt-length boundary that changes the rates.
OpenAI: GPT-6.1 Sol
OpenAI's own price
- Input
- $2
- Output
- $10
- Cached
- $0.10
per 1M tokens
Price checked 2026-11-19
How this is calculated
For 100,000 input and 5,000 output tokens, an uncached base-tier request costs $0.20 for input plus $0.05 for output, or $0.25. The calculator's starting example reads half the input from cache, which puts the input estimate at $0.105 and the total at $0.155.
At 100 requests per month, that's $15.50 before cache writes and tools. Above 272,000 input tokens, the entire request moves to $4 input, $0.20 cache reads, and $15 output per million tokens. A 300,000-input, 5,000-output request then costs $1.275 without cache hits or $0.705 with half the input cached. These are standard provider text-token examples. The embedded calculator loads OpenRouter prices and its conditional tiers, so provider routing can affect the displayed estimate.
Verdict
Budget from completed tasks rather than one representative call. Record prompt length, cache-hit tokens, output usage, and attempts on your own workload, then apply the matching tier. Sol can be a useful candidate for coding and agent workflows that meet your quality targets at these rates. Keep unnecessary context out of each request, and compare larger document prompts separately because crossing the input boundary reprices the whole request.
More API Standalones scenarios
Related guides
Frequently asked questions
How much would 10,000 GPT-6.1 Sol requests cost?
What does the cache-read discount apply to?
Does a large prompt change Sol's rates for the whole request?
What does batch processing save on Sol?
Is GPT-6.1 Sol pricing a ChatGPT subscription price?
Related tools
LLM VRAM Calculator
Calculate the VRAM needed to run or fine-tune any LLM at any quantization.
Use toolPower Cost Estimator
Estimate annual electricity costs for your PC, Server, or TV.
Use toolData Transfer Calculator
Calculate file transfer time or the speed you need over USB, Wi-Fi or Ethernet, with latency.
Use toolJSON Formatter
Validate, format, and minify JSON. Browse it as a tree, run JSONPath queries, compare two documents, or validate against a JSON Schema.
Use tool