Launch-day checklist before moving off kling-3 on Sume

Before you move any production job off kling-3, confirm the new id is in GET /v1/videos/models; as of 2026-10-13 Sume lists kling-3 and no newer Kling row. If your replacement is a different family, five limits can break a working request: resolution, length, ratio, references and audio.

The five checks

Run them in this order, since each one is cheap to test.

• Listed: the new id appears in the catalog; otherwise submit returns 404 model_not_found.
• Resolution: kling-3 always renders 1080p, and still accepts 720p from older callers. Other rows bill by tier.
• Length: kling-3 is 4-15 s. Omni stops at 10 s.
• Ratio: kling-3 lists 16:9, 9:16 and 1:1. Omni lists only 16:9 and 9:16.
• Inputs: kling-3 takes no reference images or clips. Moving to a reference row lets you add them but changes the request shape.

Roll out safely

Send 5% of traffic to the new id first, record the model id in your job log, and keep kling-3 as the fallback until clip lengths and ratios in real requests have all passed. Because kling-3 is billed at a 1080p price for every clip, a lower-tier row can cost less; compare against the list in the docs, not against memory.