MiniMax H3 license: AI-generation identifier is encouraged

No, it is not required. Section III.3.b of the MiniMax H3 Community License says you are "encouraged to" add an AI-generation identifier to files produced using generative AI models including MiniMax H3. The same list encourages a "Powered by MiniMax H3" notice and a public write-up. The text does not say what the identifier must be.

This quotes the license, read 2026-10-01; it is not legal advice. What Sume documents is a visible plate (Timeline compose) and burned-in text (video captions). It does not document embedded metadata or a provenance feature.

What does the license ask for, and what does it leave open?

The wording is "an AI-generation identifier", with no format. Exhibit A, item 12, separately forbids publishing machine-generated content to a public environment without clearly and prominently disclosing it. That item is a use restriction, not an encouragement.

What can Sume put on the video itself?

Two documented routes. Timeline compose puts one still and one video on screen in one MP4; in overlay mode the plate is placed by position, width_ratio and margin_ratio. Video captions can burn authored overlay text from cues or segments, which skips speech-to-text.

How do I burn a text label with captions?

Send phrase-level cues with text, start and end in seconds. The docs say this burns exactly that copy at those times, and it is the path for silent clips. The video must be a public HTTPS URL.

curl -X POST https://api.sume.com/v1/video-captions \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: ai-label-001" \
  -d '{
    "video_url": "https://example.com/clip.mp4",
    "style": "slam",
    "cues": [{ "text": "AI-generated video", "start": 0, "end": 4 }]
  }'

Does a visible label satisfy anything?

Sume makes no claim that it does. Neither this license nor a platform's rules are settled by a caption; the docs describe how to draw text, not what text a rule needs. For the EU icon case, see that post.