OpenAI shut down the Assistants API on August 26, 2026. Compare migration paths: Responses API, Claude, Gemini, open-source frameworks. Free tier comparison for 10+ AI API providers with stability ratings.

OpenAI Assistants API Sunset: Migration Guide & Free Alternatives

Published 2026-04-02 · Not yet reviewed · Figures in the tables below come from our records for 1,498 developer tools · 19 OpenAI pricing changes tracked

Shut down
August 26, 2026
OpenAI stability: VOLATILE
Shut down
August 26, 2026
12
Alternatives Compared
6
Free or Trial Tiers
4
Migration Paths

What’s happening: OpenAI deprecated the Assistants API in favor of the Responses API. OpenAI shut down the Assistants API on August 26, 2026; it is no longer available. All developers using Threads, persistent Assistants, Code Interpreter, or File Search through the Assistants API must migrate.

Key insight: The Responses API is a direct replacement with feature parity plus new capabilities (MCP support, deep research, computer use). Most developers should migrate to Responses API first — then evaluate whether to diversify to other providers for cost or capability reasons.

Our data says: OpenAI’s stability rating is volatile based on 19 tracked pricing changes — including free tier credit removal, ChatGPT ad insertion, and now this API sunset. Developers building on OpenAI should have a diversification plan.

Jump to section

  1. What’s Changing
  2. Migration Paths (Decision Tree)
  3. Free Tier Comparison Table
  4. OpenAI Pricing Change Timeline
  5. Which Alternative for Which Developer
  6. Methodology

What’s Changing

The Assistants API provided a stateful, session-based interface for building AI agents. OpenAI is replacing it with the Responses API — a stateless, more flexible approach. Here’s what breaks and what replaces it:

Assistants API Feature What Breaks Responses API Replacement
Threads Persistent conversation state deleted Conversations API (or manage context yourself)
Persistent Assistants Assistant objects no longer exist Prompts + system instructions per request
Code Interpreter Built-in code execution removed Code interpreter tool in Responses API
File Search Vector store file search removed File search tool in Responses API
Function Calling Same concept, different API shape Function calling (compatible pattern)
Run Lifecycle Polling-based run management removed Streaming-first, simpler lifecycle
Azure OpenAI users: Azure follows OpenAI’s deprecation timeline. Microsoft retired the Azure OpenAI Assistants API on August 26, 2026 as well, so an Azure deployment does not extend the deadline. Move agents to Microsoft Foundry Agent Service; the Azure OpenAI Responses API mirrors OpenAI’s implementation for inference only.

Migration Paths

Four paths depending on your constraints. The first path (stay with OpenAI) requires the least code changes. The others offer different trade-offs between cost, capability, and vendor independence.

Path 1: Stay with OpenAI — Migrate to Responses API

Direct replacement with feature parity. Threads → Conversations API. Assistants → prompts + system instructions. Code Interpreter and File Search tools carry over. New capabilities: MCP support, deep research, computer use.

Best for: Teams heavily invested in OpenAI ecosystem, production apps where minimizing migration risk matters most

Path 2: Diversify to Another AI API

Claude (best reasoning, long context), Gemini (free tier, multimodal), Cohere (RAG/enterprise search). Each has native tool use/function calling. Requires API integration changes but not architectural rewrites.

Best for: Teams wanting to reduce single-vendor dependency, those needing specific capabilities (long context, multimodal, search)

Path 3: Go Open Source

LangChain, CrewAI, AutoGen, or custom orchestration with open-source models via Ollama, vLLM, or llama.cpp. Full control over the stack. No vendor lock-in. Run locally or on your own infrastructure.

Best for: Teams with ML ops capability, privacy-sensitive workloads, cost-conscious at scale

Path 4: Multi-Provider Abstraction

OpenRouter or LiteLLM as a unified API layer across multiple LLM providers. Switch models without code changes. Compare pricing and latency across providers. Reduces lock-in to any single API.

Best for: Teams wanting flexibility to switch providers, cost optimization across multiple models

Free Tier Comparison Table

All 12 alternative AI API providers compared. The tier and paid-rate columns are read from each provider's record in our index at request time, and the stability ratings come from our stability dashboard. A dash means the record carries no paid rate; the link goes to the vendor's own pricing page. Click provider names for full vendor profiles.

