Developers building on Runway’s API can now call three families of Kling video models. Runway’s API changelog, in an entry dated 13 October 2026, puts it simply: “Kling is now available on Runway Dev.” The new models are Kling 2.5 Turbo Pro, Kling 3.0 (in Standard, Pro and 4K versions) and Kling O3 (also in Standard, Pro and 4K).
This is a catalogue addition. Runway Dev, Runway’s platform for developers, has been running since July; the change is that apps already wired to it can now pick Kling as well as Runway’s own models and the other partner models it hosts.
What developers get, in plain English
Runway Dev lets a developer send a request from their own software and get a generated video back, paying in Runway credits. With this update, they can choose a Kling model for that job using the same text-to-video, image-to-video and video-to-video endpoints they already use.
- Kling 2.5 Turbo Pro makes clips from a written prompt or from a starting picture, with the option of a final picture to end on. Clips are 5 or 10 seconds long, and 5 is the default.
- Kling 3.0 makes clips from a prompt or from first and last frames, anywhere from 3 to 15 seconds. It can add audio, which is switched on unless you turn it off. It also supports “multishot” prompts: you can describe up to six separate segments in one request, as long as the whole video is 3 to 15 seconds, so one call can produce a short sequence of shots instead of a single shot.
- Kling O3 uses the same sizes and lengths as Kling 3.0, but adds two things. You can give it up to seven reference images when starting from pictures (start and end frames count towards the seven), and you can hand it an existing clip of up to 10 seconds to edit.
Each family comes in tiers that mainly change the output size. According to the changelog, Standard text-to-video produces 1280×720, 720×1280 or 960×960; Pro produces 1920×1080, 1080×1920 or 1440×1440; and 4K produces 3840×2160, 2160×3840 or 2880×2880. Kling 2.5 Turbo Pro’s text-to-video sizes are 1920×1080 (the default), 1440×1440 or 1080×1920. For image-to-video, the output follows the shape of the picture you supply.
There is also a dial called cfgScale, which runs from 0 to 1 with a default of 0.5, on Kling 2.5 Turbo Pro and Kling 3.0.
What it costs
Runway bills in credits per second of video. These are Runway’s figures, as listed in the changelog:
| Model | Length | Credits per second |
|---|---|---|
| Kling 2.5 Turbo Pro | 5 or 10 seconds | 12 |
| Kling 3.0 Standard | 3–15 seconds | 9 without audio, 13 with audio |
| Kling 3.0 Pro | 3–15 seconds | 12 without audio, 17 with audio |
| Kling 3.0 4K | 3–15 seconds | 43 with or without audio |
| Kling O3 Standard | 3–15 seconds | 13 |
| Kling O3 Pro | 3–15 seconds | 17 |
| Kling O3 4K | 3–15 seconds | 43 |
Two details matter for budgeting. Runway says Kling O3 is charged at those rates “including when audio is false“, so turning off sound on O3 does not make it cheaper, unlike on Kling 3.0 Standard and Pro. And for Kling O3 video editing, Runway says it is “billed per second of the input video”, meaning the length of the clip you send in sets the bill.
As a rough example using Runway’s rates, a 10-second Kling 3.0 Pro clip with audio would cost 170 credits, while the same clip without audio would cost 120. Runway’s changelog entry does not give a dollar value per credit.
Why it matters
For developers, the main gain is choice without extra plumbing. Instead of signing up with another provider and writing new code, a team already using Runway’s API can try Kling’s models through the same endpoints and the same credit balance, and compare them with the other video models on the platform. The clear per-second pricing also makes it easier to estimate what a feature will cost before shipping it.
Related stories
- AI Creative Tools: Cheaper Video, Brand Kits and Claude Motion
- Runway Multi-Shot: AI Video Just Learned to Tell Stories
- Grok Imagine: While OpenAI Retreats, xAI Bets on the Everyday Creator
Sources
- Runway, “API Changelog: Kling on Runway Dev”, 13 October 2026. https://docs.dev.runwayml.com/api-details/api_changelog/
