MSN's AI content policy: AIAC vs unreviewed AIGC for video makers
MSN separates AI-assisted content from unreviewed AI-generated content, and asks for disclosure now. What a Sume video publisher on MSN should do.
MSN's Partner Hub draws a line between two kinds of AI content. The MSN AI content policy, read on 2026-10-05, distinguishes AI-assisted content, abbreviated AIAC, from unreviewed AI-generated content, AIGC. It prohibits unreviewed AIGC with limited exceptions. For AI-assisted content it recommends disclosure now.
The page adds that MSN expects to ask partners to tag all AI-assisted content within the next 6 to 12 months. As of 2026-10-05, that is a forward-looking statement, not a current requirement.
Two buckets
| Category | Meaning | Policy position |
|---|---|---|
| AIAC | AI-assisted content that a person reviewed and shaped | Disclosure recommended now |
| Unreviewed AIGC | AI-generated content published without review | Prohibited, with limited exceptions |
| All AI-assisted content | Everything touched by AI | Tagging expected to be requested within 6 to 12 months |
What it means for a video made with Sume
A clip generated through the Sume video API is AI-generated media. Whether it is AIAC or unreviewed AIGC depends on what you do next. A clip that you prompted, watched, cut and approved, then wrote around, fits the reviewed side. A batch published straight from a job result with nobody watching fits the unreviewed side, which MSN prohibits with limited exceptions.
I did not find a definition of the exceptions in what I read, so I will not list them.
Make review visible
None of this is MSN-specific tooling. Sume's docs do not describe an MSN or Microsoft partner integration, and they do not claim to add provenance data to clips. 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.
- Add a human review step before publishing, and record who watched the clip and when.
- Store the Sume job id with that review note. The
metadatafield on a Sume job is stored on the job and is not sent to the provider, so it can hold a reviewer initials and date. - Disclose AI assistance in the article or video description now, since MSN recommends it today.
- Tag everything consistently so you can answer if MSN later asks partners to tag all AI-assisted content.
Sources
Related posts
More in Use cases
- A holiday music video from one Lyria track: 18 clips, about $23.50
Lyria track $0.125, eighteen 10-second Omni Flash clips at 720p $22.50, Timeline $0.30, captions $0.60. Total about $23.53 for 3 minutes.
- Music visualizer clip: MiniMax H3 Max, image plus audio reference
Make a 10-second visualizer from cover art plus a track excerpt with minimax-h3-max on Sume: $1.00 at 768p; audio alone is not a valid reference.
- Napkin sketch to product render: one reference on GPT Image 2.5
Turn a photographed napkin sketch into a product render with one input reference on GPT Image 2.5. Set aspect_ratio auto to keep the shape. Code and prices.
- New Year countdown video music: build to midnight with a timed prompt
Write a timed Lyria 3.5 prompt that builds for 50 seconds and hits at midnight. $0.125 a take on Sume, then a Timeline render at $0.10 under your countdown.
Written by Sume