Publishing
Text ❌ · Images ❌ · Video ✅
Inbox
Comments
Analytics
Views, likes, comments
Why Postlaty
Why schedule YouTube with Postlaty
Named AI models, then the composer
Generate the file with Veo, Nanobanana, Kling, Recraft, Grok, Flux, or Seedance, then schedule it to YouTube from the same login. You are not exporting from another lab.
One clip, 19 networks
Cross-post the same encode to TikTok, Reels, Shorts, and the rest of Postlaty’s 19 channels. Each network keeps its own caption.
Inbox where the API allows it
YouTube inbox: Comments. Reply from Postlaty instead of hopping into the native app for every thread.
Cursor, Claude, ChatGPT via MCP
Connect YouTube once. Then an agent on REST or MCP can generate and schedule to this account. Setup lives on each agent page (for example /cursor).
MCP
Ask Cursor, Claude, or ChatGPT
Connect YouTube in Postlaty, add MCP, then paste this.
Generate a 9:16 post for YouTube and schedule it tomorrow at 9:00. Use my connected YouTube account in Postlaty.
Setup for each client: all agents · API docs
FAQ
Frequently Asked Questions
Sign up, connect YouTube (OAuth Allow popup), then create in the AI tab or upload a file and schedule from the composer. Starter is $29/month for 10 channels across 19 networks, with a 7-day trial.
Publishing is Shorts-oriented: videos you send through Postlaty go out as Shorts. YouTube needs a video file, not a text-only post. Comments come back into Inbox. Analytics include views, likes, and comments.
Not yet. YouTube picks a still from the Short. After it publishes, you can change it in YouTube Studio if your channel is verified.
Yes. Create an API key in Profile, add the Postlaty MCP server to the agent, connect YouTube in the app, then ask it to generate and schedule. Same pipeline as the UI.
No. YouTube is one of 19 networks. The same subscription includes the AI studio, inbox where supported, REST, and MCP.
