seedanceapi
Pixverse V5.5 Transition render example

PixVerse · Pixverse V5.5 Transition · image to video

Pixverse V5.5 Transition

Render Pixverse V5.5 Transition through the same job workflow as Seedance — from $0.608 per render.

Model idpixverse/pixverse-v5.5-transitionShot spec360p · 540p · 720p · 1080p · 5sRatefrom $0.608

What it renders

Create smooth morph transitions between two images into 5s, 8s or 10s videos at 360p, 540p, 720p, or 1080p—perfect for logo reveals, before-and-after shots, and social posts. 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.608 and is locked in before the first frame is queued.

  1. Motion-first defaults

    Pixverse V5.5 Transition 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 Pixverse V5.5 Transition without leaving the video workspace.

  5. Pixverse V5.5 Transition shots

    Pixverse V5.5 Transition stays available for Pixverse V5.5 Transition without leaving the video workspace.

  6. Video shots

    Video stays available for Pixverse V5.5 Transition without leaving the video workspace.

From the shot board

Pixverse V5.5 Transition example output.
Pixverse V5.5 Transition 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 pixverse/pixverse-v5.5-transition 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":"pixverse/pixverse-v5.5-transition","aspect_ratio":"16:9","duration":5,"prompt":"A slow dolly across a rain-lit neon street, shallow depth of field.","resolution":"540p","seed":1,"thinking_type":"auto"}'

Shot settings

aspect_ratiooptional
string · 16:9 / 1:1 / 4:3 / 3:4 / 9:16
durationoptional
integer · 5 / 8 / 10
end_imageneeded
string
imageneeded
string
negative_promptoptional
string
promptoptional
string
resolutionoptional
string · 360p / 540p / 720p / 1080p
seedoptional
integer
thinking_typeoptional
string · enabled / disabled / auto

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 Pixverse V5.5 Transition render?

Authenticate, check the live model list for pixverse/pixverse-v5.5-transition, 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 Pixverse V5.5 Transition?

Pixverse V5.5 Transition accepts aspect_ratio, duration, end_image, image, negative_prompt, prompt, resolution, seed, thinking_type. Unknown keys are rejected before the render is queued, so a typo never burns a job.

What does a Pixverse V5.5 Transition render cost?

Pricing is per render and starts at $0.608. 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 Pixverse V5.5 Transition?

Yes — Pixverse V5.5 Transition 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 Pixverse V5.5 Transition 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