Provider Recorded Tier Paid Rate Tool Use Code Execution Stability
OpenAI (Responses API) Pay-as-you-go gpt-6-luna $0.10/$0.50 – gpt-6-astra $10.00/$50.00 per MTok Native (function calling) Code interpreter tool volatile
  • OpenAI does not use data sent to the API to train its models unless you opt in to share data. (From developers.openai.com/api/docs/guides/your-data, read 2026-10-06.)
  • Abuse monitoring logs may contain prompts and responses and are kept for up to 30 days by default. (From developers.openai.com/api/docs/guides/your-data, read 2026-10-06.)
  • New API accounts use prepaid billing. Purchased credits expire after 1 year and are non-refundable unless required by law, contract, or an approved exception. (From help.openai.com/en/articles/8264644-how-can-i-set-up-prepaid-billing, read 2026-10-06.)
  • Without ChatGPT subscriber credits, OpenAI's API needs a payment method and a credit purchase of at least $5 before you use it. (From help.openai.com/en/articles/8264644-setting-up-and-managing-prepaid-api-billing, read 2026-10-22.)
  • OpenAI's API credits for ChatGPT subscribers need an active, paid ChatGPT Pro or Business subscription at least seven days old. The owner of the subscription or Business workspace links it to one API organization they own, using the same email. ChatGPT Plus, Go, Free and Enterprise plans, free trials and complimentary subscriptions are not eligible. No API payment method is needed while the credits last. Unused credits expire at the end of the billing cycle and do not roll over. They do not cover Codex used with an API key. (From developers.openai.com/api/docs/guides/chatgpt-api-credits, read 2026-10-29.)
  • gpt-6.2-astra, gpt-6.2-sol, gpt-6.1-terra and gpt-6-luna have 2-hour and 8-hour background completion windows. The 2-hour window is 30% below Standard. The 8-hour window is 40% below Standard. These windows are in public beta. They require Standard processing. They share the Batch/Background Rate Limit with Batch API jobs. (From developers.openai.com/api/docs/pricing, read 2026-11-18.)
Anthropic Claude API Pay-as-you-go Claude Haiku 5.5 $0.10/$0.50 – Claude Fable 5.1 $10/$50 per MTok Native (tool use) Computer use, code execution volatile
  • Monthly credits with Claude Max, Ultra and Team plans pay for the Claude API, Claude Managed Agents and the Claude Agent SDK. That includes `claude -p` run with an API key from the Console organization linked to the plan. `claude -p` run while signed in with the plan uses the plan's usage limits, not the credits. The credits do not pay for interactive Claude Code, runs started by the Claude Code GitHub Action, an IDE extension or the desktop app, extra usage, or third-party apps billed through linked billing. They expire at the end of each billing cycle. New subscribers can claim them after seven days on the plan, with no payment method. Free, Pro and Enterprise plans are not eligible. (From support.claude.com/en/articles/17154008-monthly-api-credits-for-max-ultra-and-team-plans, read 2026-11-18.)
  • Anthropic's Claude API needs prepaid credits, bought with a payment method, before you use it. (From support.claude.com/en/articles/8977456-how-do-i-pay-for-my-claude-api-usage, read 2026-10-22.)
