AI voice reading news articles on YouTube Shorts: allowed?

Not on its own. YouTube's reused content policy (read 2026-10-03) lists readings of unoriginal materials, such as websites or news feeds, as not allowed for monetization. An AI voice that reads an article aloud over stock visuals is a reading of a website. The same policy does allow content where you add commentary or explain your contribution, so the fix is to say something about the story, not to read it.

Sume can fetch a page for research and generate your visuals and voice, but the analysis has to be yours. No tool in the API decides what counts as your contribution.

Where is the line between a reading and a report?

The policy page's allowed examples are the guide: critical reviews, reaction videos with commentary, edited footage with a storyline and commentary. Its not-allowed examples include non-verbal reactions without commentary and content copied without substantive modifications. Applied to news, the rule of thumb is that the viewer should learn something from you that they would not learn from the article.

The reach side is separate. As reported by Relevant Audience, YouTube said on October 1, 2026 that it wants own commentary, analysis and storytelling and is reducing reach for channels that mainly aggregate or re-upload clips. That coverage is about clips, not text, but the direction is the same.

How do you research a story without copying it?

Sume's scrape endpoint reads a public page to markdown, which is useful for checking facts and quotes. Per the OpenAPI schema, url is required and formats accepts markdown, links, html, json, screenshot, rawHtml and images. In Sume's hosted MCP the same family is the crawl_* tools, such as crawl_scrape, per the MCP tools and gates page. Use the output as reference material, then write from it:

curl -X POST https://api.sume.com/v1/firecrawl/scrape \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: research-note-001" \
  -d '{
    "url": "https://example.com/post-you-are-researching",
    "formats": ["markdown"],
    "only_main_content": true
  }'

Check the site's own terms before you reuse its text. Quote briefly, name the source on screen, and put your reasoning in the script. A page's text pasted into a narration is the reading YouTube names.

What does a good news Short contain?

Start with a claim that is yours: what the story gets wrong, what it leaves out, or what it changes for a specific viewer. Use one or two facts from the article as evidence, name the source on screen, and spend most of the runtime on your reasoning. A good test is whether the Short would still make sense if the article vanished, because then the Short, and not the article, carries the idea.

Keep the claim checkable. If you cite a number, read it from the original page, not from memory, and say where it came from. Sume's scrape output is for exactly that check. It makes fact-checking faster; it does not make a copied script into a report.

Pace matters too. A Short that opens on your conclusion and then shows the evidence keeps the viewer on your reasoning from the first second, while one that opens by reciting the headline puts the article first and you second.

What about the voice and the AI label?

A synthetic narrator is not the issue by itself. YouTube's disclosure page (read 2026-10-03) asks for disclosure when content makes a real person appear to say or do something they did not, and lists cloning your own voice and caption creation as edits that need none. The page also says disclosure does not restrict reach or monetization eligibility. Visuals can come from Video generation, and Video captions burns the lines in, but neither turns a reading into analysis.

• Do not narrate an article word for word, with any voice.
• Name the source on screen and quote sparingly.
• Lead with your claim, then use the story as evidence.
• Disclose realistic AI scenes; a news visual that looks real but never happened is the clearest case.