Reviewed by Jonathan West · Updated Sep 8, 2026

ChatGPT Model Not Found Error Explanations and Fixes

A missing model code points to a retired snapshot, an exact-string mismatch, or an unassigned project tier.

Reviewed by Jonathan West · Updated Sep 8, 2026

A ChatGPT model not found error occurs when you call an invalid model name, query a retired snapshot, or request a model your account cannot access. At Layer3Labs, we build AI workflow systems for businesses, and diagnosing model routing errors is standard work during our client deployments. The message appears in two distinct environments. You see it inside the web application or as an API response. Both point to specific configuration mismatches.

OpenAI does not formally document a 404 model not found status in its standard API error codes guide. The official guide covers status codes like 400, 401, 403, and 503 instead. That omission leaves developers guessing. They cannot tell whether the issue sits in their request payload, their plan tier, or OpenAI servers.

Why the API Error Codes Guide Omits Model Not Found

OpenAI omits the model not found error from its standard API error documentation. The official API error codes guide documents other failure codes. It defines code 400 for disallowed service tiers and code 401 for invalid credentials. It outlines code 403 for unsupported regions and code 503 for overloaded models. A missing model triggers a 404 that the guide does not document at all.

The client receives a message stating that the model does not exist or you lack access. That single response conflates two separate operational issues. The string could be misspelled. Alternatively, the model exists within the ecosystem, but your specific organization or project has not received access to it. Checking the raw API payload clarifies which branch you are hitting.

A Starlink dish mounted on the roofline of a house at dusk
Power Your AI With Starlink

First Month Free

Get one month of Starlink free when you sign up through this link. Fast, reliable internet at home and on the go.

Claim First Month Free

Plan Tiers and Model Rollouts in the ChatGPT App

Access to new models in the ChatGPT application depends directly on your subscription tier. OpenAI announced GPT-6 Astra on September 3, 2026. GPT-6 Pro runs on GPT-6 Astra across the Pro, Business, and Enterprise plans. Plus plans include GPT-6 Astra in ChatGPT Work and Codex during the rollout. Plus users will not see GPT-6 Astra in the primary chat model list.

OpenAI deploys major updates gradually. Availability can differ between Chat, Work, and Codex on the same account. A model your plan cannot select is different from a model that does not exist. If your interface drop-down is missing, read our guide on the ChatGPT model picker missing. That is an interface state. Consult the ChatGPT help article to confirm which models your current tier includes.

Model Deprecations and Scheduled API Shutdowns

Querying a shut-down model returns an error because the model has been retired from service. OpenAI separates deprecation from shutdown. A deprecation is the formal announcement of planned retirement. A deprecated model continues to accept incoming requests and return completions until the shutdown date arrives. It stops answering completely once shutdown occurs.

Retirement notice periods follow fixed schedules. OpenAI provides at least 6 months of notice for generally available models. Specialized variants receive at least 3 months of notice. Preview models can shut down with as little as 2 weeks of notice. Check the OpenAI deprecations page for active timelines.

  • gpt-4-0613, gpt-4-turbo-2024-04-09, gpt-3.5-turbo-0125, and o1-2024-12-17 were announced for retirement on April 22, 2026 and shut down on October 23, 2026.
  • gpt-5-2025-08-07, gpt-5-mini-2025-08-07, gpt-5-nano-2025-08-07, and o3-2025-04-16 were announced on June 11, 2026 with a shutdown date of December 11, 2026.
  • OpenAI designated gpt-5.6-sol, gpt-5.6-terra, and gpt-5.6-luna as replacements for retiring models.

Exact Model Identifiers and SDK Host Routing

OpenAI requires exact string matches for every model identifier passed to its endpoints. The API treats gpt-4 and gpt-4-0613 as two completely distinct identifiers. A single typo in a snapshot date makes the gateway reject the request. Sending a model request to the wrong endpoint also causes immediate failures. A chat model fails on a legacy completions route. Audio models fail on text endpoints.

