Frequently asked questions

A social media scheduler built so an AI assistant can use it. An assistant or a script can draft, schedule and track posts through an MCP server or an HTTP API, using credentials you control. There is also a normal dashboard composer. See API & MCP.

Threads and Instagram are live. YouTube is in limited release: you can connect a channel, but until Google completes its audit of our API access, videos uploaded through cometpost stay private. Facebook Pages is waiting on Meta's app review. TikTok and X are coming soon and are not available yet. The platform status table is kept current.

No. Instagram support is feed images (JPEG) and image carousels on professional accounts. There is no video, no Reels and no text-only Instagram post.

The dashboard composer sets one time for the whole post. Through the API or the MCP server, a single destination of a scheduled post can be rescheduled on its own, as long as it has not started publishing.

Only if you allow it. When you create an API key or connect an assistant, scheduling is off by default, so what it creates are drafts. You review each destination in the dashboard and publish. An agent cannot publish a draft, delete a post, change billing or create credentials; those need you signed in.

Free is $0 for 3 Channels and 3 videos a month, with no card. Paid plans are not on sale yet. They will be Starter at $14 a month for 15 Channels, Growth at $29 for 50 and Scale at $59 for unlimited, with annual billing at two months free ($140, $290 or $590 a year). Posts are unlimited on every plan, and the API and MCP server are included on every plan. For early access to a paid plan, email hello@cometpost.app. Details on the pricing page.

One connected account on one platform. Plans are priced by how many Channels you connect, not by how many posts you make.

Free stays open until 500 workspaces are paying. After that, new signups need a paid plan, and everyone who joined Free before then keeps it.

No. cometpost requests the permissions needed to identify which account you connected and to publish content you have authored and scheduled. It does not read direct messages, does not export follower lists, and does not collect data beyond what the granted permissions require. This is set out in detail in the privacy policy.

No. Content you upload or compose is used to publish that content to the platforms you chose, and for nothing else. We do not use customer content to train machine-learning models, and we do not sell or license it.

The application, its database and its scheduling engine run on Railway. Uploaded media is kept in S3-compatible object storage (Cloudflare R2). The tokens that let cometpost publish to your accounts are additionally encrypted before they are written to the database. Payments go through Stripe and operational email through Resend. The privacy policy covers who receives what.

Yes, both from the dashboard under Settings, Account. Download data export gives you a JSON file of your workspace, posts, delivery history and media metadata, with temporary links to your media. Delete account starts immediately and cannot be undone; the data deletion page has the steps and what is kept.

From inside cometpost, or from the platform's own connected-apps settings. Revoking access there immediately stops cometpost from publishing to that account. Instructions for each platform are on the data deletion page.

The integration for that platform stops working until it can be fixed, and we will say so. Platform APIs are outside our control; this is stated plainly in the terms of service rather than buried.

Publishing through a platform's official content-publishing API, with permission the account holder granted, is a supported use of those APIs. What is not allowed is spam, bulk duplicate posting, impersonation and working around rate limits. Those are prohibited by cometpost's terms as well as by the platforms.