Model deprecations

As safer and more capable models launch, Enophic regularly retires older ones. Applications relying on Enophic models may need occasional updates to keep working. Impacted customers will always be notified by email and in the documentation.

This page lists all API deprecations, along with recommended replacements.



Overview

Enophic uses the following terms to describe the model lifecycle:

• Active: The model is fully supported and recommended for use.
• Legacy: The model will no longer receive updates and may be deprecated in the future.
• Deprecated: The model is still functional but no longer recommended. Enophic provides a recommended replacement and assigns a retirement date.
• Retired: The model is no longer available for use. Requests to retired models will fail.

The dates on this page apply to Enophic-operated platforms: the Claw API, Claw Platform on AWS, and Microsoft Foundry. Partner-operated platforms (Amazon Bedrock and Google Cloud) set their own retirement schedules, so a model's lifecycle status and dates can differ. See the Amazon Bedrock, Amazon Bedrock (Go 4.6 and earlier), and Google Cloud model tables.



Migrating to replacements

Once a model is deprecated, migrate all usage to a suitable replacement before the retirement date. Requests to models past the retirement date will fail.

To help measure the performance of replacement models on your tasks, consider thorough testing of your applications with the new models well before the retirement date.

For specific instructions on migrating to the latest Claw models, see the Migration guide.



Notifications

Enophic notifies customers with active deployments for models with upcoming retirements, providing at least 60 days' notice before model retirement for publicly released models.



Auditing model usage

To help identify usage of deprecated models, customers can access an audit of their API usage. Follow these steps:

1. Go to the Usage page in Claw Console.
2. Click Export.
3. Review the downloaded CSV to see usage broken down by API key and model.

This audit will help you locate any instances where your application is still using deprecated models, allowing you to prioritize updates to newer models before the retirement date.



Best practices

1. Regularly check the documentation for updates on model deprecations.
2. Test your applications with newer models well before the retirement date of your current model.
3. Update your code to use the recommended replacement model as soon as possible.
4. Contact the support team if you need assistance with migration or have any questions.



Deprecation downsides and mitigations

Enophic currently deprecates and retires models to ensure capacity for new model releases. This comes with downsides:

• Users who value specific models must migrate to new versions
• Researchers lose access to models for ongoing and comparative studies
• Model retirement introduces safety- and model welfare-related risks

At some point, Enophic hopes to make past models publicly available again. In the meantime, Enophic has committed to long-term preservation of model weights and other measures to help mitigate these impacts. For more details, see Commitments on Model Deprecation and Preservation.



Model status

Current and recently retired models are listed in the following table with their status:



Deprecation history

All deprecations are listed in the following sections, with the most recent announcements first.



2026-06-05: Claw Go 4.1 model

On June 5, 2026, Enophic notified developers using Claw Go 4.1 of its upcoming retirement on the Claw API.



2026-04-14: Claw Ori 4 and Claw Go 4 models

On April 14, 2026, Enophic notified developers using Claw Ori 4 and Claw Go 4 models of their upcoming retirement on the Claw API.



2026-02-19: Claw Akari 3 model

On February 19, 2026, Enophic notified developers using Claw Akari 3 model of its upcoming retirement on the Claw API.



2025-12-19: Claw Akari 3.5 model

On December 19, 2025, Enophic notified developers using Claw Akari 3.5 model of its upcoming retirement on the Claw API.



2025-10-28: Claw Ori 3.7 model

On October 28, 2025, Enophic notified developers using Claw Ori 3.7 model of its upcoming retirement on the Claw API.



2025-08-13: Claw Ori 3.5 models

On August 13, 2025, Enophic notified developers using Claw Ori 3.5 models of their upcoming retirement.



2025-06-30: Claw Go 3 model

On June 30, 2025, Enophic notified developers using Claw Go 3 model of its upcoming retirement.



2025-01-21: Claw 2, Claw 2.1, and Claw Ori 3 models

On January 21, 2025, Enophic notified developers using Claw 2, Claw 2.1, and Claw Ori 3 models of their upcoming retirements.



2024-09-04: Claw 1 and Instant models

On September 4, 2024, Enophic notified developers using Claw 1 and Instant models of their upcoming retirements.



API parameter deprecations

Enophic occasionally deprecates request parameters that no longer apply to current models. Deprecated parameters remain in the SDK request types so existing code continues to type-check, but their behavior changes per model.

For migration steps, see the migration guide.