Google Gemini API Free (Reduced) Gemini 3.1 Flash-Lite $0.25/$1.50 – Gemini 3.1 Pro Preview $2/$12 per MTok Native (function calling) Code execution tool watch
  • The Gemini API Free Tier needs no credit card or billing account; linking a billing account and prepaying moves you to the Paid Tier. (From ai.google.dev/gemini-api/docs/billing, read 2026-10-22.)
  • Google's pricing page says free-tier content is used to improve Google's products. (From ai.google.dev/gemini-api/docs/pricing, read 2026-10-04.)
  • For developers outside the European Economic Area, Switzerland and the United Kingdom, Google's terms say human reviewers may read free-tier prompts and responses, and Google says not to send sensitive, confidential or personal information on the free tier. (From ai.google.dev/gemini-api/terms, read 2026-10-04.)
  • Paid-tier projects created on or after October 26, 2026, store Generate Content API requests and responses by default. Projects created before that date keep their existing Generate Content API storage setting, which is off unless it was turned on in AI Studio. The Interactions API stores requests by default in all projects, including projects created before October 26, 2026. The Paid Tier keeps stored interactions for 55 days and the Free Tier for 1 day. Logging also covers calls made through OpenAI compatibility endpoints. Logs are retained for up to 55 days, configurable to 7, 14 or 28 days. Logs are not used to improve Google's products unless shared. Logging can be toggled independently for each API in AI Studio, and store=false on a request turns it off for that request. (From ai.google.dev/gemini-api/docs/logs-policy, read 2026-11-06.)
  • Apps that serve users in the European Economic Area, Switzerland or the United Kingdom may use only the paid tier. (From ai.google.dev/gemini-api/terms, read 2026-10-04.)
  • Google's terms require users to be 18 years of age or older to use the Gemini API and Google AI Studio. The API may not be used in a website, app, or other service directed towards or likely to be accessed by individuals under 18. These rules apply to both the free and paid tiers. (From ai.google.dev/gemini-api/terms, read 2026-10-17.)
  • Google offers the Gemini API and Google AI Studio, free and paid, in 230 countries and territories, including Taiwan, Brazil, Japan, Singapore, and the United Kingdom. China, Hong Kong, Macao, Russia, Belarus, and Iran are not among them. Google says to developers outside the list: "try the Gemini API in Gemini Enterprise Agent Platform". (From ai.google.dev/gemini-api/docs/available-regions, read 2026-10-17.)
  • Google's terms say changes to Gemini API paid prices take effect 30 days after Google posts them unless Google specifies otherwise. Pricing for a new paid service takes effect immediately unless Google specifies otherwise. (From ai.google.dev/gemini-api/terms, read 2026-10-17.)
  • Google is moving existing Postpay accounts to Prepay for Gemini API usage. An account that has not switched and added credits by the cutover date in its account notice has its paid service interrupted; other Google Cloud services on the billing account stay on Postpay. (From ai.google.dev/gemini-api/docs/billing, read 2026-10-07.)
  • When the Prepay balance reaches $0, every API key in every project on the billing account stops working until credits are added; requests then fail with an HTTP 402 Payment Required error. (From ai.google.dev/gemini-api/docs/billing, read 2026-10-07.)
  • The monthly Google Cloud credits from Google AI Pro or Ultra are eligible Google Cloud credits. On the Prepay billing plan, these credits pay for Gemini API usage only after you buy Prepay credits in AI Studio. With a $0 Prepay balance, requests fail even with unused Google Cloud credits, according to a Google staff member on discuss.ai.google.dev. (From discuss.ai.google.dev/t/error-code-402-message-your-prepayment-credits-are-depleted/185524, read 2026-10-10.)
  • A paid project does not automatically revert to the free tier, even when its Prepay balance reaches $0. To use the free tier, disable billing on the project, which unlinks it from its billing account. (From ai.google.dev/gemini-api/docs/billing, read 2026-10-10.)
  • Disabling billing on a Google Cloud project stops all other paid Google Cloud services in it. Some resources may be deleted and become non-recoverable. Outstanding charges are still due. (From cloud.google.com/billing/docs/how-to/modify-project, read 2026-10-10.)
GitHub Models Retired — Via hosted models No built-in retired
OpenRouter Free — vendor pricing Model-dependent Model-dependent stable
  • OpenRouter's free models need no credit card. (From openrouter.ai/blog/tutorials/free-llm-apis-compared, read 2026-10-22.)
  • A request over a free-model limit gets a 429 error with the message "Rate limit exceeded". The daily limit counts by UTC day. (From openrouter.ai/docs/api-reference/limits, read 2026-10-29.)
  • The paid variant of a model has no platform-level request cap. (From openrouter.ai/docs/api-reference/limits, read 2026-10-29.)
  • With a negative credit balance, requests can fail, including for free models; adding credits to bring the balance above zero restores access. (From openrouter.ai/docs/api-reference/limits, read 2026-10-29.)
  • OpenRouter does not store your prompts or responses unless you opt in to Private Input & Output Logging or OpenRouter Use of Inputs/Outputs, or content is flagged as potential CSAM. Both opt-ins are off by default. OpenRouter Use of Inputs/Outputs lets OpenRouter use prompt and completion data to improve the product, for a 1% discount on model usage. OpenRouter stores request metadata without prompt or response content. (From openrouter.ai/docs/guides/privacy/data-collection, read 2026-10-30.)
  • Each provider has its own data handling policies. OpenRouter works with providers so that prompts are not trained on wherever possible, but there are exceptions. Account settings control routing to providers that may train on your data, separately for paid and free models. If you opt out of training, OpenRouter will not route to those providers. (From openrouter.ai/docs/guides/privacy/provider-logging, read 2026-10-30.)
