seedanceapi
Start End to Video Q2 Pro render example

Vidu · Start End To Video Q2 Pro · image to video

Start End to Video Q2 Pro

Render Start End To Video Q2 Pro through the same job workflow as Seedance — from $0.203 per render.

Model idvidu/start-end-to-video-q2-proShot spec540p · 720p · 1080p · 1–8sRatefrom $0.203

What it renders

Vidu Q2 Pro Start-End to Video produces smooth image-to-video transitions between start and end images for seamless morphs. 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.203 and is locked in before the first frame is queued.

  1. Motion-first defaults

    Start End to Video Q2 Pro 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. Image to Video shots

    Image to Video stays available for Start End to Video Q2 Pro without leaving the video workspace.

  5. Start End To Video Q2 Pro shots

    Start End To Video Q2 Pro stays available for Start End to Video Q2 Pro without leaving the video workspace.

  6. Video shots

    Video stays available for Start End to Video Q2 Pro without leaving the video workspace.

From the shot board

Start End to Video Q2 Pro example output.
Start End to Video Q2 Pro output

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 vidu/start-end-to-video-q2-pro 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":"vidu/start-end-to-video-q2-pro","bgm":true,"duration":5,"movement_amplitude":"auto","prompt":"A slow dolly across a rain-lit neon street, shallow depth of field.","resolution":"720p","seed":1}'

Shot settings

bgmoptional
boolean · default true
durationoptional
integer · default 5
imageneeded
string
last_imageneeded
string
movement_amplitudeoptional
string · auto / small / medium / large
promptoptional
string
resolutionoptional
string · 540p / 720p / 1080p
seedoptional
integer

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 Start End to Video Q2 Pro render?

Authenticate, check the live model list for vidu/start-end-to-video-q2-pro, 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 Start End to Video Q2 Pro?

Start End to Video Q2 Pro accepts bgm, duration, image, last_image, movement_amplitude, prompt, resolution, seed. Unknown keys are rejected before the render is queued, so a typo never burns a job.

What does a Start End to Video Q2 Pro render cost?

Pricing is per render and starts at $0.203. 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 Start End to Video Q2 Pro?

Yes — Start End to Video Q2 Pro 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 Start End to Video Q2 Pro 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