Korea AI Basic Act Article 31: labeling an exported AI video
MSIT's guidelines ask for a human-recognizable label when AI video leaves the service. Here is how to burn a visible Korean label onto a clip with cues.

For AI video that is downloaded or shared outside the service where it was made, MSIT's transparency guidelines call for a label people can recognize, such as a visible or audible identifier, or a machine-readable marker added after a text or voice notice. On Sume, the visible route is a text overlay burned onto the MP4 with authored cues.
This is a description of the ministry's press release and Sume's docs, not legal advice. Sources were read 2026-09-30.
What do the guidelines say about exported content?
MSIT unveiled the Guidelines on Ensuring AI Transparency on January 22, for Article 31 of the AI Basic Act. They split content in two: output shown only inside a service environment (screens, UIs, apps), where flexible labeling such as a logo is allowed, and output exported by downloading or similar means, where "more explicit labeling is required". For AI-manipulated video that is hard to tell from reality, the labeling must be clearly recognizable.
The release also says a grace period of at least one year applies, and that fact-finding and penalties under the provision are deferred during it. It says the obligation falls on AI business operators who provide AI products and services, not on users who use them as tools; its example is a film company using AI video tools.
| Path | What the release describes |
|---|---|
| Human-recognizable | Visible or audible identifiers, for example a watermark |
| Machine-readable | Metadata embedded in the content, after a text or voice notification |
| Inside the service only | Flexible: UI indicators or visual marks such as logos |
How do I burn a visible Korean label onto a clip?
Send the finished clip to POST /v1/video-captions with cues. Passing text, start and end per cue burns authored overlay copy without speech-to-text, so a silent clip works too. Korean copy needs a Hangul-capable style: slam, punch and tiktok-green return 400 for Korean text, while an omitted style resolves to black-outline for Korean. The clip 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": "black-outline",
"cues": [
{ "text": "AI로 생성된 영상", "start": 0, "end": 5 }
]
}'Can I put a badge image on the frame instead?
Timeline compose takes one still and one video and returns one MP4 with both on screen, using operation of stack or overlay. Both URLs must already be media in your workspace, so import first with POST /v1/media-imports. See Timeline compose.
What does Sume not do here?
The caption and compose docs describe burned-in pixels, not metadata. If you choose the machine-readable path, that step is outside what these pages cover; see does Sume add C2PA or a watermark. For the comparable EU rule, read Article 50 video labeling.
Sources
Related posts
More in Use cases
- LinkedIn 30-minute video: build 1800 s with Timeline
LinkedIn's Videos API lists three seconds to 30 minutes. Sume Timeline 1.0 renders up to 1800 s in one MP4 at $0.10 per output minute: 30 minutes is the cap.
- LinkedIn Videos API: 500MB or 5GB? Plan for the lower number
LinkedIn's Videos API page lists a 75kb to 500MB file size and a 5GB maximum. Sume states no output file size, so measure the MP4 first.
- LinkedIn video captions: English SRT only vs burned-in text
LinkedIn's Videos API takes one English caption file, shown with SRT. Sume video-captions burns your cues text into the video and does not accept SRT uploads.
- LinkedIn Videos API thumbnail: pick a still from the clip first
LinkedIn's Videos API page says a system thumbnail may be added if you upload none. Sume video-frames returns jpeg stills at times you choose.
Written by Sume