Overview
When a model in the Krea API is deprecated, we communicate it through three channels so your integration can react automatically:- HTTP headers on every successful response from a deprecated endpoint:
Deprecation: trueSunset: Mon, 27 Apr 2026 00:00:00 GMT— when the endpoint will stop accepting requests (RFC 1123 date)Link: <https://docs.krea.ai/developers/deprecations#seedance-1-0-lite>; rel="deprecation"; type="text/html"— points to the entry on this page
- OpenAPI: the operation is marked
deprecated: trueand the description starts with a warning block. - MCP
list_models: deprecated models include adeprecationobject alongside their schema.
410 Gone with a structured body:
error field is stable and safe to switch on. The replacement and migration_url fields are present when a recommended replacement exists.
Sunset is enforced server-side at the moment the date passes. Your code should treat any
410 from a
model endpoint as terminal — retrying will not help.Currently Sunset
seedance-1-0-lite
Sunset on 2026-04-27. The provider has discontinued this model. Migration: switch your request path fromvideo/bytedance/seedance-1.0-lite to video/bytedance/seedance-1.0-pro-fast. The request and response shapes are otherwise compatible.
model argument:
sora-2
Sunset on 2026-04-27. The provider has discontinued this model. There is no drop-in replacement at this time. If you were usingvideo/openai/sora-2, evaluate other text-to-video models in our Video catalog — video/google/veo-3.1, video/runway/gen-4.5, and video/bytedance/seedance-2 are the closest options for high-quality short clips.
How to detect deprecation in your code
If you want to catch deprecations before sunset rather than reacting to410, watch for the Deprecation: true header on any response and surface it in your logs or alerts. A minimal example:
deprecation field on each model returned by list_models and get_model_schema.