seedanceapi
Pixverse V6 · Extend render example

PixVerse · Pixverse V6 · video extend

Pixverse V6 · Extend

Render Pixverse V6 through the same job workflow as Seedance — from $0.034 per render.

Model idpixverse/pixverse-v6/extendShot spec360p · 540p · 720p · 1080p · 1–15sRatefrom $0.034

What it renders

PixVerse V6 Extend continues and enhances existing video content by analyzing the ending segment and generating new frames forward. 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.034 and is locked in before the first frame is queued.

  1. Motion-first defaults

    Pixverse V6 · Extend 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 Extend shots

    Video Extend stays available for Pixverse V6 · Extend without leaving the video workspace.

  5. Pixverse V6 shots

    Pixverse V6 stays available for Pixverse V6 · Extend without leaving the video workspace.

  6. Video shots

    Video stays available for Pixverse V6 · Extend without leaving the video workspace.

From the shot board

Pixverse V6 · Extend example output.
Pixverse V6 · Extend output
Pixverse V6 · Extend example reference.
Pixverse V6 · Extend 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 pixverse/pixverse-v6/extend 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-v6/extend","duration":5,"generate_audio_switch":false,"prompt":"A slow dolly across a rain-lit neon street, shallow depth of field.","resolution":"720p","seed":1,"style":"anime"}'

Shot settings

durationoptional
integer · default 5
generate_audio_switchoptional
boolean · default false
negative_promptoptional
string
promptoptional
string
resolutionoptional
string · 360p / 540p / 720p / 1080p
seedoptional
integer
styleoptional
string · anime / 3d_animation / clay / comic / cyberpunk
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 Pixverse V6 · Extend render?

Authenticate, check the live model list for pixverse/pixverse-v6/extend, 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 V6 · Extend?

Pixverse V6 · Extend accepts duration, generate_audio_switch, negative_prompt, prompt, resolution, seed, style, video. Unknown keys are rejected before the render is queued, so a typo never burns a job.

What does a Pixverse V6 · Extend render cost?

Pricing is per render and starts at $0.034. 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 V6 · Extend?

Yes — Pixverse V6 · Extend 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 V6 · Extend 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