Using USD display for price cards and history values.

Latest snapshot May 13, 22:05 Most recent stored public pricing point for this model.
Source PricePerToken OpenAI Source page Keep the source link visible so the latest stored number stays manually verifiable.
Source mode Fallback source Verified fallback is in use because the preferred official page is not consistently crawlable right now.
History signal Usable signal Stored history is deep enough to use trend language with more confidence. 10 stored points across 44 days. 7d and 30d windows are already ready. 90d window is still awaiting depth. The latest stored comparison already shows a sharp move input move.
Cached pricing $0.125 Cached input pricing only appears when the source exposes it clearly.
Batch discount Not listed Shown only when a provider-listed batch price is normalized. Do not mix it with realtime pricing assumptions.
Latest move Sharp move Input changed +100% on May 13, 22:05.
Stored history 10 points · 44 days Trend-ready. Stored history is deep enough to read short-term movement with more confidence.
Strongest window 7d change shows an increase Input pricing is up in this window. Re-check workload cost assumptions.
Recommended next step Run in calculator The latest stored move is an increase, so cost impact is the first question to answer.
Input price
$1.25 per 1M tokens
Output price
$10.00 per 1M tokens
Cached input
$0.125 per 1M tokens
Blended price
$3.44 75 / 25 input-output mix
Single request estimate $0.012
Monthly estimate $3615.00
Batch discount Not listed
How to read this estimate The reference workload is a fast sanity check, not a forecast. If your prompt shape, cache ratio, or monthly traffic differs, jump to the calculator with this model preselected and adjust the assumptions there.

Latest detected move: Input +100%. The latest stored move is an increase, so cost impact is the first question to answer.

Input price +100% Sharp move $0.625 -> $1.25 Delta +$0.625 May 11, 22:05 -> May 13, 22:05 2 days between stored points This move raises spend assumptions. Re-run your workload in the calculator before committing budget.
Output price +100% Sharp move $5.00 -> $10.00 Delta +$5.00 May 11, 22:05 -> May 13, 22:05 2 days between stored points This move raises spend assumptions. Re-run your workload in the calculator before committing budget.

Stored history is deep enough to read short-term movement with more confidence.

7d change May 1, 22:05 -> May 13, 22:05
Input +100% Output +100% Cached 0%
5 stored points across 12 days Input pricing is up in this window. Re-check workload cost assumptions.
30d change Apr 13, 22:05 -> May 13, 22:05
Input +100% Output +100% Cached 0%
15 stored points across 30 days Input pricing is up in this window. Re-check workload cost assumptions.
90d change Awaiting depth Awaiting depth Needs 90+ days of stored snapshots.
Tracking span Mar 30, 12:00 -> May 13, 22:05 44 stored days covered by the visible history.
Latest detected change Input +100% Driven only by stored deltas, not guessed from one point.
History status Trend-ready Stored history is deep enough to read short-term movement with more confidence.
Input Output Cached

Shared scale across visible pricing lines. Use the table below for exact values.

Captured at Input / 1M Output / 1M Cached / 1M Source
Mar 30, 12:00 $1.25 $10.00 $0.125 OpenAI
Mar 31, 09:56 $1.25 $10.00 $0.125 PricePerToken OpenAI
Apr 3, 22:05 $0.625 $5.00 $0.125 PricePerToken OpenAI
Apr 6, 22:05 $1.25 $10.00 $0.125 PricePerToken OpenAI
Apr 13, 22:05 $0.625 $5.00 $0.125 PricePerToken OpenAI
Apr 18, 22:05 $1.25 $10.00 $0.125 PricePerToken OpenAI
Apr 26, 22:05 $0.625 $5.00 $0.125 PricePerToken OpenAI
Apr 30, 22:05 $1.25 $10.00 $0.125 PricePerToken OpenAI
May 11, 22:05 $0.625 $5.00 $0.125 PricePerToken OpenAI
May 13, 22:05 $1.25 $10.00 $0.125 PricePerToken OpenAI
GPT-5 output_price_per_million increased
output_price_per_million changed from USD 5 / 1M to USD 10 / 1M
Sharp move · Run in calculator
+100%
May 12, 22:05 $5.00 -> $10.00
GPT-5 input_price_per_million increased
input_price_per_million changed from USD 0.625 / 1M to USD 1.25 / 1M
Sharp move · Run in calculator
+100%
May 12, 22:05 $0.625 -> $1.25
GPT-5 output_price_per_million decreased
output_price_per_million changed from USD 10 / 1M to USD 5 / 1M
Sharp move · Open compare
-50%
May 1, 22:05 $10.00 -> $5.00
GPT-5 input_price_per_million decreased
input_price_per_million changed from USD 1.25 / 1M to USD 0.625 / 1M
Sharp move · Open compare
-50%
May 1, 22:05 $1.25 -> $0.625
GPT-5 output_price_per_million increased
output_price_per_million changed from USD 5 / 1M to USD 10 / 1M
Sharp move · Run in calculator
+100%
Apr 29, 22:05 $5.00 -> $10.00
GPT-5 input_price_per_million increased
input_price_per_million changed from USD 0.625 / 1M to USD 1.25 / 1M
Sharp move · Run in calculator
+100%
Apr 29, 22:05 $0.625 -> $1.25
GPT-5 output_price_per_million decreased
output_price_per_million changed from USD 10 / 1M to USD 5 / 1M
Sharp move · Open compare
-50%
Apr 19, 22:05 $10.00 -> $5.00
GPT-5 input_price_per_million decreased
input_price_per_million changed from USD 1.25 / 1M to USD 0.625 / 1M
Sharp move · Open compare
-50%
Apr 19, 22:05 $1.25 -> $0.625

Source and limits

Source PricePerToken OpenAI PricePerToken OpenAI
Recorded check Checked May 13, 22:05
Parser version pricepertoken-payload-v1
Context window 400000
Output limit 128000
Trust policy This page stays official-first whenever the provider page is crawlable. If not, verified fallback or baseline states stay explicit so the source trace never over-claims a live official crawl.
Source note Fallback snapshot from PricePerToken because OpenAI official pricing pages currently return an anti-bot challenge to server-side crawlers. Source updated at 2026-05-13T08:24:36.982337Z.

When this model detail is enough

Use this page when you need a single-model read: current price, source traceability, recent change strength, and enough stored history to judge whether the latest move is actionable.

When to escalate to compare

If a recent price cut or a stable multi-point window makes this model newly competitive, move to compare so every candidate runs against the same workload assumptions.

When to escalate to calculator

If a recent price increase changes spend assumptions or history is still thin, use calculator next so you can replace the reference workload with your own traffic, cache ratio, and budget ceiling.