X (Twitter) scheduler
Post to X. DMs in Inbox. Models in the AI tab.
Schedule X (Twitter) posts from Postlaty: text, images, or video, including mixed media. DMs show in Messages after you reconnect with dm.read / dm.write. Native X comments, mentions, and post analytics need a paid X API plan, so those stay paused on our side.
Named AI models, then the composer
Generate the file with Veo, Nanobanana, Kling, Recraft, Grok, Flux, or Seedance, then schedule it to X 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
X inbox: DMs. Reply from Postlaty instead of hopping into the native app for every thread.
Cursor, Claude, ChatGPT via MCP
Connect X once. Then an agent on REST or MCP can generate and schedule to this account. Setup lives on each agent page (for example /cursor).
Frequently asked questions
How do I schedule X posts with Postlaty?
Sign up, connect X (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.
Why are X comments and analytics missing?
X charges for those API endpoints. Postlaty still publishes to X and can read/send DMs after a reconnect. We do not pretend comments, mentions, or impressions work without that paid X API access.
Can Cursor or Claude post to X?
Yes. Create an API key in Profile, add the Postlaty MCP server to the agent, connect X in the app, then ask it to generate and schedule. Same pipeline as the UI.
Is Postlaty only an X tool?
No. X is one of 19 networks. The same subscription includes the AI studio, inbox where supported, REST, and MCP.