X
Posts, threads, images and scheduled follow-ups.
Native connections for every major network, plus a REST API and MCP server so your assistants and internal tools can publish through the same engine.
Each connection is authorized through the network's official flow. We store scoped tokens, never passwords.
Posts, threads, images and scheduled follow-ups.
Company pages and personal profiles.
Feed posts, carousels and Reels captions via the linked page.
Pages, groups and community posts.
Short-form video posts with caption and hashtags.
Shorts and video metadata, titles and descriptions.
Conversational posts connected to your Instagram account.
Review requests, approvals and weekly digests.
Publish results and analytics pushed to your endpoint.
The publishing engine is available programmatically for every Pro workspace.
Settings → API keys issues a workspace-scoped key you can rotate at any time.
POST a brief, a network list and a timing preference. The response returns scheduled post IDs.
Paste the remote MCP URL into Claude, ChatGPT, Cursor or VS Code and approve the tools once.
Claude, ChatGPT, Cursor, VS Code and any other MCP client can draft and schedule inside the conversation you already have open.
Internal dashboards, CMS workflows and product launches can publish through the API with idempotent requests.
Yes. You can authorize a personal profile and a company page for the same workspace and choose the target per post.
The connection is flagged in settings, the affected queued posts are paused, and you are notified before publishing.
The API publishing endpoint is one of the paid plans, so you can test it alongside the rest of the studio.
Sign in with Google, pick a plan, and let the studio draft the week while you keep shipping.