MiniMax H3 Recast on SJolt: API Guide and Video Workflow

Recast starts with footage you already have. The source supplies the performance and scene, while the reference photos supply the appearance of the new people. By default, the photos map to the main people from left to right. An optional prompt can clarify who replaces whom and which details should stay consistent.

This is useful when the action and setting already fit your brief but you want to explore a different cast. A dancer can keep the recorded choreography, for example, while the reference photo directs a different appearance. Preservation is the intended behavior, so still inspect the output for changes in identity, motion, timing, and sound.

• Try MiniMax H3 Recast on SJolt

The two H3 workflows have separate request contracts. Recast uses one source video and replacement photos. Reference-to-video creates a new scene from a prompt and supporting media. Choose the workflow first, then use its documented fields rather than copying parameters between the endpoints.

• Edit an existing clip with H3 Recast
• Create a new scene with H3 reference-to-video
• Explore H3 text-to-video

The current SJolt Recast endpoint accepts the following fields inside input. Start with a short clip in which the intended people are clearly visible, and use one clear reference photo per replacement person.

Keep the source video within the 15-second limit before submitting. There is no separate duration or aspect_ratio field on this endpoint. The replacement-photo field is image_urls; each image describes a person rather than defining the first frame of a new video.

Use reachable media URLs for API requests. A file on your laptop or a URL that opens only in a signed-in browser will not work as a public input. SJolt’s API documentation also covers uploading assets when you need hosted URLs.

• Review the Recast model parameters
• Read SJolt file-upload and authentication documentation

• Open the MiniMax H3 Recast model page and upload one MP4 source clip lasting 5–15 seconds.
• Upload 1–4 replacement photos. Arrange them in the intended left-to-right mapping, or explain a different mapping in the prompt.
• Choose 768p or 1080p. Keep the resolution fixed during your first comparisons so you can judge the effect of changing the references or prompt.
• Add a short prompt when the cast mapping or clothing needs clarification. Leave it empty when the default mapping is sufficient.
• Run the task, review the completed clip, and refine one input at a time before moving the request into your application.

Replace the sole dancer with the adult woman in the reference photo.
Use her face, black braids, and midnight-blue dress with gold trim.
Preserve the source choreography, camera movement, courtyard, and original audio.
Keep one coherent person throughout the clip.

This prompt is a starting point for a single-person clip. For multiple people, describe the visible position or role of each source person so the replacement mapping is unambiguous. Avoid asking for a new camera path or unrelated action when retaining the source performance is the goal.

Set SJOLT_API_KEY in your server environment, then replace the example media URLs with accessible files you control. The request below submits a Recast task with one replacement person at 1080p. The source clip itself must be 5–15 seconds long.

curl --request POST 'https://sjolt.ai/sjolt-ai/v1/minimax/h3-recast/video-edit' \
  --header "Authorization: Bearer $SJOLT_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
    "input": {
      "video_url": "https://example.com/source.mp4",
      "image_urls": ["https://example.com/replacement-person.jpg"],
      "prompt": "Replace the sole dancer with the person in the reference photo. Preserve the source choreography, camera movement, courtyard, and original audio.",
      "resolution": "1080p"
    }
  }'

A successful submission returns data.task_id. Store it and query that task rather than submitting again while you wait. Replace YOUR_TASK_ID in the following request with the returned identifier.

curl 'https://sjolt.ai/sjolt-ai/v1/tasks/YOUR_TASK_ID' \
  --header "Authorization: Bearer $SJOLT_API_KEY"

The task status is 0 while running, 1 on success, and 2 on failure. Read the completed video links from data.output_urls after success. Use polling with a delay and a timeout, stop at either terminal status, and show failures clearly instead of automatically creating another billable task.

You can also supply a top-level webhook URL alongside input. Webhook delivery is best-effort; the task query remains the source for final status and result URLs. Keep your SJolt API key on the server, and pass only the task state and result needed by your client application.

• Read the Recast API request reference
• Read SJolt task polling and webhook documentation

As checked on October 6, 2026, SJolt’s public Recast rates are $0.30 per second at 768p and $0.45 per second at 1080p. Billing uses the measured source-video duration rounded up to the next whole second. Reference photos add no extra charge.

For budgeting, multiply the rounded source duration by the selected resolution rate for each generation attempt. Include the attempts you expect to reject when estimating the cost of an accepted shot. Confirm the current rate on SJolt’s model or pricing page before a production batch.

• View current Recast pricing on SJolt
• Compare model prices

A completed task means a result is available; it does not establish that the clip meets your creative brief. Compare the output with the source and reference photos, particularly where people turn, overlap, or leave and re-enter the frame.

• Identity: confirm that each replacement remains recognizable across face angles, motion, and partial occlusion.
• Mapping: for multiple people, verify that the intended photo maps to the correct person in every shot.
• Performance and setting: inspect the choreography, camera movement, scene transitions, background, and clothing for unwanted changes.
• Audio and timing: listen to the entire output and check its alignment with the source performance.
• Delivery: open the result file, check its actual resolution and duration, and keep a copy in your own asset storage for the downstream edit.

Record the input assets, prompt revision, resolution, task ID, and acceptance decision for each attempt. When you find a combination that works, keep the request structure and automate the same Recast endpoint through SJolt. The request example in this guide was checked against SJolt’s API contract; no new paid generation was run for this article update.