Model retirement dates / OpenAI
gpt-4-turbo-preview-completions
OpenAI retired gpt-4-turbo-preview-completions on 26 March 2026. API calls to it now fail. The recommended replacement is gpt-5 (which is itself retiring; move to gpt-6.1-sol).
| Provider | OpenAI |
|---|---|
| Status | Retired (as of 16 Nov 2026) |
| Shutdown | 26 March 2026 |
| Replacement | gpt-5 → move to gpt-6.1-sol |
| Moving to it | API change · The old Completions endpoint (a plain prompt) doesn't serve the replacement: move the call to the Responses API or Chat Completions (messages). OpenAI's guide |
| Model type | Text |
| Announced | 26 September 2025 |
| Source | OpenAI deprecations page |
Before you switch
A replacement model answers the same prompt differently: tone, length, format, and whether JSON still parses. Driftline Pro runs your real prompts on gpt-6.1-sol in CI, so you see the new answers before you ship the switch. See a drift test, or the verdict in a fix pull request.
Check your code for it
Run this in your repository. No install and no API key; it lists every OpenAI, Anthropic, Google, Mistral, xAI, Cohere, DeepSeek, Groq, Bedrock, Vertex AI and Azure model ID it finds, with its retirement date and replacement:
npx -y @aidriftline/driftline .
Or look for this ID only: grep -rn "gpt-4-turbo-preview-completions" . (misses aliases, Bedrock and Vertex names, and IDs split across lines).
To be warned automatically before the next retirement, add the free Driftline GitHub Action. It annotates the exact line in pull requests and can fail the build on retired models.
Where a new name is the whole change, Driftline can make it for you: npx -y @aidriftline/driftline fix --dry-run shows the edits, and the Action's fix-pr: true opens one pull request with them, plus a checklist for the lines that need more. See an example pull request.
Same date at OpenAI
gpt-4-0125-preview gpt-4-0314 gpt-4-turbo-preview
Checked against OpenAI's official page on 16 November 2026. Something wrong? hello@aidriftline.com