Kling 4.0 API: what Sume lists and what to use today
Kling 4.0 API availability could not be confirmed from Kling's own pages on 2026-09-29. Here is what Sume's docs list today for video, and where Kling appears.
Whether a Kling 4.0 API exists yet could not be confirmed on 2026-09-29: Kling's release notes and announcement post did not load when this page was written, so this page states nothing about Kling 4.0's launch, specs or price. What can be checked is Sume's side. Sume's docs name no Kling 4.0 model. Kling shows up in Sume as kling-3 for video generation and as the kling-motion-control_create MCP tool.
If you need a video API today, the model ids the docs actually name are below. Check the live catalog before you build, because the docs describe limits that can change.
Which video models does Sume's documentation name?
The Video generation page states per-model limits. The catalog is read from GET /v1/videos/models, and from video-router_models over MCP.
| Model id | Length | Resolution named |
|---|---|---|
| seedance-2.5 | 4 to 30 seconds | 480p, 720p, 1080p |
| wan-3.0 | 2 to 30 seconds | not stated in that paragraph |
| minimax-h3 | 5 to 15 seconds | native 480p and 768p |
| gemini-omni-flash-1.1 | 3 to 10 seconds | 360p, 720p, 1080p, 4K |
Where does Kling appear in Sume?
Two places. Kling 3.0 text-to-video and image-to-video run as generate_video with the model kling-3, and Kling 3.0 motion control is the kling-motion-control_create MCP tool (kling/3.0/motion-control). The tool takes one still plus a driving video, and the output length follows the driving clip, so it is a motion-transfer tool and not a general Kling 4.0 endpoint. See Kling motion control API in Python for how that route is called.
Sume also has a post on Kling 3.0; it predates any Kling 4.0 news and says nothing about it.
What should I use while I wait for Kling 4.0?
Pick by the constraint you have, not by a model name. For a 30-second single clip, the docs list seedance-2.5 and wan-3.0. For 4K, they list gemini-omni-flash-1.1, capped at 10 seconds. If you do not care which family runs, send sume/auto; see sume/auto or a pinned model.
Every request needs a catalog id, so a new model id only works once it shows up in the catalog response. Fetch the catalog rather than assuming.
How do I check the live catalog before I build?
Call GET /v1/videos/models with your API key. Each model in the data array reports supported_durations, supported_resolutions, supported_aspect_ratios, generate_audio and pricing_skus. The docs say to use it to check which resolutions, aspect ratios and durations a model supports before you submit, because limits are not uniform across models.
That response, not a blog post, is the source of truth for whether a model id exists on your account. If your code hard-codes a model name, move the name into configuration so a catalog change is a one-line edit.
How will I know when Sume lists a Kling 4.0 model?
It will appear as an id in the catalog and on the video docs page. Until then, a request that names an id the catalog does not list is not a supported call. Kling's own announcement is the place to confirm its launch date and terms.
Sources
Related posts
More in Models
- Kling motion control camera movement and orientation
In Kling motion control, character orientation decides whether the camera follows the video or the image. What Kling says, and Sume's character_orientation.
- Kling motion control face consistency: element binding
Kling 3.0 Motion Control keeps a face steady by binding a facial element to the character image. How it works, and what Sume's endpoint takes instead.
- Kling motion control with multiple people in the video
Kling motion control animates one character. With two or more people in the reference, it uses the one with the largest share of the frame.
- Kling motion control not working: causes and fixes
A short, cut-off or wrong-person Kling motion control result usually traces to the reference video. Kling's causes, and the errors Sume's endpoint returns.
Written by Sume