> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/start-with-an-ai-agent/llm/limits.md).

# Plan and request limits

Distinguish plan defaults, account-specific contact limits, upload constraints, and API request rate limits.

Compact reference for agents making REST requests. All endpoint paths below are relative to `https://backend.blotato.com/v2`. For task instructions, read the [workflow guide](/api-and-mcp-concepts/rate-limits.md). For tool calls, use the [MCP reference](/start-with-an-ai-agent/mcp/tools.md).

## Plan limits

```
Blotato has 3 plans (starter, creator, agency). Plan defaults:

                               starter    creator    agency
Max connected social accounts  20         40         100
Max media upload size          400 MB     1 GB       1 GB
Queued scheduled posts         200        1000       3000
Scheduling horizon (months)    9          9          9
Active contacts per month      1,000      6,000      15,000
Analytics metric fields        25         all        all
Analytics checkpoints/post     4          18         20
Analytics collection window    30 days    30 days    90 days

Active contacts are unique per connected social account. The same person reached through 2 connected Facebook Pages counts as 2 active contacts. Reaching the same person again through the same connected account during the monthly window does not add another contact.

GET /users/me/usage returns accounts, contacts, and contactsLimit. contactsLimit is an integer or "unlimited". Use contactsLimit as the user's current monthly active-contact limit, not the connected-account cap. Some accounts have a custom monthly active-contact limit.

The scheduling horizon is 9 months on EVERY plan. It does not scale with the plan.

A DM sent by a DM automation counts toward active contacts like any other send.

Facebook Pages and LinkedIn Company Pages count toward the cap.
* Facebook: The personal Facebook login is the required OAuth parent for its Pages. It must remain connected while those Pages are connected. Disconnecting the login removes every Page authorized through it. The login does not count toward the cap. Each connected Page counts as one account.
* LinkedIn: Each profile and each connected company Page each count as one account.

Plan validation might reject submission before background work starts. A successful
create response is not proof of completion. Follow the operation-specific status
endpoint and report its error when processing fails.
```

## Rate limits

```
POST /posts:                    30 requests / minute
GET  /posts/:id:                60 requests / minute
POST /videos/from-templates:    30 requests / minute
POST /source-resolutions-v3:    30 requests / minute
GET  /source-resolutions-v3/:id: 60 requests / minute
POST /media:                    30 requests / minute
POST /media/uploads:            120 requests / minute

429 response means rate limit exceeded. Check "message" for retry timing.
```

Plan upload limits do not replace the target platform's file restrictions. A rate-limit response does not establish whether an earlier write succeeded. Follow [rate-limit recovery](/api-and-mcp-concepts/rate-limits.md) and look up existing submission IDs before repeating a create request. See [billing and credits](/settings/billing-and-credits.md#plan-limits) for plan details.

Return to the [agent reference index](/start-with-an-ai-agent/llm.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/start-with-an-ai-agent/llm/limits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.