MiniMax-H3
MiniMax-H3 Regeneration
- Regenerate MiniMax-H3 768P video into 2K
- Prefer source_task_id only; the platform auto-fills prompt, media, and source video
- Not generic upscaling: source must be an H3 768P output
- Per-second billing ($0.045/s output + same rate for reference videos)
POST
Full 2K Workflow (optional): ① Context-IR → ② MiniMax-H3 with
resolution: "768P" → ③ this endpoint to 2K.768P unit price + regeneration unit price = direct 2K unit price, with cheaper iteration.Recommended: source_task_id only
Pass only the task_id of a successful MiniMax-H3 · 768P job. The server fills in the rest.
source_task_id must satisfy all of the following, or you get a sync 400 (no task, no charge):
Authorization
string
requis
Bearer Token auth. Get a key from the API Key Management Page.
Request Parameters
string
requis
Fixed value:
MiniMax-H3-Regenerationstring
requis
ID of a successful MiniMax-H3 · 768P task on this platform.When set, you do not need
prompt, source video, or reference media — the server fills them.Source Video Specs
The source must match MiniMax-H3 768P output:
Spec failures fail the task with a reason and refund.
Billing
Per second (same structure as H3 generation, different unit prices):Media from the original 768P job is billed again on regeneration — not output seconds only.Examples
With
source_task_id, pre-charge uses the original task’s real output seconds.
Request Examples
source_task_id
Common Errors
Submit-time parameter errors are sync 400 (no task, no charge):
Failed tasks are auto-refunded.
Response
integer
Status code; 200 on success
array
On submit:
status / task_id; when complete, result is in result.videos (same as normal video jobs)Poll Get Task Status. On success use
result.videos[0].url.