Same intro and outro on every Short: YouTube lists it as allowed

Yes. YouTube's channel monetization page lists "same intro and outro for your videos, but the bulk of your content is different" as allowed under its inauthentic-content policy (read 2026-10-03). The same page treats minimal variation across videos, and AI content made from generic templates that gives the impression of mass production, as not allowed. The intro is not the risk. The sameness of everything between the intro and the outro is.

That matters this week because the Shorts recommendation change reported on October 1 names template-based bulk changes as something that does not make a reused clip original (Search Engine Journal, read 2026-10-03). A shared bumper on your own episodes is a different thing from a template applied to someone else's clip, but the test you will be judged on is whether the middle is yours.

What a safe series shell looks like

Think of each episode as three slots: a fixed intro, a body that changes, a fixed outro. The shell is branding. The body carries the substance: its own storyline, focus or concept, which is the language of the second allowed example on the same page (a series following characters, or a review channel where each video has a distinct storyline, focus or concept).

Keep the shell short. A three-second bumper leaves 57 seconds of a one-minute Short for something only that episode contains.

Assembling it with Timeline

Timeline 1.0 takes an audio spine plus ordered video[] slots and returns one MP4, default 1080 by 1920. video[0].start must be 0 and later starts must increase. Every URL must already be on your workspace's media storage. POST /v1/timeline-1.0/plan is an unbilled compile check that returns the duration, segment count and estimated cost before you render; render itself is priced at $0.10 per output minute under the docs.

The script below plans one episode per voice file: three seconds of intro, the body from your own footage, three seconds of outro, all with a quarter-second fade. It uses placeholder URLs and prints the plan so you can see the cost before rendering.

import os, requests
H = {"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"}
INTRO = "https://media.sume.com/artifacts/artf_demo/intro.mp4"
OUTRO = "https://media.sume.com/artifacts/artf_demo/outro.mp4"

def plan(voice_url, seconds, body_url, body_in):
    body_len = seconds - 6
    doc = {
        "audio": {"url": voice_url, "duration_seconds": seconds},
        "video": [
            {"source_url": INTRO, "start": 0, "duration": 3},
            {"source_url": body_url, "start": 3, "duration": body_len,
             "source_in": body_in, "transition": {"type": "fade", "duration": 0.25}},
            {"source_url": OUTRO, "start": 3 + body_len, "duration": 3,
             "transition": {"type": "fade", "duration": 0.25}},
        ],
    }
    r = requests.post("https://api.sume.com/v1/timeline-1.0/plan", json=doc, headers=H)
    r.raise_for_status()
    return r.json()

print(plan("https://media.sume.com/artifacts/artf_demo/ep1.wav", 45,
           "https://media.sume.com/artifacts/artf_demo/ep1-body.mp4", 12))

Honest limits

A fixed shell does not rescue a thin body, and a rich body does not need a shell. Sume cannot tell you how YouTube's systems will weigh a series, and it does not guarantee reach or eligibility for monetization. If you render many episodes, vary the script, the footage and the claim of each one rather than only the title card, as the template bulk edits post walks through.

A per-episode variation checklist

Before you render a batch, check each episode against the same short list. The aim is that two episodes could never be mistaken for each other once the bumper is cut away.

• Does the body have its own claim, story beat or question, not just a new noun in the same sentence?
• Is the footage different, or is it the same stock sequence recolored?
• Does the voice say something specific that you could only say about this episode?
• Would the episode still make sense if the intro and outro were removed?
• If it is a character series, does each episode end differently?

Rendering many episodes

Timeline renders are ordinary jobs, so a loop over episodes submits one render each with its own Idempotency-Key; replaying a key is how you avoid paying twice after a timeout. Poll GET /v1/jobs/:id/status with backoff and read /result for the video_url, as in jobs and results.

If the body itself is produced by an agent from a brief, a Format bulk run queues up to 100 Format runs with a concurrency window of 1 to 16, and each item is its own run with its own instruction and receipt. The queue status completed means every item reached a terminal state, not that every item succeeded, so check counts.failed before you trust the batch.