Kingy.ai Price History Library · evidence observed through August 2, 2026
OpenAI o3 input price history tracks input list pricing for o3-2025-04-16 (served by the o3 alias). It publishes 1 editorially verified episode while preserving the broader machine timeline as a separate evidence layer.
Identity and scope
The April 2025 o3 API release is the o3-2025-04-16 snapshot, also served through the o3 alias. OpenAI described the June change as the same exact model becoming cheaper, which rules out a replacement-model explanation for this episode.
Editorially verified change
Uncached input fell from $10 to $2 per million tokens. This component is the clearest workload baseline for recalculating prompt-heavy o3 API costs after June 10, 2025.
| Old price last seen | Old | New price first seen | New | Verification |
|---|---|---|---|---|
| June 8, 2025 last old-price capture |
$10 | June 11, 2025 first new-price capture |
$2 | 80% cut; OpenAI announced the change June 10 and the retained pricing capture observed it by June 11 UTC. |
Machine-detected state timeline
The rows below come from the scope-safe machine series. A changed value is not automatically an editorial change. Only rows tied to the verified brackets above support the page’s change claim; the others remain observations or held transitions.
| State | First observed | Value | Editorial status | Lineage |
|---|---|---|---|---|
| 1 | $10 USD | machine-only state | archive6b4dd816f708e8ad… |
|
| 2 | $2 USD | bounds a verified episode | archivefbf62536bcf75db7… |
Source and archive lineage
- Current official pricing page.
- Episode 1 before: https://web.archive.org/web/20250608083612/https://openai.com/api/pricing — capture SHA-256
6d44c8bce7bd26330062f44771ba8635b71a94113aaec425d05ee625fe1305aa. - Episode 1 after: https://web.archive.org/web/20250611095744/https://openai.com/api/pricing — capture SHA-256
fbf62536bcf75db71bef76fe454d43080596b90993fc49bac01b7d161ff68e19. - Retained series ID:
openai:o3:input. - Dataset series window: April 17, 2025 to August 7, 2025.
How to use this history
Use the verified row when reconstructing a dated standard-list-price estimate. Use the machine timeline to audit extraction and locate captures, not to infer billing scope or a precise effective timestamp. Recheck the provider’s current documentation before making a live purchasing or architecture decision.