SunsetDiff

LiteLLM: where a model id lives when a model shuts down

A LiteLLM model shutdown is a string in the model argument, or in litellm_params.model behind a proxy alias. Change the provider string to the official replacement in the table. For one Responses API call, the LiteLLM OpenAI page uses an openai/responses/ prefix.

Last reviewed . Publisher: SunsetDiff.

Steps

  1. Find both strings. A direct call uses the model argument. A proxy client sends model_name. litellm_params.model is the provider string.
  2. Read the shutdown table. Match the provider string, not only the alias the application sends.
  3. Swap the provider string. Put the official replacement in model or in litellm_params.model. You can keep the alias if clients should not change.
  4. Route GPT-6 tool calls. Prefix one call with openai/responses/ when that call must use the Responses API.
  5. Check the id. Check the id with lookup JSON, the MCP check_model tool, or a status badge before you ship the new string.

Where the model id lives

The proxy config page says model_name is the name to pass to LiteLLM from the external client. litellm_params.model is the model string passed to litellm.completion(). A client can keep sending a private alias while the provider id behind it changes.

The OpenAI provider page says a model string with the openai/ prefix calls Chat Completions. Prefix one call with openai/responses/ to send that call to the Responses API. The page shows openai/responses/gpt-6.1-sol for a request that includes tools.

Credentials stay in the environment or in a credential field on the proxy. This page does not show a key.

Proxy shape from the config page, keys removed

model_list:
  - model_name: gpt-6.1-sol
    litellm_params:
      model: openai/gpt-6.1-sol

Sources: LiteLLM proxy config , LiteLLM OpenAI provider , checked October 25, 2026.

How to pin or swap it

To pin a call, put the specific provider id in the model string. To swap a shutdown, replace that id with the official replacement from the table. If applications call a model_name alias, change litellm_params.model and leave the alias in place.

The reliable completions page documents a fallbacks list on completion(). The proxy reliability page documents router_settings.fallbacks, which maps one model_name to another. Samples for both are on the swap guide.

Sources: LiteLLM proxy config , LiteLLM reliable completions , LiteLLM proxy fallbacks , checked October 25, 2026.

GPT-6 function tools

Use openai/responses/ plus the model id when the call includes function tools for a model OpenAI says must use the Responses API. The OpenAI provider page shows that prefix on gpt-6.1-sol.

OpenAI's Using GPT-6 guide says GPT-6 Astra and GPT-6.1 Sol tool calling requires the Responses API. GPT-6 Sol and GPT-6 Luna can keep function tools on Chat Completions only with reasoning effort none. The error pages quote the failure and the working requests.

Python, Responses prefix from the LiteLLM OpenAI page

import litellm
response = litellm.completion(
    model="openai/responses/gpt-6.1-sol",
    messages=[{"role": "user", "content": "Hello"}],
)

Sources: LiteLLM OpenAI provider , Using GPT-6 , checked October 25, 2026.

Upcoming shutdowns in this dataset

gpt-4.1-2025-04-14, gpt-4.1-mini-2025-04-14, gpt-4o-2024-08-06, gpt-4o-2024-11-20, and gpt-4o-mini-2024-07-18 shut down on 2027-01-14. The official replacement on these rows is gpt-6-luna.

gpt-4.1, gpt-4.1-mini, gpt-4o, and gpt-4o-mini have no shutdown date on their own records. A request that sends the short id is not the dated snapshot row. Open the model page before you treat the short id as shut down.

Rows are upcoming OpenAI chat models in the gpt-4o, gpt-4.1, gpt-4-turbo, gpt-4, and gpt-3.5-turbo families. Audio, realtime, transcribe, and search ids are not in this table. The same id on another platform is in the other-platforms column. The full calendar is upcoming shutdowns. Provider wording for the shutdown day is on what happens on shutdown day.

5 upcoming OpenAI chat shutdowns from this dataset.
Shutdown Provider Model Replacement Other platforms
2027-01-14
source, checked 2026-10-26
OpenAI GPT-4.1 (gpt-4.1-2025-04-14)
gpt-4.1-2025-04-14
gpt-6-luna
Switch guide: gpt-6-luna
Azure OpenAI: shuts down on 2027-10-14
2027-01-14
source, checked 2026-10-26
OpenAI GPT-4.1 mini (gpt-4.1-mini-2025-04-14)
gpt-4.1-mini-2025-04-14
gpt-6-luna
Switch guide: gpt-6-luna
Azure OpenAI: shuts down on 2027-10-14
2027-01-14
source, checked 2026-10-26
OpenAI GPT-4o (gpt-4o-2024-08-06)
gpt-4o-2024-08-06
gpt-6-luna
Switch guide: gpt-6-luna
Azure OpenAI: shuts down on 2027-10-01
2027-01-14
source, checked 2026-10-26
OpenAI GPT-4o (gpt-4o-2024-11-20)
gpt-4o-2024-11-20
gpt-6-luna
Switch guide: gpt-6-luna
Azure OpenAI: shuts down on 2027-04-14
2027-01-14
source, checked 2026-10-26
OpenAI GPT-4o mini (gpt-4o-mini-2024-07-18)
gpt-4o-mini-2024-07-18
gpt-6-luna
Switch guide: gpt-6-luna
Azure OpenAI: shuts down on 2027-10-01

Detect a dying model

These checks read SunsetDiff. They do not call the model provider.

Related SunsetDiff pages

Other frameworks

All frameworks

Questions

Which LiteLLM field is the provider model id?

On a direct call, the model argument. On the proxy, litellm_params.model. model_name is the alias clients send. Source: the proxy config page.

How does LiteLLM call the Responses API?

Prefix the model string with openai/responses/. The OpenAI provider page shows openai/responses/gpt-6.1-sol.

Where do the dates in the shutdown table come from?

From SunsetDiff model records for upcoming OpenAI chat ids in the gpt-4o, gpt-4.1, gpt-4-turbo, gpt-4, and gpt-3.5-turbo families. The sentence above the table is built from those records when the site is built. Each row links the provider source stored on that record.

How do I check one model id from this page?

Open lookup JSON and replace gpt-4o with your id. Or call check_model on the MCP server. Or use a status badge. No API key.