Cohere Free Command R7B $0.0375/$0.15, Command R $0.15/$0.60 per MTok Native (tool use) No built-in stable
  • Cohere's Trial API keys may not be used for production or commercial purposes. (From cohere.com/pricing, read 2026-10-04.)
  • Cohere creates a free Trial API key with each new account; no credit card is needed. (From cohere.com/pricing, read 2026-10-22.)
Groq Free gpt-oss-20b $0.075/$0.30, gpt-oss-120b $0.15/$0.60, Qwen3.8 27B $0.80/$4.00 per MTok Native (function calling) No built-in volatile
  • Groq rate limits apply to the whole organization, not per user or API key. A request over the limit returns a 429 Too Many Requests error. Cached tokens do not count toward rate limits. (From console.groq.com/docs/rate-limits, read 2026-11-04.)
  • You are billed only after you add a payment method and move to the paid Developer tier. (From console.groq.com/docs/billing-faqs, read 2026-10-05.)
  • Groq's Services Agreement does not permit it to train or fine-tune models on your inputs or outputs unless you give permission. (From console.groq.com/docs/legal/services-agreement, read 2026-10-05.)
  • Groq's Services Agreement grants use of Groq APIs to integrate its services into customer applications for end users. Its restrictions do not prohibit commercial use. (From console.groq.com/docs/legal/services-agreement, read 2026-10-29.)
  • Customers may not resell access to their Groq account. Groq's Services Agreement prohibits selling, reselling, or transferring its services except with Groq's express approval. (From console.groq.com/docs/legal/services-agreement, read 2026-10-29.)
  • Groq does not retain inference requests by default. Batch input and output files are kept for 30 days unless deleted earlier. Fine-tuning data is kept until deleted. Groq may log inference inputs and outputs for up to 30 days to troubleshoot errors or investigate abuse. Zero Data Retention stops this logging and disables the Batch API and fine-tuning. (From console.groq.com/docs/your-data, read 2026-11-04.)
  • Data Groq retains is stored in Google Cloud buckets in the United States. (From console.groq.com/docs/your-data, read 2026-10-05.)
Fireworks AI Free Credits $0.05/$0.20 – Fireworks serverless serves Kimi K3 $3.00/$15.00 per MTok Native (function calling) No built-in unrated
Together AI Pay-as-you-go gpt-oss-120B $0.15/$0.60 – Together AI serverless serves Kimi K3 $3.00/$15.00 per MTok Native (function calling) No built-in volatile
Mistral AI Pay-as-you-go Ministral 3 $0.1/$0.1 – Mistral Medium 3.5 $1.5/$7.5 per MTok Native (function calling) No built-in volatile
  • Since August 2026, Mistral offers Mistral AI Studio and its API only to business customers. Its consumer terms for personal use exclude both, and API use falls under the Commercial Terms for an organization, company or other entity. (From legal.mistral.ai/terms/row-consumer-terms, read 2026-10-11.)
  • A business can use Mistral's API in a commercial product; individuals cannot use the API for personal projects. (From legal.mistral.ai/terms/commercial-terms-of-service, read 2026-10-11.)
  • Models whose names start with "labs-" are free of charge once you have API access; Mistral calls them experimental and not for production. (From docs.mistral.ai/inference/model-lifecycle, read 2026-11-12.)
  • In Free mode, Mistral may use your Studio inputs and outputs to train its models, and you can opt out at any time. (From help.mistral.ai/en/articles/347617-do-you-use-my-user-data-to-train-your-artificial-intelligence-models, read 2026-11-12.)
  • Mistral may train on inputs and outputs from Labs or Preview Models, which its Commercial Terms define as experimental, preview or pre-release models identified as such, including those with the "labs" prefix, even if you opted out or use zero data retention. Mistral Large 4 is a public preview. (From legal.mistral.ai/terms/commercial-terms-of-service, read 2026-10-11.)
  • Pay-as-you-go uses prepaid credits. Your monthly usage is consumed first. API and Vibe Code requests beyond it fail with HTTP 402 if your credit balance is zero. Add credits to restore access. Auto Recharge charges your payment method when your balance falls below a set threshold. (From docs.mistral.ai/admin/billing-usage/billing, read 2026-11-04.)
