Wan 3.0 Prime API

Wan 3.0 Prime Video extend continues a clip you already have. Send it as video_url; a prompt for what happens next steers the continuation, and without one the model carries the scene on by itself. The final frame of your clip becomes the opening frame of a new Wan 3.0 Prime image-to-video shot of 2 to 30 seconds, and the two are joined into one MP4: your original first, then the continuation, with the repeated seam frame removed. The new segment also comes back as its own file, so you can keep extending or edit the pieces separately.

Continuity comes from the last frame. Wardrobe, set, light and where everyone stands carry over because the new segment literally starts on your final frame. Motion does not carry over the same way: the model sees one still, not the whole clip, so describe the movement you want to continue instead of assuming it will keep its speed or direction.

Optionally, choose where it lands. Pass last_image_url and the new segment ends exactly on that image, so a shot can return to its hero angle or arrive at a set composition. Without it the model decides how the segment ends. The start is always the final frame of your clip.

One file back, plus the new piece on its own. The joined MP4 keeps your clip’s frame rate and its framing, with no black bars. To line the seam up, the picture may be trimmed or adjusted by a few percent at the edges. If the model returns a noticeably different shape, the new segment is scaled to fill your frame and centered, cropping what spills over. It is encoded as H.264 MP4 with AAC sound. Sound from your source stays; sound generated for the new segment follows it; a silent side is padded with silence so picture and sound stay in step at the seam. The second asset in the output is the new segment alone, ready for another extend or for an editor.

Everything else is Wan 3.0 Prime image-to-video. The new segment runs on the same routes, with the same content range and the same per-second price as the image-to-video endpoint, and a failed generation is refunded the same way. If the generation succeeds but the join itself cannot be built, the task fails and the charge is refunded.

Lengthen a shot that ended too early: a product turntable that stops before the label faces camera, or a walk that cuts before the subject reaches the door. Extend it by a few seconds and describe only the remaining motion.

Build a longer sequence step by step. Generate a first shot, extend it, then extend the joined result again; each step bills only the seconds it adds. Because every step starts from a single frame, watch each seam before stacking the next one.

# Generate the idempotency key once; reuse it when retrying after a lost response.
export SPICY_IDEMPOTENCY_KEY="${SPICY_IDEMPOTENCY_KEY:-$(uuidgen)}"
curl -X POST https://api.spicyapi.ai/api/v1/jobs/createTask \
  -H "Authorization: Bearer $SPICY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $SPICY_IDEMPOTENCY_KEY" \
  -d '{
  "model": "alibaba/wan-3.0-prime/video-extend",
  "input": {
    "duration_seconds": 5,
    "resolution": "720p",
    "video_url": "https://example.com/reference.mp4"
  }
}'

# Copy data.taskId from the response into TASK_ID, then poll the status.
TASK_ID="TASK_ID_FROM_RESPONSE"
curl "https://api.spicyapi.ai/api/v1/jobs/recordInfo?taskId=$TASK_ID" \
  -H "Authorization: Bearer $SPICY_API_KEY"

See the API reference for authentication, the complete schema, polling, and error handling.