Automate the editing, keep the thinking.
Clippie takes a topic or a script and returns a narrated, captioned video in 16:9, from the editor or from your own code. The ideas, the facts and the upload stay with you.
- Story looks45 to choose from
- AI voices125, plus a voice library
- CaptionsIn 100+ languages
Sample clips of three 16:9 looks you can set for a whole channel.
Three ways to run it. Pick how hands-off you want.
- 1
In the editor
Type a topic, get a script, press generate, then fix any line or scene by hand. This suits most channels and gives you the closest review.
- 2
Through the API
Call the REST API to write a script, make an AI story video and render it to MP4. Webhooks tell your system when a job is done.
- 3
From an AI assistant
Connect Clippie’s MCP server to Claude, ChatGPT or Cursor and ask for a video in plain words. It can check your minutes and the cost before it spends them.
What automation means here. And what it does not.
“YouTube automation” usually means outsourcing a channel’s production so you are not the one editing. Here is where the line sits.
What Clippie can do for you
Each of these runs from one topic or script. Through the API, script drafts stop at 5 minutes and pasted scripts at 12,000 characters.
- First-draft scripts: From 30 seconds to 10 minutes, in a theme and a tone you choose.
- Voiceover: From 125 AI voices and the wider voice library, or your own imported voice.
- Scenes: One picture per line in the look you set, with optional AI motion.
- Captions and music: Word-timed burned-in captions and a background music library.
- Rendering: An MP4 at 1920x1080 or 1080x1920.
What you should not automate
Topic choice, fact checks and the final watch. AI drafts can state wrong dates and invent details, and your name is on the channel. Clippie also does not post to YouTube, write your thumbnail or manage your channel.
YouTube’s spam and monetization policies exclude mass-produced content made with little variation, and they call out AI specifically. A fully unattended pipeline is the exact thing those rules describe, so keep a person in the loop on every video.
A simple pipeline that holds up
If you build on the API, this order keeps the checks in the right place:
- Keep a list of topics you have researched yourself.
- Call write_script, then read and edit the draft.
- Call create_ai_story_video with your edited script, look and voice.
- Call preview_video to see frames from the video before you render.
- Render, watch it through and upload it by hand or with your own YouTube integration.
Made to run on repeat. With checks built in.
REST API and MCP server
Make videos from your own code, or from Claude, ChatGPT and Cursor, on the same plan.
Cost estimates
The API shows what a job would charge in credits and minutes before you run it.
Preview before render
See up to 4 still frames, from the opening to late in the video, before spending export minutes.
Reusable defaults
Save a voice, caption style and look so each video matches the last.
Redraw in another look
Redo a video’s pictures in a new look without changing the script.
Reddit and Roblox too
The API also makes Reddit story and Roblox rant videos, and adds captions to your own clips.
Frequently asked questions.
Is YouTube automation allowed?
Using tools or staff to produce videos is allowed. What YouTube refuses to monetize is mass-produced, repetitive content with no original input, whichever way it was made. Review every video and bring your own research and angle.
Is this passive income?
No, and we would not describe any channel that way. A channel needs ideas, checks and regular uploads. It may never meet YouTube’s thresholds, and Clippie makes no promise about views or earnings.
Can Clippie post to my channel?
No. Clippie gives you the finished MP4. If you build on the API, you can pass that file to your own upload step.
Do I need to code?
No. The editor does the same job by hand, and the MCP server lets an AI assistant run it from plain words. The REST API is there if you want a pipeline of your own.
Does the API cost extra?
No. It needs an active plan and spends the same minutes and credits as the editor. Scene pictures are included, and a call to estimate_cost shows the charge first.
