seedanceapi
Kling Video O3 Std · Video Edit render example

Kling AI · Kling Video O3 Std · video to video

Kling Video O3 Std · Video Edit

Render Kling Video O3 Std through the same job workflow as Seedance — from $0.851 per render.

Model idkwaivgi/kling-video-o3-std/video-editShot specVideo to VideoRatefrom $0.851

What it renders

Kling Omni Video O3 Video-Edit (Standard) enables natural-language video edits: remove or replace objects, swap backgrounds, restyle scenes, change weather/lighting, and apply localized… Hand over the model id and your shot settings, keep the job id, and collect the finished clip once the job lands. Pricing is per completed render from $0.851 and is locked in before the first frame is queued.

  1. Motion-first defaults

    Kling Video O3 Std · Video Edit opens on workable shot framing before you tune anything.

  2. Async by design

    Renders run as background jobs; poll at your own pace instead of holding a connection open.

  3. Clip-ready output

    Results arrive as a downloadable asset from private storage with a short-lived link.

  4. Video to Video shots

    Video to Video stays available for Kling Video O3 Std · Video Edit without leaving the video workspace.

  5. Kling Video O3 Std shots

    Kling Video O3 Std stays available for Kling Video O3 Std · Video Edit without leaving the video workspace.

  6. Video shots

    Video stays available for Kling Video O3 Std · Video Edit without leaving the video workspace.

From the shot board

Kling Video O3 Std · Video Edit example output.
Kling Video O3 Std · Video Edit output
Kling Video O3 Std · Video Edit example reference.
Kling Video O3 Std · Video Edit reference

Wire the render pipeline

  1. Grab a key

    Sign in, create a server-side key and add a little balance.

  2. Confirm the endpoint

    GET /v1/models lists kwaivgi/kling-video-o3-std/video-edit with its shot limits and current rate.

  3. Queue the render

    POST /v1/jobs with the model id, your shot settings and a unique Idempotency-Key.

  4. Collect the clip

    Poll GET /v1/jobs/{id} until it lands, then fetch GET /v1/jobs/{id}/content.

Queue the render

# Seedance API — queue one render
curl https://seedanceapi.pro/v1/jobs \
  -H "Authorization: Bearer $SEEDANCE_API_KEY" \
  -H "Idempotency-Key: $REQUEST_ID" \
  -H "Content-Type: application/json" \
  -d '{"model":"kwaivgi/kling-video-o3-std/video-edit","keep_original_sound":true,"prompt":"A slow dolly across a rain-lit neon street, shallow depth of field.","shot_type":"customize"}'

Shot settings

imagesoptional
array
keep_original_soundoptional
boolean · default true
promptoptional
string
shot_typeoptional
string · customize / intelligence
videoneeded
string

Try a render from here

This queues a real job on this site's /v1/jobs using your signed-in balance, or an API key if you are not signed in. A pasted key lives only in this tab; the render is billed at the quoted USD rate.

Or sign in to use your account balance.

Before you wire it in

How do I start a Kling Video O3 Std · Video Edit render?

Authenticate, check the live model list for kwaivgi/kling-video-o3-std/video-edit, then POST the model id and shot settings to /v1/jobs with an Idempotency-Key. Poll the job id until it settles, then download the clip.

What can I control on Kling Video O3 Std · Video Edit?

Kling Video O3 Std · Video Edit accepts images, keep_original_sound, prompt, shot_type, video. Unknown keys are rejected before the render is queued, so a typo never burns a job.

What does a Kling Video O3 Std · Video Edit render cost?

Pricing is per render and starts at $0.851. The exact figure for your settings is returned by the model list and reserved before the job is accepted.

Is the same Seedance key valid for Kling Video O3 Std · Video Edit?

Yes — Kling Video O3 Std · Video Edit runs on the same account, key and wallet as Seedance. Each endpoint is enabled individually, so verify the route before you depend on it.

Why does my Kling Video O3 Std · Video Edit job show as queued?

Video rendering is asynchronous: queued and running are normal. Keep polling until the job succeeds, fails or asks for review, and never resubmit the same Idempotency-Key expecting a second render.

More endpoints like this