Host configuration presents another common hurdle. Developers using the official SDK sometimes route requests to Azure OpenAI endpoints. Azure OpenAI resolves custom deployment names instead of base OpenAI model IDs. Passing a valid OpenAI model string to an Azure host returns a resource not found message. Verify your base URL settings if you connect through proxy architectures.

The failure mode we hit most often is teams assuming their API key grants access to every model OpenAI publishes. Keys belong to specific projects. A project often lacks permission for newest preview models. Developers then waste effort rewriting code when the fix requires updating project settings on the OpenAI platform. Check permissions before touching code.

Step-by-Step Triage for Missing Models

A systematic check isolates whether the failure stems from your string, your credentials, or retirement schedules. Run through these checks in order. Each step rules out a specific operational failure.

Review your request logs for specific HTTP response status codes. The status code reveals how OpenAI processed your authentication and project tier. Checking the response headers helps confirm your project routing.

  • Step 1: Check the exact model string. Compare your identifier against the active list on the OpenAI platform to catch typos.
  • Step 2: Inspect endpoint compatibility. Chat models must target /v1/chat/completions.
  • Step 3: Review project permissions. Confirm your API key belongs to an organization and project authorized for that service tier.
  • Step 4: Check retirement status. Visit the OpenAI deprecations page to confirm the shutdown date.
  • Step 5: Verify host routing. Azure endpoints require deployment names.

Who This Troubleshooting Guide Is Not For

This troubleshooting guide does not address users experiencing broad service outages or missing interface buttons. If OpenAI servers return 500 server errors, the problem sits on OpenAI infrastructure. Code 503 indicates that the requested model is temporarily overloaded. Wait for server capacity to recover when encountering 503 responses.

Users who cannot locate the model selector dropdown in ChatGPT should read our ChatGPT model picker missing guide. That issue involves interface controls. It is not a missing model code error. Developers encountering missing CLI models should consult our Codex model not available article instead.

What Would Change These Troubleshooting Checks

These troubleshooting steps would change if OpenAI adds explicit 404 error definitions to its developer documentation. The missing status code currently creates ambiguity between syntax errors and access limitations. Clear documentation would simplify payload inspection. Our checks would also change if OpenAI standardizes deployment naming conventions across partner platforms.

Which exact models a plan or an API project can reach changes without notice. Verify your project limits directly on the OpenAI platform before refactoring active workflows. Audit your project access permissions as your next troubleshooting step.

Frequently Asked Questions

  • ChatGPT displays this error when your account requests a model that has shut down or one your subscription tier cannot access. For API users, it also occurs when the model identifier string contains a typo or targets the wrong endpoint. Check active model lists on the OpenAI platform and verify your account plan.
  • You cannot change models if your current plan restricts access. An active conversation can also lock to a specific model version. OpenAI rolls out models like GPT-6 Astra gradually across tiers. Pro, Business, and Enterprise plans receive GPT-6 Astra in chat, while Plus plans access it in Work and Codex. Check our ChatGPT model picker missing guide if the UI selector disappeared.
  • Find active API models by logging into the OpenAI platform and viewing your project permissions. In the web interface, open ChatGPT and check the model dropdown menu at the top of a new conversation. Model availability varies by plan tier. Check OpenAI help documentation to confirm which models your tier supports.
  • Select a model by opening a new chat and clicking the model dropdown menu at the top of the conversation window. Choose your preferred model from the list available to your subscription plan. In API workflows, pass the exact model string in your request payload. Match the identifier exactly as published in official documentation.
  • If ChatGPT returns errors across all models, the service may be experiencing server disruptions. OpenAI returns code 500 during server outages. Code 503 indicates that a model is temporarily overloaded. Check the OpenAI community for real-time user discussion when widespread failures occur.
  • The model_not_found error means the requested model identifier does not exist on the target server or your API project lacks access to it. It frequently happens when querying a shut-down snapshot or calling a chat model on a completions endpoint. Verify that the model string is spelled accurately. Check the OpenAI deprecations page to confirm the model remains active.

Need Help Fixing Model Errors in Production?

We audit enterprise API integrations, fix routing failures, and configure model access across developer teams.

Book a Consultation