Cheapest GPT API
Compare Cost per Accepted Output
Find the lowest-cost GPT API route by comparing current model versions, access paths, processing modes, and prices on the same accepted workload.
TL;DR
Use the same prompts, context, tools, output limits, quality bar and region.
Record retrieval time, model version, access path and official source URL.
Include input, output, cache, batch, tools, media, retries and route fees.
A low unit rate loses when quality failures and retries consume extra calls.
What “cheapest” should mean
Compare direct provider access, cloud-platform access and managed gateways only when they deliver the same model version, region, features and service level. Otherwise label the difference rather than hiding it.
OpenAI's current table separates short- and long-context prices and distinguishes Standard, Batch, Flex, and Priority service. It also lists cached input and, for supported models, cache-write rates. Regional processing can add an uplift, while web search, file search, containers, image generation, audio, and other tools have their own billing units. A headline input rate therefore describes only one part of one route.
Calculate total charges for a representative batch, then divide by outputs that pass your acceptance gate. Include input, cached input, cache writes, visible output, reasoning tokens where billed, retries, failed attempts, and tool charges. Add engineering, support and compliance costs separately when they materially affect the decision.
GPT access path comparison
| Access path | Best fit | Verify before choosing |
|---|---|---|
| Direct provider | Official models and features with a direct commercial relationship. | Current model price, tiers, regions, support, data terms and limits. |
| Cloud platform | Existing cloud identity, networking, procurement or residency matters. | Deployment names, regional availability, feature lag and platform pricing. |
| Managed gateway | Multi-provider policy, observability and one integration are valuable. | Gateway fee, model markup, routing policy, data path and evidence quality. |
| Batch or async | Work can wait and the official route supports asynchronous processing. | Eligibility, completion window, failure handling and actual acceptance rate. |
True-cost worksheet
Separate prompt, cached input, reasoning and visible output dimensions.
Add search, code, files, images, audio, video and storage charges when used.
Count timeouts, invalid outputs, safety failures and fallback attempts.
Use workload tests with explicit quality, schema and latency gates.
Run a defensible cost test
Use production-shaped prompts rather than a synthetic one-line benchmark. The replay set should include the real context-length distribution, cacheable and unique prefixes, short and long answers, structured outputs, tool calls, rate-limit pressure, and requests that fail the quality gate. Compare service tiers separately because a lower token rate is not equivalent if completion time or availability changes.
- Snapshot current official pricing, model ID, context band, service tier, region, and terms for each exact route.
- Replay the same representative workload with fixed schema, quality, latency, and safety criteria.
- Capture native request IDs and usage fields instead of estimating tokens from text length.
- Reconcile cached input, cache writes, reasoning or output, retries, failed attempts, tools, and route charges to the bill.
- Calculate cost per accepted result and per completed user workflow, not only cost per call.
- Repeat after model, price, prompt, SDK, tool, or workload-distribution changes.
Measure cost after the quality gate
A versioned workload suite calls each eligible route. The ledger records every attempt and billing dimension. A quality gate marks accepted results. The comparison engine calculates total bill divided by accepted outputs and retains source URLs and timestamps.
Production rule: never publish a cheapest claim without an exact model, route, workload, date and acceptance method.
Separate model cost from capability cost
QVeris complements GPT access with governed discovery and execution of external APIs, tools, services and live data. Track those capability charges separately, then join them to the parent workflow when calculating end-to-end cost.
Current GPT-5.6 list-price ladder
Official OpenAI prices verified July 21, 2026, in USD per 1 million tokens. Luna is the lowest list-price GPT-5.6 option, but the cheapest accepted route depends on task quality, reasoning effort, cached input, output length, retries, and tool fees.
| Model or route | Input / cost | Output | Scope |
|---|---|---|---|
| GPT-5.6 Sol | $5.00 | $30.00 | Cached input $0.50 |
| GPT-5.6 Terra | $2.50 | $15.00 | Cached input $0.25 |
| GPT-5.6 Luna | $1.00 | $6.00 | Cached input $0.10 |
Always verify the linked official pricing source immediately before a buying decision. Model quality, output length, cacheability, retries, tools, service tier, region, taxes, and discounts can reverse a token-price comparison.
FAQ
It depends on the exact model, route, region and workload; verify current official pricing.
No. Include output mix, retries, tools, quality acceptance and support terms.
After material model, price, prompt, feature or workload-distribution changes.