MiniMax H3 aigc_watermark defaults to false: what Sume exposes
MiniMax's H3 API has an aigc_watermark boolean, off by default. What it does, and what to do for a minimax-h3 clip made through Sume.

MiniMax names its watermark option for what it is: an AI label. The MiniMax-H3 video generation reference, read on 2026-10-05, lists aigc_watermark as a boolean whose default is false, described as whether to add an AIGC label watermark to the generated video. So if you call MiniMax directly and say nothing, the page indicates you get no label mark.
The question for a Sume user is which of those two behaviours your clip gets, because Sume lists minimax-h3 as a model.
What Sume documents for minimax-h3
Sume's video generation docs list minimax-h3 with durations of 5 to 15 seconds, and minimax-h3-max as the faster 768p variant. Billing reserves the provider list price times 1.25 at submit. I searched the docs and found no aigc_watermark or watermark field on the public API, and no statement of which value Sume sends to MiniMax.
That means two things you cannot assume. You cannot assume the clip has a visible AIGC mark, and you cannot assume it does not. Generate a short test and look.
A test that settles it
| Item | MiniMax API | Sume |
|---|---|---|
| AI label switch | aigc_watermark, default false | None documented |
| Where you set it | In the MiniMax request | Not available |
| How to know the result | Request value | Inspect the delivered file |
How to inspect and what to do next
Generate the shortest clip you can, 5 seconds, play it full frame, and check the corners and the last second, where marks often sit. Then run ffprobe -show_format and read the tags. If neither shows a mark or metadata, treat the file as unlabelled.
Unlabelled does not mean exempt. Platforms that ask for an AI toggle, such as YouTube's altered or synthetic setting, still apply to you whatever the file says. If a visible label is required, burn one in with Sume's video captions cues, or add one in your editor.
Save the Sume job id, the model and the date next to the file. Sume job metadata is stored with the job and is not sent to MiniMax, so tag your disclosure decision there. Sume's docs describe a metadata field on video, image and music jobs that Sume stores on the job and does not send to the provider. I found nothing in the docs about Sume adding, keeping or removing C2PA credentials, watermarks or platform labels, so treat that as undocumented and check the delivered file.
Sources
Related posts
More in Developers
- Omni and Seedance clips in one timeline: the fps resample warning
Clips from two video models can have different frame rates. Sume's timeline warns with output_fps_resamples_sources; probe each clip, then set output.fps.
- mode subscribe on Sume images is a 30-second wait: poll instead
On Sume, mode subscribe is an alias of sync with one wait of at most 30 seconds and no events. For a longer wait, submit async and poll status in your client.
- Model calls image-generations_create? Use generate_image
New LLMs may emit old Sume tool names. The hosted server maps dots to underscores and documents two retired aliases that now point at new names.
- 'model_params has an empty allowlist': omit it or send {}
Video Router v1 has no pass-through knobs. model_params with any key gets a 400; {} is fine. /v1/videos refuses provider.options the same way. What to change.
Written by Sume