Kling 4.0 API price: not public yet; what you can call today on Sume
No public Kling 4.0 API price was found on 2026-10-09. Sume lists a kling-3 video id and Kling 3.0 Motion Control at $0.1575 per second, 1 to 30 seconds.

There is no public Kling 4.0 API price to quote on 2026-10-09: the Kling developer pricing page returned no 4.0 rate when read. What Sume lists today is Kling 3: a kling-3 model id in its Video Router catalog and Kling 3.0 Motion Control as a separate model at $0.1575 per output second.
So the practical answer for a buyer is to build against Kling 3 on Sume now, keep the model id in config, and switch when a 4.0 price and API are public and Sume lists them.
What Sume lists
Sume's public catalog, read 2026-10-09, names these Kling rows.
| Catalog id | What it is | Price | Cost of 10 s | Cost of 30 s |
|---|---|---|---|---|
| kling-3 | Video Router model id | read live from GET /v1/videos/models | n/a | n/a |
| kling-motion-control | Kling 3.0 Motion Control | $0.1575 per output second, 1 to 30 s | $1.575 | $4.725 |
How the reservation works
Motion Control reserves a price at submit time. The catalog shows a minimum reservation of 16 cents and a maximum of 473 cents. Those are the 1-second and 30-second cases rounded up to a whole cent: $0.1575 rounds up to $0.16, and 30 x $0.1575 = $4.725 rounds up to $4.73. Failed jobs are refunded before capture.
Planning for a model swap
Treat the model id as data, not code. The Video Router catalog is the place to see which ids exist, and GET /v1/video-router/models/{model_id} returns one model's envelope. When a new Kling id appears you change one string and rerun your prompt set.
Until then, do not budget from rumors of a 4.0 price. If you need a number for a plan, use the Kling 3 figures above and mark the line as provisional.
Checks before you rely on a number
The following figures use the same list prices as the tables above.
- A price quoted in a forum or news item is not a price list. Check the vendor's own pricing page and note the read date.
- Sume's Motion Control rate of $0.1575 per second is for Kling 3.0 and applies to 1 to 30 seconds of output.
- A 30-second Motion Control run reserves 473 cents and a 1-second run 16 cents, per the catalog.
- Keep your pipeline's model id in configuration so changing to a Kling 4 id later is one edit.
Limits of this comparison
If you are comparing vendors this week, put Kling 4 on a watch list with a date, not on a cost sheet. In the meantime the Kling 3 id on Sume takes the same request shape as every other Video Router model, so a prompt set you build now will run unchanged when a Kling 4 id is added. The one thing to avoid is hard-coding a price into your product copy before the vendor publishes it.
Sources
Related posts
More in Models
- H3 Max 4K request fails: H3 takes 2K and 4K as 768p upscales
minimax-h3-max accepts 480p, 768p or 1080p only. A 4K request belongs on minimax-h3, where it is a 768p upscale at $0.20 a second, $1.60 for 8 s on Sume.
- Mistral Large 4 on a 12-turn storyboard: tokens are 4% of the bill
Mistral Large 4 lists $1.36 input and $4.18 output per million tokens. A 12-turn run that makes six Wan 3.0 clips spends 4.3% of its total on tokens.
- Nano Banana 2.1 at 8:1 and 4K: 12288x1536, 18.87 megapixels
Google's size table puts Nano Banana 2.1 8:1 at 4K at 12288x1536, about 18.87 MP, larger than a 4096x4096 square. Sume lists 8:1 and 4K at $0.20 flat.
- nano-banana-2 still works but runs as 2.1: check the stored job id
Sume retired Nano Banana 2: google/nano-banana-2 runs as Nano Banana 2.1 and the job stores the 2.1 id. A Python check and what you pay.
Written by Sume