seedanceapi
Wan 3.0 · Image to Video render example

Alibaba · Wan 3.0 · image to video

Wan 3.0 · Image to Video

Render Wan 3.0 through the same job workflow as Seedance — from $0.641 per render.

Model idalibaba/wan-3.0/image-to-videoShot spec480p · 720p · 1080p · 2–30sRatefrom $0.641

What it renders

Wan 3.0 Image to Video animates a first-frame image into a cinematic video, with optional last-frame guidance, flexible 2-30 second duration, aspect ratio control, optional audio, and… 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.641 and is locked in before the first frame is queued.

  1. Motion-first defaults

    Wan 3.0 · Image to Video 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 3.0 · Image to Video without leaving the video workspace.

  5. Wan 3.0 shots

    Wan 3.0 stays available for Wan 3.0 · Image to Video without leaving the video workspace.

  6. Video shots

    Video stays available for Wan 3.0 · Image to Video without leaving the video workspace.

From the shot board

Wan 3.0 · Image to Video example output.
Wan 3.0 · Image to Video 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 alibaba/wan-3.0/image-to-video 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":"alibaba/wan-3.0/image-to-video","aspect_ratio":"16:9","duration":5,"enable_audio":true,"enable_prompt_expansion":false,"prompt":"A slow dolly across a rain-lit neon street, shallow depth of field.","resolution":"720p","seed":1}'

Shot settings

aspect_ratiooptional
string · 16:9 / 9:16 / 1:1 / 4:3 / 3:4
durationoptional
integer · default 5
enable_audiooptional
boolean · default true
enable_prompt_expansionoptional
boolean · default false
imageneeded
string
last_imageoptional
string
promptoptional
string
resolutionoptional
string · 480p / 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 Wan 3.0 · Image to Video render?

Authenticate, check the live model list for alibaba/wan-3.0/image-to-video, 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 3.0 · Image to Video?

Wan 3.0 · Image to Video accepts aspect_ratio, duration, enable_audio, enable_prompt_expansion, image, last_image, prompt, resolution, seed. Unknown keys are rejected before the render is queued, so a typo never burns a job.

What does a Wan 3.0 · Image to Video render cost?

Pricing is per render and starts at $0.641. 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 3.0 · Image to Video?

Yes — Wan 3.0 · Image to Video 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 3.0 · Image to Video 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