DeepSeek API Pay-as-you-go DeepSeek-V4.1-Flash $0.30/$1.20, DeepSeek-V4-Pro $1.32/$3.96 per MTok Native (function calling) No built-in volatile
  • Since November 1, 2026, 00:00 Beijing time (16:00 UTC on October 31), server-side Search and Fetch calls via DeepSeek Harness, Claude Code, or Codex are billed at $0.75 per 1,000 successful requests; they were free until then. (From api-docs.deepseek.com/quick_start/pricing, read 2026-11-01.)
  • DeepSeek's Search API and Fetch API are standalone APIs billed per request. Search finds web pages for a query; Fetch retrieves one web page as Markdown. Each costs $0.75 per 1,000 successful requests. Failed requests, empty search results, and timeouts are not billed. (From api-docs.deepseek.com/guides/search, read 2026-10-17.)
  • DeepSeek's Terms of Use, which also govern its API, let DeepSeek use inputs and outputs, de-identified and "to a minimal extent", to develop or improve its services and the technologies behind them. The terms say a user opts out by turning off "Improve the model for everyone". (From cdn.deepseek.com/policies/en-US/deepseek-terms-of-use.html, read 2026-10-23.)
  • DeepSeek's privacy policy says it collects, processes and stores personal data in the People's Republic of China. (From cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html, read 2026-10-23.)
Cerebras Trial GPT OSS 120B $0.35/$0.75, Qwen 3.8 27B $0.99/$1.49 per MTok Via Llama models No built-in volatile
  • Cerebras's pricing page puts its $5 trial credit and pay-as-you-go pricing on its Developer tier, which it says is not intended for production use, and puts production workloads on its Enterprise tier, priced by quote. (From cerebras.ai/pricing, read 2026-10-09.)
  • Cerebras's terms give it no right to use API inputs and outputs to train or fine-tune models. (From cerebras.ai/terms-of-service, read 2026-10-04.)
  • Cerebras's privacy policy says it does not retain inference inputs and outputs. (From cerebras.ai/privacy-policy, read 2026-10-04.)
  • Free Trial context windows are 65K tokens for gpt-oss-120b and 64K for qwen-3.8-27b. Paid accounts get 131K and 128K. (From inference-docs.cerebras.ai/models/overview, read 2026-10-11.)
  • Cerebras Code's Pro ($50, up to 24 million tokens a day) and Max ($200, up to 120 million tokens a day) plans were marked "sold out" on cerebras.ai/code on 2026-10-22. cerebras.ai/code still names GLM 4.7 as the model, but Cerebras's API no longer serves GLM 4.7. (From cerebras.ai/code, read 2026-10-22.)
  • Cerebras requires a payment method before API access, including its $5 free trial credits. (From inference-docs.cerebras.ai/support/rate-limits, read 2026-10-22.)
Assistants API feature mapping: If you relied on Code Interpreter, OpenAI's Responses API, Google Gemini and Anthropic's code execution tool offer direct equivalents. For File Search, Claude handles PDFs natively, Gemini is multimodal (images, audio, video), and Cohere specializes in document RAG. For Threads/conversation state, most providers are stateless — you’ll manage context yourself or use Conversations API (OpenAI only).
Cost comparison at scale: At 100M input and 100M output tokens a month, the cheapest rate our index holds for the providers above is Command R7B at $19, and the dearest is Claude Fable 5.1 at $6,000. OpenRouter carry no per-token price in our index, so what you pay above the free tier is on the vendor's own page.

OpenAI Pricing Change Timeline

OpenAI’s stability rating is volatile. We’ve tracked 19 changes. Here’s the full history:

