To schedule faceless videos across 11 platforms, you need three things: a clip with no on-camera presenter, one place that holds every connected account, and a queue you can fill without opening each app. Creator OS does that. Generate the clip with Claude, upload it once, then schedule it through the web app, the CLI or Claude Code.
Claude (faceless clip)
|
v
media:upload -> med_ id (reusable)
|
v
posts:create --platforms instagram,tiktok,youtube,...
|
+-- web app (drag, pick date)
+-- CLI (batch script)
+-- Claude Code (skill + publish guard)
|
v
11 platforms + Skool, one workspaceHow Do I Schedule Faceless Videos to Multiple Platforms at Once?
You upload the file once, create one post record, and name every platform in that request. Creator OS applies each platform’s rules for you, so the same source clip becomes a Reel, a Short, a TikTok video and a feed video without four separate uploads.
The simple form of the REST API takes this shape:
POST /v1/posts
{
"content": "Three mistakes that cost me a month of editing",
"platforms": ["instagram", "tiktok", "youtube", "linkedin"],
"media": ["med_..."],
"schedule_at": "2026-03-04T17:00:00Z",
"timezone": "America/Toronto"
}
The docs at https://www.creatoros.ca/docs/api/posts list the full field set, including the advanced form where each platform gets its own options object. You do not need a base URL from memory: the docs page states it, and everything is authenticated with a cos_live_ key pinned to one workspace.
Two behaviours matter when you fan out a faceless clip:
- A file uploaded through
POST /v1/mediareturns amed_id you reuse on every platform. - Platforms you named but never connected come back in
missing_platforms. The rest still publish. That means a broken TikTok connection does not hold up your Reels.
If you want the broader picture of multi platform scheduling, the post on scheduling posts to multiple platforms covers the account setup side.
What You Need Before You Start: Claude, Creator OS, and Your 11 Accounts
Set up the connections once and the rest of this article is just commands and clicks.
| Piece | What it does | Where you set it up |
|---|---|---|
| Creator OS plan | One set of socials covers 11 platforms plus Skool, one account each | sign-up |
| MCP server | Lets Claude, ChatGPT, Cursor and others call your accounts | MCP docs |
| CLI | Scriptable scheduling, batch uploads, analytics | CLI docs |
| Claude Code plugin | Adds skills plus a publish guard that asks before anything goes out | plugin docs |
Start with the CLI install, which also drops 14 Claude Code skills onto your machine:
npx @creatoros/cli@latest init
creatoros auth:check
creatoros accounts:connect instagram
creatoros accounts:health
accounts:health is the one people skip. Run it before a batch. A token that quietly expired is the usual reason a scheduled faceless video only lands on three platforms.
For the plugin route:
/plugin marketplace add kevinbadi/creatoros-claude-plugin
/plugin install creatoros@creatoros
/plugin configure creatoros@creatoros
It asks for your cos_live_ key and needs Claude Code 2.1.287 or later.
Step 1: Generate the Faceless Clip With Claude Motion
This is where the no-face constraint gets solved before scheduling ever enters the picture. The faceless skills walk Claude through building a vertical clip from stills, b-roll, text cards, captions and voiceover, so nothing depends on someone sitting in front of a camera.
Ask for the format you actually need. A useful prompt is specific about ratio, length and audio:
Build a 28 second vertical 9:16 clip, no presenter.
Topic: three signs your content calendar is too full.
Structure: hook card, three text beats, CTA card.
Burned in captions, no background music.
Output a single mp4.
The full skill walkthrough lives in this post on Claude Motion faceless skills. Once you have the mp4, upload it once:
creatoros media:upload ./short-03.mp4
Keep that returned med_ id. Every scheduling call in the next two steps reuses it, and you never re-upload the same file four times.
One detail worth knowing before you pick a file: TikTok needs its consent fields filled, and Creator OS fills them for you when you use the simple post form. If you post through the advanced form you pass privacy_level, allow_comment, allow_duet, allow_stitch, content_preview_confirmed and express_consent_given yourself. On YouTube, a vertical short video becomes a Short automatically.
Step 2: Queue and Schedule Threads and Other Posts in the Creator OS Web App
The web app is the fastest path for a single faceless video you want to place by eye. Drag the file in, paste the caption, tick the destinations, pick a date.
Threads deserves its own note because text-first networks behave differently from video platforms. A faceless video posted to Threads sits under a 500 character caption cap, and the platform allows 250 posts per 24 hours. You can also build a multi post thread with threadItems, and use firstComment as the first reply in a chain, up to 500 characters. That is how you put a link under a Threads video, since captions there are not clickable.
Instagram has the same link problem, which is what firstComment is for there too. And if you are running faceless Reels, Trial Reels are worth testing: set post_type to short_video with trial_reel true to show the clip to non followers first. Instagram only allows this on accounts with 1,000 or more followers, and Creator OS refuses the post up front below that with trial_reel_needs_followers rather than failing silently later.
Comment handling is the other reason to keep the web app open. Replies are supported on Instagram, Facebook, X, Threads, YouTube, LinkedIn and Reddit. TikTok comment replies are not supported through the API, so plan your faceless TikTok comments strategy around hiding rather than answering.
Step 3: Batch Schedule Faceless Videos With the Creator OS CLI
One clip at a time does not scale. The CLI takes a JSON calendar and queues everything in one pass, and --dryRun tells you what would break before it breaks.
creatoros posts:bulk-upload --file march-shorts.json --dryRun
creatoros posts:bulk-upload --file march-shorts.json
For a single scheduled drop, posts:create covers it:
creatoros posts:create \
--text "Three signs your calendar is too full" \
--platforms instagram,tiktok,youtube,threads,linkedin \
--media med_abc123 \
--scheduledAt 2026-03-04T17:00:00Z \
--timezone America/Toronto \
--hashtags contentcalendar,creators
Check the caption against every limit before it goes out:
creatoros validate:post-length --text "Three signs your calendar is too full"
Then confirm the queue:
creatoros posts:list --status scheduled --from 2026-03-01 --to 2026-03-31
A table of the calls you will actually use for a faceless video pipeline:
| Task | Command |
|---|---|
| Upload once | creatoros media:upload ./clip.mp4 |
| Check a URL is valid media | creatoros validate:media --url ... |
| Queue a scheduled post | creatoros posts:create --scheduledAt ... |
| Reschedule | creatoros posts:update <postId> --scheduledAt ... |
| Retry a failed platform | creatoros posts:retry <postId> |
| Pick a posting window | creatoros analytics:best-time --platform tiktok |
analytics:best-time is the part most schedulers leave to guesswork. Ask it per platform before you write the calendar, not after.
Step 4: Automate the Pipeline in Claude Code
Once the steps are stable, hand them to an agent. The plugin ships a mod with a live pane and a publish guard, which is the difference between a helpful agent and one that posts at 2am.
/creatoros
/cos-stats
/cos-health
The guard asks Proceed or Cancel before anything is published, spent or deleted, so a scheduled faceless video does not leave your machine until you say so. Skills arrive as slash commands too, including post-shortform, schedule-posts and analytics. The skills also come in through the MCP server as prompts, so they show up in the prompt menu of any MCP capable app.
If you want a standing job instead of a conversation, the CLI can run a skill on a cron:
creatoros automations:create weekly-shorts \
--schedule "0 9 * * 1" \
--skill post-shortform
For a heavier setup, Social Agents is an open source harness that runs your socials on Creator OS: it interviews you about your brand, then posts, replies and reports. Start it with npm start creatoros social-agents. Watch the walkthroughs on the KevBuildsApps YouTube channel, and the launch video shows the whole toolchain in motion.
Can It Create Videos and Schedule Them in One Flow?
Yes, with one honest boundary: the clip generation happens in Claude, and the scheduling happens in Creator OS. An agent holding your API key can call both in sequence.
A working loop looks like this. Read last week’s numbers, decide the next topic, generate the clip, upload it, schedule it, then read the result. Creator OS supplies the posting and the numbers. Your prompt or workflow decides what changes next.
For faceless video specifically, the numbers that matter are already there. get_post_analytics returns reelsSkipRate (the share of views that swiped away in the first three seconds), plus igReelsAvgWatchTime and igReelsVideoViewTotalTime in milliseconds. Meta reports these for Reels only. So an agent can look at a skip rate, rewrite the hook card, regenerate, and reschedule, all without a human in the loop until the publish guard fires.
What Creator OS does not do is invent the edit for you. The judgment about what to cut stays with you or your agent. If you want the same loop for still images and carousels, bulk scheduling through the REST API covers the request shapes.
FAQ
How do I schedule posts for multiple platforms?
Upload the media once to get a med_ id, then create one post record that lists every platform you want, with a schedule_at time and a timezone. Creator OS applies each network’s rules and returns any unconnected platforms in missing_platforms while the rest still publish. You can do this from the web app, the CLI or the MCP server.
Can Creator OS create faceless videos and schedule them automatically?
Creator OS handles the upload, scheduling, publishing and analytics. The faceless clip itself is generated in Claude using the faceless skills, then handed to Creator OS as an mp4. The two halves chain together in Claude Code or any MCP capable agent, and the publish guard asks before anything leaves.
Can I schedule Threads posts from the same dashboard?
Yes. Threads is one of the 11 platforms, and a post can target Threads alongside Instagram, TikTok and the rest in the same request. Threads caps posts at 500 characters and 250 posts per 24 hours, supports multi post threads through threadItems, and treats firstComment as the first reply in a chain.
What file formats should faceless videos use for TikTok and other platforms?
Export a single mp4 from your Claude workflow, vertical 9:16 if the clip is headed for Reels, Shorts or TikTok. Upload it once with media:upload and reuse the returned id everywhere. On TikTok, Creator OS fills the required consent and privacy fields when you use the simple post form.
Do I need the Claude Code plugin or is the CLI enough?
The CLI is enough for uploading, scheduling, rescheduling and reading analytics, and every plan includes it. The plugin adds the skills, the live pane, the instant stats commands and the publish guard that asks before publishing, spending or deleting. Use the plugin when an agent does the scheduling for you.
Get started
Connect your accounts, upload one faceless clip and put it on a schedule. Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. Start at creatoros.ca/sign-up, then keep the docs open while you build the calendar.
Get started for $0
Free trial for new subscribers. Cancel anytime.