Pricing, costs and limits

Plan costs and allowances

Compare the plan price with the work you need to do. Prices are in USD and apply to the selected monthly or yearly subscription. The table and calculator read the plan definitions used by the app. Yearly billing collects the annual total, rather than charging the displayed monthly equivalent each month. The listed plans have unlimited posts.

Writing requests and image credits are separate allowances. They reset with the UTC calendar month, rather than your invoice date. An image uses one image credit and a five-second AI video uses 10 credits. AI generation also needs its provider to be enabled and available; an allowance does not guarantee that a provider can complete a request.

Accounts, people and workspaces

One workspace holds one account on each network. Connecting another account on the same network replaces the network’s connection in the partner workspace. There are 12 supported networks, so a plan’s nominal account cap does not mean you can add more than 12 distinct network connections in one workspace. Choose Agency when you need duplicate networks across brands.

Agency permits unlimited workspaces on one plan. The nominal Agency allowance is up to 100 accounts in each workspace, one per network per workspace. The app checks account usage within each workspace, with no combined cap across all of an owner’s workspaces. Therefore 150 accounts across many workspaces is not an automatic contact-sales case.

Solo has one login seat, including the owner. Team, Studio and Agency have no seat cap. Invites reserve seats while pending, so a full plan cannot add another member by leaving an invitation open. Client approval links require Team or higher. A person can review a client link without creating a login; the link itself grants access to that review.

The calculator asks for total accounts, duplicate networks and people. It picks the least expensive plan that fits a single workspace when that is possible. More than 12 accounts or a duplicate network selects Agency so accounts can be split across workspaces. It is a plan estimate, not a purchase or a reservation of provider capacity.

Uploads and post media

A file uploaded through the Worker has a 95 MiB request limit. The app also supports direct R2 uploads with a maximum announced file size of one GiB, confirmed against the stored object before it becomes ready. Accepted types are JPG, PNG, WebP, GIF, MP4, MOV, WebM and PDF; PDFs are for LinkedIn documents. Network-specific rules still apply after upload.

Post media must match the selected network. The shared validator allows up to 10 images in a post and one video, rejects mixed image/video posts and requires a video for YouTube. Instagram and TikTok require media; Pinterest requires an image. Some formats have stricter provider rules, so a successful upload by itself does not mean a post can be sent.

Per-platform text limits

The table lists the app’s default character limits for the post body. The composer checks each selected account and lets you write a separate version for each one. Some account capabilities override the default, such as a longer X allowance reported by the partner. Titles, first comments, threads and network-specific fields have their own checks in addition to the body limit.

A validation problem returns HTTP 422 before a post is saved for sending. The app shows the reason so you can shorten the text, attach the right media or adjust the network settings. Platforms can also refuse a post after it passes our validation; the app shows the provider’s error and offers retry where the post state permits it.

API, MCP and other request limits

The REST API defaults to 120 requests per minute per workspace and API key or OAuth client on paid plans and 30 without a plan. These defaults are configurable by the operator. MCP allows 120 requests per minute per connected app grant or API key on a paid plan, or 30 without a plan. A parse error also counts toward the MCP limit.

Exceeding the API or MCP pace limit returns HTTP 429 and a Retry-After header. Wait before retrying. A plan or account allowance refusal uses HTTP 402 with an upgrade or plan-required explanation. A missing permission uses HTTP 403. Unsupported file types return HTTP 415, and oversized upload declarations or requests return HTTP 413. These responses do not buy extra capacity.

There can be 20 active API keys and five webhooks in a workspace. Creating keys and webhooks is also paced at 30 per hour, and direct-upload starts at 60 per hour. AI writing has a per-user pace limit in addition to the monthly allowance. Reaching a monthly allowance stops generation with a limit message; it does not add a paid overage to your subscription.

Extra charges and AI availability

There is no metered or usage-based billing in this subscription implementation: nothing is billed beyond the plan price for extra accounts, seats, posts or AI use. Stripe Checkout creates a single subscription line with quantity one. Changing plans or billing periods is a separate billing action; it can affect what is due for that subscription.

AI spending also has server-wide budget guards. A provider outage, missing key or used global budget can pause AI even if your workspace still has allowance left. The app reports when generation is unavailable and uploads remain an alternative. Plan allowances are ceilings for included use, rather than a commitment to buy third-party generation on demand.

Trial, cancel and refunds

The normal checkout offer is a 7-day trial on a paid plan, with a card required and no charge at trial start. Eligibility is checked per workspace, person and normalized email inbox. Trials can be paused by configuration, and a used trial does not reset when you open another workspace. Confirm the offer shown at checkout before starting.

Section 6 of the terms says: “You can cancel at any time. Your access runs to the end of the period you paid for. After that the workspace is read-only: you can sign in, export and delete, and nothing is deleted until you do.” It also says: “We do not refund partial periods, unless the law requires it.”

When a plan ends, the app preserves the workspace but refuses new write activity that needs a plan with HTTP 402. Scheduled posts are held until a plan is active again. Signing in, exporting and deleting remain available. The same happens to workspaces sharing an Agency plan when that covering subscription ends; there is no second hidden subscription for each shared workspace.

Questions