Date Change Impact
effective Oct 23, 2026 The OpenAI API keeps running. The gpt-3.5-turbo, gpt-4, gpt-4-turbo, gpt-4-1106-preview, gpt-4.1-nano, gpt-4o-2024-05-13, gpt-image-1, o1, o1-pro, o3-mini and o4-mini models, with their fine-tuned versions, can be called until October 23, 2026, when OpenAI shuts down their access. OpenAI names a substitute for each model: gpt-3.5-turbo to gpt-5.6-terra; gpt-4, gpt-4-turbo, gpt-4-1106-preview and gpt-4o-2024-05-13 to gpt-5.6-sol; gpt-4.1-nano to gpt-5.6-luna; gpt-image-1 to gpt-image-2.5-sunburst or gpt-image-2.5-flare; o1 to gpt-5.6-sol; o1-pro to gpt-5.6-sol with reasoning.mode: pro; o3-mini to gpt-5.6-sol; o4-mini to gpt-5.6-terra. Source ↗ MEDIUM
effective Sep 28, 2026 gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106 shut down in the OpenAI API on September 28, 2026. OpenAI names gpt-5.6-terra as the replacement. Source ↗ LOW
effective Sep 24, 2026 Sora 2 video generation in the OpenAI API shut down on September 24, 2026: OpenAI removed the Videos API and the sora-2 and sora-2-pro models, and names no replacement. Source ↗ MEDIUM
effective Aug 26, 2026 Assistants API deprecated, full shutdown August 26, 2026. Developers must migrate to Responses API + Conversations API Source ↗ HIGH
effective May 12, 2026 dall-e-2 and dall-e-3 were removed from the OpenAI API on 2026-05-12. OpenAI names gpt-image-2, gpt-image-1 or gpt-image-1-mini as substitutes, and gpt-image-1 itself shuts down on 2026-10-23. Source ↗ HIGH
effective May 12, 2026 The Realtime API beta was removed on 2026-05-12; OpenAI's generally available Realtime API replaces it. Source ↗ HIGH
effective Mar 20, 2024 Between 2024-03-13 and 2024-03-20, OpenAI stopped giving new API accounts the $5 free trial credit, which could be used during an account's first 3 months. New accounts now have to buy prepaid credits, $5 minimum, to use any paid model. Source ↗ HIGH

Upcoming Changes

These are announced changes that have not taken effect yet, listed soonest first.

Date Change Impact
effective Nov 30, 2026 The OpenAI API keeps running. Agent Builder, the Evals platform and the v1/prompts API can be used until November 30, 2026. Existing evals become read-only on October 31, 2026. ChatKit remains available. Migrate from Agent Builder to the Agents SDK or ChatGPT Workspace Agents. Migrate from Evals to Promptfoo. Move reusable prompt content into application code. Source ↗ LOW
effective Dec 1, 2026 The OpenAI API keeps running. The gpt-image-1-mini, gpt-image-1.5 and chatgpt-image-latest models can be called until December 1, 2026. OpenAI's substitutes are gpt-image-2.6-sunburst or gpt-image-2.6-flare. Source ↗ LOW
effective Dec 1, 2026 OpenAI's promotional pricing for gpt-5.6-sol on the OpenAI API ends on November 30, 2026. Until then, gpt-5.6-sol costs $4.00 per million input tokens, $0.40 per million cached input tokens and $20.00 per million output tokens on Standard processing, and $2.00, $0.20 and $10.00 on Flex and Batch. OpenAI has not said what gpt-5.6-sol costs from December 1, 2026. OpenAI's note covers gpt-5.6-sol on the OpenAI API only and says nothing about Azure OpenAI. Source ↗ MEDIUM
effective Dec 11, 2026 The OpenAI API keeps running. gpt-5 and gpt-5-2025-08-07 are available until December 11, 2026, replaced by gpt-6.1-sol. gpt-5-mini and gpt-5-mini-2025-08-07 are available until December 11, 2026, replaced by gpt-6.1-terra. gpt-5-nano and gpt-5-nano-2025-08-07 are available until December 11, 2026, replaced by gpt-6-luna. gpt-5-pro and gpt-5-pro-2025-10-06 are available until December 11, 2026, replaced by gpt-6.1-sol with reasoning.mode: pro in the Responses API. o3 and o3-2025-04-16 are available until December 11, 2026, replaced by gpt-6.1-sol. o3-pro and o3-pro-2025-06-10 are available until December 11, 2026, replaced by gpt-6.1-sol with reasoning.mode: pro in the Responses API. o3-mini is a different model from o3, and OpenAI shut it down on October 23. Source ↗ MEDIUM
effective Jan 6, 2027 The OpenAI API keeps running. The tts-1, tts-1-hd, gpt-4o-mini-tts-2025-03-20 and gpt-4o-mini-tts-2025-12-15 models can be called until January 6, 2027. OpenAI's replacement for each: gpt-realtime-2.1-mini. Source ↗ LOW
effective Jan 6, 2027 The OpenAI API keeps running. From January 6, 2027, no organization can create new fine-tuning jobs on OpenAI's self-serve fine-tuning platform. Since May 7, 2026, organizations that never ran fine-tuning cannot create jobs. Since July 2, 2026, organizations that have not run inference on a fine-tuned model in the past 60 days cannot either. Fine-tuned models keep serving inference until their base model is deprecated. Source ↗ MEDIUM
effective Jan 14, 2027 The OpenAI API keeps running. The gpt-4o (gpt-4o-2024-08-06 and gpt-4o-2024-11-20), gpt-4o-mini, gpt-4.1 and gpt-4.1-mini models, with their fine-tuned versions, can be called until January 14, 2027, when OpenAI shuts down their access. OpenAI names gpt-6-luna as the replacement for all four. Source ↗ MEDIUM
effective Jan 20, 2027 The OpenAI API keeps running. The gpt-realtime, gpt-4o-realtime, gpt-realtime-mini, gpt-4o-mini-realtime, gpt-audio, gpt-4o-audio, gpt-audio-mini, gpt-4o-mini-audio and gpt-4o-mini-transcribe-2025-03-20 models can be called until January 20, 2027. OpenAI's substitutes: gpt-realtime-2.1 for gpt-realtime and gpt-4o-realtime; gpt-realtime-2.1-mini for gpt-realtime-mini and gpt-4o-mini-realtime; gpt-audio-1.5 for gpt-audio, gpt-4o-audio, gpt-audio-mini and gpt-4o-mini-audio; gpt-4o-mini-transcribe-2025-12-15 for gpt-4o-mini-transcribe-2025-03-20. Source ↗ LOW
effective Feb 1, 2027 The OpenAI API keeps running. The gpt-5.5-cyber-preview model can be called until February 1, 2027, when OpenAI removes it from the API. OpenAI tells users to move to the most capable cyber model available to them. Source ↗ LOW
effective Feb 10, 2027 The OpenAI API keeps running. The gpt-image-2 model and its gpt-image-2-2026-04-21 snapshot can be called until February 10, 2027, when OpenAI removes them from the API. OpenAI names gpt-image-2.6-sunburst or gpt-image-2.6-flare as the replacement. Source ↗ MEDIUM
effective Feb 26, 2027 The OpenAI API keeps running. The whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe and gpt-4o-transcribe-diarize models can be called until February 26, 2027. OpenAI's substitute for each is gpt-live-transcribe or gpt-transcribe. The /v1/audio/translations endpoint also shuts down on February 26, 2027. OpenAI's replacement is /v1/realtime/translations. Source ↗ MEDIUM
effective Apr 1, 2027 The OpenAI API keeps running. The gpt-5.3-codex, gpt-5.1 and gpt-5.4-nano models can be called until April 1, 2027. OpenAI's replacements: gpt-6-sol for gpt-5.3-codex and gpt-5.1; gpt-6-luna for gpt-5.4-nano. Source ↗ MEDIUM

