Deprecations | Cohere

> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.cohere.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cohere.com/_mcp/server. Deprecations > Learn about Cohere's deprecation policies and recommended replacements Find information around deprecated endpoints and models with their recommended replacements. Overview As Cohere launches safer and more capable models, we will regularly retire old models. Applications relying on Cohere's models may need occasional updates to keep working. Impacted customers will always be notified via email and in our documentation along with blog posts. This page lists all API deprecations, along with recommended replacements. Cohere uses the following terms to describe the lifecycle of our models: Active: The model and endpoint are fully supported and recommended for use. Legacy: The model and endpoints will no longer receive updates and may be deprecated in the future. Deprecated: The model and endpoints are no longer available to new customers but remain available to existing users until retirement. (An existing user is defined as anyone who has used the model or endpoint within 90 days of the deprecation announcement.) A shutdown date will be assigned at that time. Shutdown: The model and endpoint are no longer available for users. Requests to shutdown models and endpoints will fail. Migrating to replacements Once a model is deprecated, it is imperative to migrate all usage to a suitable replacement before the shutdown date. Requests to models and endpoints past the shutdown date will fail. To ensure a smooth transition, we recommend thorough testing of your applications with the new models well before the shutdown date. If your team requires assistance, do not hesitate to reach out to support@cohere.ai(mailto:support@cohere.ai). Deprecation History All de