Deprecation and Sunset headers before 410 Gone: Sume's old names
Krea's retired Kling endpoints send Deprecation and Sunset headers, then 410 Gone. Here is how to detect that in code and which Sume aliases still work.

Krea's changelog says its retired video endpoints keep working until September 15, 2026 and return Deprecation and Sunset headers, then return 410 Gone. Log those two headers and treat a 410 as final. Sume's docs list deprecations in tables of aliases and ignored fields; the pages cited here do not describe those two headers, so do not rely on them from Sume.
Krea facts are from its changelog; Sume facts are from the models, image, video and video inspect docs, read 2026-10-01.
What does Krea's retirement look like on the wire?
Krea's entry describes a three-stage signal. Until September 15 the retired endpoints keep working and add Deprecation and Sunset headers. After that date they return 410 Gone. A client that reads the headers is warned before the break, while one that only checks status codes finds out on the last day.
async function main() {
const res = await fetch("https://api.sume.com/v1/images/models", {
headers: { Authorization: "Bearer " + process.env.SUME_API_KEY },
});
const deprecation = res.headers.get("deprecation");
const sunset = res.headers.get("sunset");
if (deprecation || sunset) {
console.warn("deprecated endpoint", { deprecation, sunset });
}
if (res.status === 410) throw new Error("endpoint retired: migrate");
console.log(res.status);
}
main();Which old Sume names still work?
Sume documents its retiring names in place. These are the ones in the pages cited, and each says how it behaves today.
| Surface | Behavior in the docs |
|---|---|
input_urls, n, format on image jobs | Deprecated aliases still accepted; prefer the non-deprecated names |
POST /v1/avatar-1.0/image-to-video and its runs alias | Listed as deprecated or retiring compatibility aliases, still supported; the correct call is POST /v1/veed/fabric-1.0 |
routing_preset on video | Deprecated and ignored; all values use Auto |
Legacy POST /v1/video-analyses | Dest answers 410 video_analysis_retired |
Does Sume return a 410 for old names?
Only where the docs say so. The video-inspect page documents a 410 for the legacy video-analyses route, while the field aliases above are accepted rather than rejected. For moving off a retired video model itself, see Kling 2.1 API sunset.
What should my client do?
Log Deprecation and Sunset when present, alert on any 410, and keep a short list of the deprecated field names in your own code. Re-read the alias tables when you upgrade, because the docs mark them as retiring.
Sources
Related posts
More in Developers
- Lambda durable functions with Pydantic AI: Sume submit as a step
AWS says each model and tool call becomes a durable step that is not repeated after an interruption. Here is how to shape a Sume submit as that step.
- LangChain invalid tool calls: what Sume returns on a bad call
After LangChain 1.4.3 repairs an invalid tool call, Sume may still return an isError result, such as tool_not_found with a hint. Keep the same idempotency_key.
- LLaDA-Image is open weights: Sume's Image API is a hosted catalog
LLaDA-Image (6B, Apache 2.0, released 2026-09-04) is a download, not an API id. Sume does not list it; use a catalog model with a text-in-image prompt.
- LMNT has shut down: what to know moving to Sume TTS
LMNT's site says it has shut down. If you move to Sume TTS 1.0, voice ids do not carry over, language must be set for non-English text, and text caps at 20000.
Written by Sume