Drop files here, paste files, or add a URL. image/jpeg,image/png · 10 MiB
Drop files here, paste files, or add a URL. video/mp4,video/quicktime · 100 MiB
Example Output
This is sample data. Generate a new result to see real output.
Transparent pricing with no hidden fees. Pay as you go.
kling-3.0-motion-controlkling-3.0-motion-control| Model | Spec | PoYo price | Official price | You save |
|---|---|---|---|---|
| kling-3.0-motion-control | 720p | $0.045/sec 9 credits /sec | $0.126/sec Fal | 64% |
1080p | $0.075/sec 15 credits /sec | $0.168/sec Fal | 55% |
* Actual fees are based on the final output.
Complete guide to using Kling 3.0 Motion Control API for Controlled Motion Transfer
The three core ideas behind this model: fixed inputs, motion transfer, and controllable output quality.
01
Kling 3.0 Motion Control starts from one reference image, which anchors the identity, styling, and appearance of the character before motion transfer begins.
02
The motion source comes from one real reference video, which gives teams much clearer control over body rhythm, gesture, and action style than prompt-only motion descriptions.
03
The official positioning emphasizes smoother motion transfer and stronger character identity preservation, while PoYo keeps pricing direct through 720p and 1080p per-second modes.
Transfer clear body movement from reference footage into a new character-driven output.
Test motion ideas and shot direction before committing to heavier edit or VFX pipelines.
Use reference-driven generation when body rhythm, direction, or movement style matters.
Create controlled clips for campaign experiments, promos, and character-based marketing assets.
Step 1: Prepare one image and one video
Use exactly one character image and one reference video in the request payload.
Create API Key →
Step 2: Choose orientation and resolution
Set character_orientation to image or video, then choose 720p or 1080p based on quality and cost.
Add Credits →
Step 3: Submit and receive the result asynchronously
Send the task through the standard PoYo video submit flow and use polling or webhook for completion.
View API Doc →
720p: 9 credits per second
1080p: 15 credits per second
Credits are calculated from the uploaded reference video duration, which keeps the cost model direct and easy to explain to end users.
A fixed one-image plus one-video request format keeps integration predictable for product teams.
Teams can explain cost in a simple way: duration multiplied by a visible per-second rate.
Run motion-transfer jobs through the same polling and webhook flow used across PoYo video APIs.
PoYo keeps the request shape aligned with the rest of the video API family instead of exposing provider-specific complexity.
