Developer pricing desk · checked 29 August 2026
Kling AI · Video 3.0 series
Price theusable shot.
Kling's list price is charged against submitted output. Your production price emerges after retries, discarded motion, continuity repair, audio work and the seconds that actually survive the edit.
Official API list-price matrix
The configuration
sets the rate.
Kling publishes one video API unit at a $0.14 list price. The table converts the listed unit charges into dollars per submitted second.
| Model route | Configuration | 720p | 1080p | 4K |
|---|---|---|---|---|
| Kling 3.0 Turbo | Native audio | $0.112/s | $0.140/s | — |
| Kling 3.0 | No native audio | $0.084/s | $0.112/s | $0.420/s |
| Kling 3.0 | Native audio · no voice control | $0.126/s | $0.168/s | $0.420/s |
| Kling 3.0 Omni | No video input · no native audio | $0.084/s | $0.112/s | $0.420/s |
| Kling 3.0 Omni | No video input · native audio | $0.112/s | $0.140/s | $0.420/s |
| Kling 3.0 Omni | Video input · no native audio | $0.126/s | $0.168/s | $0.420/s |
$0.56
5 submitted seconds
Turbo · 720p · native audio
$0.70
5 submitted seconds
Turbo · 1080p · native audio
$0.56
5 submitted seconds
3.0 · 1080p · no native audio
$0.84
5 submitted seconds
3.0 · 1080p · native audio
$2.10
5 submitted seconds
3.0 · 4K · five seconds
Arithmetic examples from the checked list rates. They do not include retries, account discounts, packages or non-generation production costs.
Retry-adjusted cost
Model the edit,
not the invoice.
Select the exact route and enter every paid submission. “Usable seconds” means the footage that survives continuity review and enters the final sequence.
Interactive Kling API cost planner
Official submitted-second rate × your attempts ÷ usable finished seconds.
Cost per usable second
$0.35
At this submitted-output yield, one usable finished minute projects to $21.00.
- Submitted cost
- $4.20
- Generated time
- 30s
- Usable time yield
- 40%
- Unit rate
- $0.140
This excludes subscriptions, storage, upscaling, repair, editing, voice talent and other production costs.
Rates are list-price API baselines checked 29 August 2026. Default attempt and usable-second values demonstrate the interface; they are not ReelPulse benchmark results.
Route selector
Start with the bottleneck.
Do not select a model only because its per-second number is lower. Match the route to the production problem you cannot cheaply repair later.
Native-audio pilot
Kling 3.0 Turbo
Start here when the production needs the published Turbo route with synchronized sound at 720p or 1080p. The checked table does not list a 4K Turbo rate.
Resolution + multi-shot
Kling 3.0
Start here when you need a 3.0 route with 4K pricing, multi-shot control or a deliberate choice between silent and native-audio output.
Input-led control
Kling 3.0 Omni
Start here when the difficult part is multimodal or video input. Price the exact input/audio combination; Omni is not one universal unit rate.
Production rule
Keep one recurring-character pipeline for dialogue coverage. Introduce a second route only when it solves a named shot problem worth the continuity, color-matching and accounting overhead.
API production path
A task is not an asset.
The official Kling 3.0 documentation uses an asynchronous task flow. Preserve task IDs, normalize status, record charges and copy completed outputs into your own controlled storage.
POST /text-to-video/kling-3.0
{
"prompt": "locked scene prompt",
"settings": {
"resolution": "1080p",
"aspect_ratio": "9:16",
"duration": 5,
"audio": "native",
"multi_shot": true
},
"options": {
"callback_url": "https://example.com/callback",
"external_task_id": "scene-07-shot-03"
}
}Illustrative request using fields and enums documented on the checked Kling 3.0 route. Verify authentication, endpoint host and the current schema before deployment.
- 01
Choose one route and output contract
Lock the Kling model, input type, audio mode, resolution, aspect ratio and duration before the production test.
- 02
Submit the generation task
Send the prompt and settings to the documented text-to-video or image-to-video route and preserve your external task ID.
- 03
Handle asynchronous completion
Use the documented callback or task-query flow, normalize provider states and log failed as well as completed submissions.
- 04
Copy outputs into controlled storage
Do not treat provider result URLs as the permanent production archive; retain outputs and associated rights records in your own system.
- 05
Score the final edit
Count only usable finished seconds, then combine generation charges with repair, audio, editing and delivery costs.
Locked vertical-drama pilot
Test one scene
three ways.
Copy the same prompts for every model route. Keep character references, settings and review rubric fixed; record every submission.
Shot A · dialogue two-shot
Identity, lip sync and eyeline continuity
Vertical 9:16 medium two-shot inside a late-night convenience store. Mara, a woman in a charcoal coat with a small silver crescent pin, confronts Elias, a tired man in a pale blue work shirt. Keep both faces visible and preserve their exact wardrobe and relative positions. Mara says, ‘You knew the train was empty.’ Elias answers, ‘I knew who was waiting.’ Natural fluorescent ambience, restrained performances, no camera cut, subtle push-in, realistic synchronized dialogue and room tone.
Shot B · reaction close-up
Face, wardrobe and emotional continuity
Vertical 9:16 close-up of Mara in the same late-night convenience store, wearing the same charcoal coat and silver crescent pin. She processes Elias’s answer without speaking: suspicion shifts into recognition, then controlled fear. Match the fluorescent direction and background geography from the prior two-shot. Locked camera, shallow depth of field, realistic micro-expression, no new props, no text, continuous room tone.
Shot C · moving reveal
Motion, geography and prop continuity
Vertical 9:16 moving reveal in the same convenience store. Begin behind Elias’s right shoulder, track slowly past him and reveal a red suitcase beneath the counter behind Mara. Preserve both characters’ faces, wardrobe, store geography and fluorescent lighting. Elias remains foreground right; Mara remains behind the counter. The suitcase is the only new reveal. Controlled dolly movement, realistic reflections, no dialogue, tense refrigerator hum, no cuts.
These are controlled test inputs, not claims about output quality. Public sample clips and retry counts remain unpublished until a legally obtained recorded run is complete.
Official legacy retirement notice
SEP 15
2026
Do not start new work on retiring video models.
Kling's update notice says the following legacy video APIs retire on September 15, 2026: Kling 1.0, 1.5, 1.6, 2.0 Master, 2.1 and 2.1 Master. Audit pinned IDs and production queues before that date.
Kling pricing FAQ
Before you budget.
How much does the Kling AI API cost?
The official developer price table checked on August 29, 2026 states that one video API unit has a $0.14 list price. Actual per-second rates vary by model, resolution, native audio, voice control and input type. For example, Kling 3.0 Turbo with native audio is listed at $0.112 per second for 720p and $0.14 per second for 1080p.
How much is a five-second Kling 3.0 Turbo video?
At the published API list rate, five submitted seconds of Kling 3.0 Turbo with native audio cost $0.56 at 720p or $0.70 at 1080p. This is before retries, rejected clips, editing, storage or other production work.
Does Kling 3.0 support native audio?
Yes. Kling's official Video 3.0 guide and developer price table list native-audio routes. Pricing varies by exact model, resolution, voice-control choice and whether video input is used.
Does the Kling API support vertical 9:16 video?
The official Kling 3.0 text-to-video API documentation lists 9:16 as an aspect-ratio enum alongside 16:9 and 1:1. Verify the exact model route and current request schema before production deployment.
How long can a Kling 3.0 API video be?
The checked Kling 3.0 text-to-video documentation lists durations from 3 through 15 seconds, and the official model guide describes output up to 15 seconds. Duration support can differ on another model or product route.
Is the cheapest Kling route best for a short drama?
Not necessarily. A silent route can create separate dialogue, synchronization and sound-design work. Compare total cost per usable finished second after retries and repair, not only the submitted-output rate.
Are ReelPulse's Kling sample success rates available?
Not yet. This guide publishes official capabilities and pricing plus a controlled test protocol. ReelPulse will add sample clips, attempt counts and acceptance data only after legally obtained, recorded locked-prompt runs are available.
Continue the AI video production desk
Runway pricing & API
Separate app and API credits and price the Gen-4.5 workprint.
Open guide →
Luma pricing & API
Compare Ray 3.2 per-video rates and its frame-led direction surface.
Open guide →
Google Flow & Veo
Compare Flow credits, Veo API rates and native-audio output.
Open guide →
Higgsfield pricing
Compare a multi-model subscription and credit value per usable second.
Open guide →