seedanceapi
Wan 2.1 14b Vace render example

OpenWeights · Wan 2.1 14b Vace · image to video

Wan 2.1 14b Vace

Render Wan 2.1 14b Vace through the same job workflow as Seedance — from $0.405 per render.

Model idopen/wan-2.1-14b-vaceShot spec832*480 · 480*832 · 1280*720 · 720*1280 · 5–10sRatefrom $0.405

What it renders

WAN 2.1 VACE is an all-in-one video model supporting Reference-to-Video (Image-to-Video), V2V, Masked V2V and Move/Swap/Animate capabilities. 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.405 and is locked in before the first frame is queued.

  1. Motion-first defaults

    Wan 2.1 14b Vace 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 Wan 2.1 14b Vace without leaving the video workspace.

  5. Wan 2.1 14b Vace shots

    Wan 2.1 14b Vace stays available for Wan 2.1 14b Vace without leaving the video workspace.

  6. Video shots

    Video stays available for Wan 2.1 14b Vace without leaving the video workspace.

From the shot board

Wan 2.1 14b Vace example output.
Wan 2.1 14b Vace 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 open/wan-2.1-14b-vace 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":"open/wan-2.1-14b-vace","context_scale":1,"duration":5,"flow_shift":16,"guidance_scale":5,"num_inference_steps":30,"prompt":"A slow dolly across a rain-lit neon street, shallow depth of field.","seed":1,"size":"832*480","task":"depth"}'

Shot settings

context_scaleoptional
number · default 1
durationoptional
integer · default 5
first_imageoptional
string
flow_shiftoptional
number · default 16
guidance_scaleoptional
number · default 5
imagesoptional
array
last_imageoptional
string
mask_imageoptional
string
mask_videooptional
string
negative_promptoptional
string
num_inference_stepsoptional
integer · default 30
promptoptional
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 Wan 2.1 14b Vace render?

Authenticate, check the live model list for open/wan-2.1-14b-vace, 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 Wan 2.1 14b Vace?

Wan 2.1 14b Vace accepts context_scale, duration, first_image, flow_shift, guidance_scale, images, last_image, mask_image, mask_video, negative_prompt. Unknown keys are rejected before the render is queued, so a typo never burns a job.

What does a Wan 2.1 14b Vace render cost?

Pricing is per render and starts at $0.405. 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 Wan 2.1 14b Vace?

Yes — Wan 2.1 14b Vace 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 Wan 2.1 14b Vace 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