Which Alternative for Which Developer

Recommendations by Use Case

Least code changes:

OpenAI Responses API — direct migration, same vendor, feature parity plus new capabilities. Start here.

Best reasoning & long context:

Anthropic Claude API — Claude Fable 5.1 $10/$50 per MTok at the top of the lineup our record holds. Best for complex multi-step agent workflows that need strong reasoning.

Free tier available:

Google Gemini API — free tier with rate limits, multimodal input (images, audio, video). Best for prototyping and low-volume production.

Multi-model access:

GitHub Models is recorded as Retired — GitHub ended it, so it is no longer a way to reach several models for free. OpenRouter is the multi-model route still open in our index, recorded as Free.

Cheapest at scale:

Cohere — Command R7B $0.0375/$0.15 per MTok, the lowest paid rate our index carries for any provider on this page. That is 3× cheaper than gpt-6-luna at the same volume.

Fastest inference:

Groq or Cerebras — ultra-fast inference on open-source models. Best for latency-sensitive applications.

No vendor lock-in:

OpenRouter — unified API across 500+ models from 80+ providers. Switch models without code changes. Compare pricing in real-time.

Enterprise RAG & search:

Cohere — purpose-built for retrieval-augmented generation with native document parsing. Best for knowledge-heavy agent workflows.

Methodology

How we track this data: AgentDeals monitors free tier changes across 1,498 developer tools in 60 categories. Stability ratings are computed from our deal changes database — OpenAI is classified as volatile based on 19 tracked changes including free tier removal, limit reductions, and API deprecation.

Vendor data verification: Free tier details were read from vendor pricing pages on 2026-04-02. Last full verification: March 2026. Provider capabilities (tool use, code execution) were read from official API documentation on 2026-04-02.

For real-time data, use our stability dashboard, Atom feed, or MCP server. Full dataset available via REST API.

Related Guides