Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Anthropic Google OpenAI

Providers

Anthropic 29 Google 24 OpenAI 103
OpenAI gpt-3.5-turbo-0613

GPT-3.5 Turbo (0613) (OpenAI)

Retired

Yes — GPT-3.5 Turbo (0613) is retired. OpenAI deprecated it on November 6, 2023 and shut it down on September 13, 2024; API requests to it now fail. The recommended replacement is GPT-3.5 Turbo.

The June 2023 snapshot that introduced function calling to the API — the feature every agent framework since has been built on. Retired September 2024 along with its 16k variant.

The facts

Provider OpenAI
Model id gpt-3.5-turbo-0613
Also published as gpt-3.5-turbo-16k-0613
Released June 13, 2023
Deprecated November 6, 2023
Shutdown September 13, 2024 · 685 days ago
Status Retired
Last verified July 30, 2026

What to use instead

OpenAI GPT-3.5 Turbo gpt-3.5-turbo Provider-recommended Deprecated

The undated pointer was the named successor and is itself now deprecated, shutting down October 2026. Plan for gpt-5.6-terra instead.

What parameters gpt-3.5-turbo accepts on modelparams.dev

Change the id

In most cases the migration is one string. Check the parameter differences before you ship — newer models drop older sampling knobs more often than they add them. 

- "model": "gpt-3.5-turbo-0613"
+ "model": "gpt-3.5-turbo"

Where the migration path ends

The recommended successor has itself been replaced. Following the chain to a model that is still active today:

  1. gpt-3.5-turbo-0613
  2. gpt-3.5-turbo Deprecated
  3. gpt-5.6-terra Active

Frequently asked questions

When did OpenAI GPT-3.5 Turbo (0613) shut down?
OpenAI GPT-3.5 Turbo (0613) shut down on September 13, 2024. API requests to it fail from that date onward.
What replaces OpenAI GPT-3.5 Turbo (0613)?
OpenAI recommends GPT-3.5 Turbo (`gpt-3.5-turbo`) as the replacement for OpenAI GPT-3.5 Turbo (0613). The undated pointer was the named successor and is itself now deprecated, shutting down October 2026. Plan for gpt-5.6-terra instead.
Is OpenAI GPT-3.5 Turbo (0613) still available?
No. OpenAI GPT-3.5 Turbo (0613) is retired and no longer served — it was shut down on September 13, 2024. Calls to it return an error.
How do I migrate from OpenAI GPT-3.5 Turbo (0613) to gpt-3.5-turbo?
Swap the model id in your API call: replace "gpt-3.5-turbo-0613" with "gpt-3.5-turbo". The undated pointer was the named successor and is itself now deprecated, shutting down October 2026. Plan for gpt-5.6-terra instead.
Does this apply to gpt-3.5-turbo-16k-0613 too?
Yes. OpenAI GPT-3.5 Turbo (0613) is also published as `gpt-3.5-turbo-16k-0613`; that id shares the same lifecycle dates as `gpt-3.5-turbo-0613`.

Sources

Found something wrong? The data is one YAML file — edit it on GitHub.

This page, for machines

JSON Markdown Badge JSON

Drop the badge in a README so it turns red the day this model is retired:

[![gpt-3.5-turbo-0613](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-3.5-turbo-0613.json)](https://modeldeprecations.dev/openai/gpt-3.5-turbo-0613)

Other OpenAI models

All OpenAI deprecations →

How to use this site

The full guide, in Markdown. Copy it and hand it to a coding agent verbatim.

# How to use modeldeprecations.dev

[modeldeprecations.dev](https://modeldeprecations.dev) answers one question per model: is it deprecated,
when does it shut down, and what replaces it. Every date on the site is cited to the
provider's own documentation, with the date we last checked it.

Three lifecycle states are used, matching the providers' own vocabulary:

- **active** — still supported, no deprecation announced.
- **deprecated** — the provider has announced it is going away. It still answers requests.
- **retired** — API access is gone. Requests fail.

A model can be active *and* carry a shutdown date: Anthropic publishes a
"not sooner than" date and Google publishes an earliest shutdown date for models
that are current and fully supported. Those are reported as scheduled shutdowns,
not deprecations, because that is what the provider actually committed to.

## Check one model

```bash
curl https://modeldeprecations.dev/api/v1/models/openai/gpt-4-32k.json
```

Or fetch the page as Markdown, which includes the answer, the dates and the sources:

```bash
curl https://modeldeprecations.dev/openai/gpt-4-32k.md
```

## Full catalog

```bash
curl https://modeldeprecations.dev/api/v1/models.json
```

Ids are `provider/model`. Dated snapshots (`gpt-4-32k-0613`) are listed as aliases of
their canonical entry rather than as separate records.

Each entry carries `computed_status`, the lifecycle state recomputed against the build
date — so a model whose shutdown has passed reads `retired` without anyone editing data.

## Badges

A shields.io endpoint per model, for READMEs that should go red when a model dies:

```
https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-4-32k.json
```

## Calendar and changelog

- Subscribe to every shutdown date: https://modeldeprecations.dev/calendar.ics
- Changelog RSS: https://modeldeprecations.dev/changelog.xml

## JSON Schema

```bash
curl https://modeldeprecations.dev/api/v1/schema.json
```

## Contribute

Data lives in YAML under `models/{provider}/{model}.yaml` in the
[GitHub repo](https://github.com/mnfst/modeldeprecations.dev). Every lifecycle date needs a source URL; CI rejects a
date without one. Open a PR.

## For agents

- Machine-readable overview: https://modeldeprecations.dev/llms.txt
- This guide plus every model inline: https://modeldeprecations.dev/llms-full.txt
- Any page also exists as Markdown: append `.md` to a model URL.
- In a browser, this site registers a **WebMCP** tool on `navigator.modelContext`:
  `check_model_deprecation`, `list_shutdowns`, `find_replacement`, and `get_usage_guide`.
- Parameters each model accepts are catalogued on the sibling site, https://modelparams.dev.