No. The route is presented specifically as Kling 3.0 Turbo and exposes its own text-to-video and single-image image-to-video schema. Standard, Omni, motion-control, and editing endpoints are not grouped into it.
Generate short-form video with Kuaishou’s Kling 3.0 Turbo through APIXO. Turn a written scene or one source image into a 3–15-second clip, choose 720p or 1080p output, and integrate asynchronous generation into production workflows with polling or webhook delivery.
APIXO modes
Text to video · Image to video
Clip duration
3 · 5 · 10 · 15 seconds
Output resolution
720p · 1080p
APIXO pricing
$0.112-$0.14 / sec
Series launch
February 5, 2026
Loading workspace...
Describe the subject, action, camera path, environment, and visual treatment in one required prompt. This makes the model practical for planned shots rather than open-ended visual experimentation.
Animate exactly one publicly accessible source image while using the prompt to define movement and scene behavior. The source establishes the composition instead of acting as a general multi-reference set.
Select clips as long as 15 seconds, providing more room for a reveal, camera move, or compact narrative beat than a fixed five-second workflow.
Use APIXO’s 720p option for lower-cost iteration or select 1080p when the final asset needs additional visual detail.
Text-to-video requests can target landscape, portrait, or square compositions, covering common advertising, social, and presentation layouts.
Build a scene entirely from a required prompt. APIXO accepts 16:9, 9:16, and 1:1 aspect-ratio controls in this mode, alongside duration and resolution.
Supply exactly one public image URL and a required prompt describing the intended animation. APIXO does not forward the aspect-ratio field in this mode, so framing follows the source-image workflow.
The route deliberately presents a narrower interface than the broader Kling 3.0 product family.
3 · 5 · 10 · 15 sec
Selectable durations
720p · 1080p
Output resolutions
16:9 · 9:16 · 1:1
Text-to-video ratios
Exactly 1 URL
Image-to-video input
Typically 60–180 sec
Generation latency
Async polling · Callback
Delivery methods
Generate reveals, environmental product shots, and ecommerce campaign clips from a written brief or an approved product still. Use 720p for review rounds and 1080p for selected deliverables.
Start text-generated scenes in 16:9, 9:16, or 1:1 and test several durations without changing endpoints. This suits short paid-social variations and organic campaign assets.
Describe a shot’s action and camera path, then generate a compact visual reference for creative reviews, pitch decks, previs, or discussions with production teams.
Use one source image to establish the subject and composition, then prompt the intended movement. This is useful when visual approval begins with an existing key art asset.
A prompt is required for both APIXO workflows.
Image-to-video accepts exactly one public image URL; additional reference images and end-frame inputs are not exposed.
Aspect ratio is forwarded only for text-to-video requests.
APIXO exposes 3, 5, 10, and 15 seconds as discrete duration choices.
The public APIXO schema does not expose negative prompts, native-audio controls, silent-output controls, video inputs, motion control, or video editing.
Complex contact, rapid movement, anatomy, embedded text, and identity continuity should be reviewed before publishing. Longer or densely staged scenes may require separate shots.
No. The route is presented specifically as Kling 3.0 Turbo and exposes its own text-to-video and single-image image-to-video schema. Standard, Omni, motion-control, and editing endpoints are not grouped into it.
APIXO bills each generated output second. The public rate is $0.112 per second at 720p and $0.14 per second at 1080p. For example, five seconds at 720p costs $0.56.
No. APIXO requires exactly one source-image URL for this workflow and does not publicly expose end-frame or multi-reference fields on the route.
APIXO’s public Kling 3.0 Turbo schema does not expose audio input, native-audio generation, dialogue, narration, or sound-toggle parameters. Applications should treat the returned workflow as video generation without configurable audio behavior.
Use an asynchronous request and poll the model-specific status endpoint, or choose callback delivery and provide a public HTTPS callback URL.
Choose 720p for lower-cost drafts and iteration. Select 1080p when added detail justifies the higher per-second rate.
Discover more AI models for your next creative workflow