seedanceapi
Minimax H3 · Image to Video render example

MiniMax · Minimax H3 · image to video

Minimax H3 · Image to Video

Render Minimax H3 through the same job workflow as Seedance — from $0.135 per render.

Model idminimax/minimax-h3/image-to-videoShot spec480p · 540p · 768p · 1080p · 5sRatefrom $0.135

What it renders

MiniMax H3 Open Weights Image to Video animates a first-frame image, optionally with last-frame guidance, into coherent 480P / 540P / 768P videos with native stereo audio, 5-15 second… 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.135 and is locked in before the first frame is queued.

  1. Motion-first defaults

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

  5. Minimax H3 shots

    Minimax H3 stays available for Minimax H3 · Image to Video without leaving the video workspace.

  6. Video shots

    Video stays available for Minimax H3 · Image to Video without leaving the video workspace.

From the shot board

Minimax H3 · Image to Video example output.
Minimax H3 · Image to Video output
Minimax H3 · Image to Video example reference.
Minimax H3 · Image to Video 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 minimax/minimax-h3/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":"minimax/minimax-h3/image-to-video","duration":5,"prompt":"A slow dolly across a rain-lit neon street, shallow depth of field.","resolution":"480p","seed":1}'

Shot settings

durationoptional
integer · 3 / 4 / 5 / 6 / 7 / 8 / 9 / 10 / 11 / 12 / 13 / 14 / 15
imageneeded
string
last_imageoptional
string
promptoptional
string
resolutionoptional
string · 480p / 540p / 768p / 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 Minimax H3 · Image to Video render?

Authenticate, check the live model list for minimax/minimax-h3/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 Minimax H3 · Image to Video?

Minimax H3 · Image to Video accepts duration, 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 Minimax H3 · Image to Video render cost?

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

Yes — Minimax H3 · 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 Minimax H3 · 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