Dev.to scheduler
DEV articles with a real title field.
Connect DEV.to with an API key. Create uses a title plus the caption as the body — it publishes as an article, not a social caption. No media, no inbox. Analytics can include page views, reactions, and comments from DEV.
Named AI models, then the composer
Generate the file with Veo, Nanobanana, Kling, Recraft, Grok, Flux, or Seedance, then schedule it to Dev.to 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
Dev.to is publish-first in Postlaty. Use another connected network when you need comments or DMs in the same inbox.
Cursor, Claude, ChatGPT via MCP
Connect Dev.to 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 Dev.to posts with Postlaty?
Sign up, connect Dev.to (Credentials on Connect), 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.
Is DEV.to a social post or an article?
An article. Fill the title on Create; the caption is the body. There is no image/video attach and no Postlaty inbox for DEV. Use MCP if you want an agent to draft and publish the article.
Can Cursor or Claude post to Dev.to?
Yes. Create an API key in Profile, add the Postlaty MCP server to the agent, connect Dev.to in the app, then ask it to generate and schedule. Same pipeline as the UI.
Is Postlaty only a Dev.to tool?
No. Dev.to is one of 19 networks. The same subscription includes the AI studio, inbox where supported, REST, and MCP.