# LLM Model Sunset Scanner: OpenAI, Claude, Gemini (`fifty50labs/llm-model-sunset-scanner`) Actor

Scan a public repo, n8n/Make/Zapier workflow JSON or a list of model IDs for OpenAI, Claude, Gemini and Azure OpenAI models that are retired or shutting down. Get file, line, shutdown date, days left, replacement and official source.

- **URL**: https://apify.com/fifty50labs/llm-model-sunset-scanner.md
- **Developed by:** [Fifty50 Labs](https://apify.com/fifty50labs) (community)
- **Categories:** Developer tools, AI, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $200.00 / 1,000 scan completeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## LLM Model Sunset Scanner

Find OpenAI, Claude, Gemini and Azure OpenAI model IDs in your code or automation workflows that are **already retired or scheduled to shut down**, and get the provider's recommended replacement for each one.

OpenAI's next large batch of shutdowns is on **23 October 2026**. It includes `gpt-3.5-turbo`, `gpt-4`, `gpt-4-turbo`, `gpt-4o-2024-05-13`, `gpt-4.1-nano`, `gpt-image-1`, `o1`, `o1-pro`, `o3-mini`, `o4-mini` and several fine-tuned bases ([OpenAI deprecations](https://developers.openai.com/api/docs/deprecations)). More shutdowns follow every few weeks from OpenAI, Anthropic and Google. On those dates, requests to the retired models start failing.

### What it scans

- **Public GitHub or GitLab repositories**: up to 5 per run. The Actor downloads the repository archive (50 MB limit) and reads source, config and workflow files. `node_modules`, build output, lock files and binaries are skipped.
- **Pasted content**: source code, or an exported **n8n, Make or Zapier** workflow (JSON). For workflow JSON, each hit also names the workflow node or module that holds the model.
- **Raw file URLs**: for example a workflow JSON on `raw.githubusercontent.com` or in a gist.
- **Model IDs (lookup mode)**: check a list of IDs directly, without any code. This is also useful for AI agents that want to check a model name before they write it into code.

### What you get

One dataset row per hit:

| Field | Example |
|---|---|
| `modelId` | `gpt-4-turbo` |
| `provider` | `OpenAI` |
| `file`, `line`, `snippet` | `app/llm.py`, `42`, `model="gpt-4-turbo"` |
| `workflowNodes` | `OpenAI Chat Model (@n8n/n8n-nodes-langchain.lmChatOpenAi)` |
| `shutdownDate` | `2026-10-23` |
| `daysLeft` | `11` (negative means already retired) |
| `severity` | `retired`, `critical` (≤30 days), `soon` (≤90), `scheduled` |
| `replacement` | `gpt-5.6-sol` (as named by the provider) |
| `sourceUrl` | link to the official deprecation page |
| `notes` | aliases, platform differences, conflicting dates on the page |

The `OUTPUT` record in the key-value store holds a summary: the earliest deadline, a per-model roll-up, and a migration checklist you can paste into an issue.

### Where the dates come from

Dates are taken **only from the providers' own deprecation pages**:

- OpenAI: https://developers.openai.com/api/docs/deprecations
- Anthropic (Claude API): https://platform.claude.com/docs/en/about-claude/model-deprecations
- Google Gemini API: https://ai.google.dev/gemini-api/docs/deprecations
- Google Vertex AI: https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions
- Azure OpenAI: https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirement-schedule

Each run fetches these pages first. If a page can't be reached or parsed, the Actor uses a bundled copy and says so: the `dataSources` field in `OUTPUT` shows, for each provider, whether the data was `live` or `bundled` and how old it is. The bundled copy was taken on 12 October 2026.

Only firm dates count. Tentative wording such as "not sooner than" or "no shutdown date announced" is not reported as a deadline.

### How matching works, and its limits

- **Exact IDs** are matched as written in the provider's table. `gpt-4` does not match `gpt-4o`.
- **Aliases** are resolved where the provider's naming makes them clear. For example, `claude-sonnet-4-5` resolves to `claude-sonnet-4-5-20250929`, and `ft:gpt-3.5-turbo-0125:org::id` resolves to its base model. These rows are marked `matchType: alias` or `normalized`.
- **Platform differences are real.** The same Gemini ID can have different dates on the Gemini API and on Vertex AI. For example, `gemini-2.5-flash` retires on Vertex AI on 20 October 2026, but the Gemini API page lists no shutdown date for it. The Actor picks the platform from clues in each file (Vertex SDK imports, Azure endpoints, n8n node types) and lists the other platforms' dates in `otherPlatforms`.
- **Azure OpenAI** dates apply only when a file looks like Azure code. Azure retires each model version separately. When the file doesn't show the version, the Actor shows the earliest upcoming date and lists every version.
- **Amazon Bedrock and Claude on Vertex AI** set their own retirement schedules. For those IDs the Actor shows the Claude API date with a note; check your platform's page before acting.
- **Model names built at runtime** (for example from an environment variable or a database) can't be seen in the code. Look those up in lookup mode.
- Model IDs in docs (`.md`, `.txt`) are skipped unless you turn on **Include docs**.

### Pricing (pay per event)

- **$0.20 per scan**: one repository, one raw file, or one block of pasted content. You are not charged if the repository can't be downloaded or nothing readable is found.
- **$0.005 per model ID** in lookup mode.

Apify's standard Actor start event also applies. Set a maximum charge on the run if you want a hard cap; the Actor stops before going over it.

### Example input

```json
{
  "repoUrls": ["https://github.com/your-org/your-app"],
  "modelIds": ["gpt-4", "claude-sonnet-4-5", "gemini-2.0-flash"],
  "horizonDays": 180
}
```

### Privacy

The Actor reads only the public repository, file or text you give it. It doesn't read git history or commit authors, and it stores only the hits (file path, line, a snippet of up to 160 characters) in your own run's dataset.

### Disclaimer

This tool is not affiliated with OpenAI, Anthropic, Google or Microsoft. Providers can change dates, so check the linked official page before you plan a migration. If a date looks wrong, open an issue on the Actor page and include the model ID.

# Actor input Schema

## `repoUrls` (type: `array`):

Up to 5 public github.com or gitlab.com repositories. Add /tree/<branch> to scan a branch other than the default. Each repository counts as one scan.

## `pastedContent` (type: `string`):

Paste source code or an exported n8n, Make or Zapier workflow (JSON). Counts as one scan.

## `fileUrls` (type: `array`):

Direct links to raw files, such as an n8n workflow JSON on raw.githubusercontent.com or a gist. Each file counts as one scan.

## `modelIds` (type: `array`):

Lookup mode: check model IDs directly, without scanning code (e.g. gpt-4, claude-sonnet-4-5-20250929, gemini-2.0-flash).

## `horizonDays` (type: `integer`):

Report models shutting down within this many days. Already-retired models are always reported.

## `providers` (type: `array`):

Leave empty for all. Options: openai, anthropic, gemini, vertex, azure.

## `includeDocs` (type: `boolean`):

Also report model IDs mentioned in documentation files. Off by default so results focus on code and config.

## `lookupAsAzure` (type: `boolean`):

In lookup mode, prefer the Azure OpenAI retirement schedule over OpenAI's own. In scan mode, Azure dates are used automatically when a file looks like Azure OpenAI code.

## Actor input object example

```json
{
  "repoUrls": [
    "https://github.com/openai/openai-quickstart-python"
  ],
  "horizonDays": 180,
  "includeDocs": false,
  "lookupAsAzure": false
}
```

# Actor output Schema

## `findings` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "repoUrls": [
        "https://github.com/openai/openai-quickstart-python"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("fifty50labs/llm-model-sunset-scanner").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "repoUrls": ["https://github.com/openai/openai-quickstart-python"] }

# Run the Actor and wait for it to finish
run = client.actor("fifty50labs/llm-model-sunset-scanner").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "repoUrls": [
    "https://github.com/openai/openai-quickstart-python"
  ]
}' |
apify call fifty50labs/llm-model-sunset-scanner --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fifty50labs/llm-model-sunset-scanner"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/TkLc5MybTkgixXx0P/builds/dPHKtdLRFjIwrs60g/openapi.json