A reference dance clip plus a still character become a fully animated reel via the Kling 3.0 Motion Control API in three minutes — no rigging team needed.
The Kling 3.0 Motion Control API renders a video where the character from a reference image performs the actions from a reference video (Kuaishou Kling v3.0). The Kling 3.0 Motion Control API outputs 3–30-second clips with character_orientation control, optional prompt, and identity preservation — all through one REST endpoint, 5% below the official rate.
SampleRun the model to replace this previewKling 3.0 Motion Control API: Motion Transfer
Use the Kling 3.0 Motion Control API to animate a reference image with the actions of a reference video.
The Kling 3.0 Motion Control API takes a reference image (the character) and a reference video (the actions) and renders a clip of the image's character performing the video's actions (Kuaishou Kling v3.0). The Kling 3.0 Motion Control API accepts an optional prompt and a character_orientation toggle — 'image' (output ≤10s) keeps the image's framing; 'video' (output ≤30s) follows the driving video's framing.
Pricing on the Kling 3.0 Motion Control API is 5% below the official rate: $0.160 per second of output, $0.798 for the default 5-second clip, $2.9925 at 10s, $4.788 at 30s. One RouterBase key works alongside 200+ other models — no provider-specific SDK.
Six reasons teams ship on the Kling 3.0 Motion Control API
From identity-locked reference images to action-driven reference videos — what the Kling 3.0 Motion Control API gets right.
Reference image = identity
The Kling 3.0 Motion Control API anchors visual appearance, styling, and silhouette to your reference image — character identity stays consistent across the render.
Reference video = motion
Pass a 3-to-30-second driving clip and the Kling 3.0 Motion Control API transfers its actions onto the image character — no manual rigging or keyframing.
character_orientation control
Set character_orientation to 'image' (keep image framing, max 10s output) or 'video' (use driving-video framing, max 30s output). The Kling 3.0 Motion Control API caps duration per mode.
Optional prompt
Pass an optional text prompt (up to 2,500 chars) to refine style or context. The Kling 3.0 Motion Control API blends it with the reference inputs during the render.
3 to 30-second clips
Output duration scales with character_orientation: 3–10s when set to 'image', 3–30s when set to 'video'. The Kling 3.0 Motion Control API charges linearly per second.
5% off the official rate
Pay 5% less than the official rate when calling through the Kling 3.0 Motion Control API. $0.160/s — $0.798 at 5s, $2.9925 at 10s, $4.788 at 30s.

Get started with the Kling 3.0 Motion Control API in 3 steps
From sign-up to your first Kling 3.0 Motion Control API call in under 5 minutes.
Create a RouterBase API key
Sign up and generate sk-rb-… — one key works across the Kling 3.0 Motion Control API and 200+ other models on RouterBase.
POST image + driving clip
Send the reference image (JPG/PNG ≤10MB, ≥300px, aspect 2:5–5:2), the reference video (MP4/MOV ≤100MB, 3–30s), and character_orientation in JSON to the Kling 3.0 Motion Control API endpoint. The call is async — RouterBase polls upstream until the render completes.
Inspect the result
Each Kling 3.0 Motion Control API response includes generation metadata for auditing and a signed render URL ready to embed in your product.
Pay only for what you use
RouterBase passes through partner-tier pricing. Compared against the model's official published API rate.
| Resolution | RouterBase | Official | Save |
|---|---|---|---|
| image | $0.798 | −5% | |
| video 5s | $0.798 | −5% |
One run at the default settings (image) costs $0.798.With $1 you can run this model approximately 1 times.
What teams build with the Kling 3.0 Motion Control API
Real production loads running on the RouterBase model catalog across 200+ models.
We swapped three providers through RouterBase in one line of code when OpenAI had its outage. Our users never noticed.
The Kling 3.0 Motion Control API keeps character identity locked across a catalog of 200 talent portraits — the reference video transfers motion without bleeding face.
One Kling 3.0 Motion Control API call replaces a full motion-capture session for our localization reels.
Plugged the Kling 3.0 Motion Control API into my existing OpenAI SDK with one base URL swap — less work than writing this testimonial.
RouterBase puts 200+ models behind one key. Our research team stopped asking for new provider accounts.
character_orientation on the Kling 3.0 Motion Control API gives us 30-second outputs when we want video-led framing and tight 10-second loops when we want the image's framing — same endpoint, two creative modes.
We migrated 42 services to RouterBase over a weekend. The only PR comment we got was 'wait, that's all?'.
The Kling 3.0 Motion Control API is 5% below the official rate at every duration — at our scale that's six figures saved per quarter on character animation alone.
Frequently Asked Questions
Common questions about the Kling 3.0 Motion Control API.
The Kling 3.0 Motion Control API is RouterBase's pass-through to Kuaishou Kling v3.0 Motion Control. It takes a reference image (identity) and a reference video (actions) and outputs a video where the image character performs the video's actions — with optional prompt and character_orientation control.