What is SkedCast’s API rate limit?

Unless your plan sets a different value, the default is 120 requests per minute for the public /v1 REST API, counted per API key or connected OAuth app.

What is the rate limit for the MCP server?

The default MCP budget is 60 requests per minute per connected client, with a separate, tighter 10-per-minute budget for destructive tools such as delete, cancel and the batch-undo tool.

How does a batch request count against the rate limit?

A single request costs 1 unit, but a batch request costs one unit per item it contains — scheduling 20 posts in one batch call uses 20 units of that minute’s budget.

What happens when you exceed the rate limit?

The request is refused with a 429 status and a Retry-After header stating how many seconds to wait before trying again; the response also names which specific budget was exhausted.

How do I see my current rate limit usage?

Every response carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, so your own integration can track its budget without a separate call, and connected-app usage is also visible from the workspace’s own settings.

Can my rate limit be higher than the default?

Yes — the per-minute budgets are set per plan, so a workspace on a higher plan, or with a specific limit configured for a connected app, can have a higher ceiling than the default.

Where can I read the full API reference?

SkedCast’s developer documentation covers the full REST and MCP reference, authentication, and every endpoint in detail beyond what this rate-limit summary covers.

Free tool

API rate limit lookup (SkedCast, not Instagram)

This page covers SkedCast's own default rate limits for its public REST API and MCP server — it is not a lookup for Instagram API rate limits, which Meta sets and documents separately for its own Graph API. Use it to read your usage and handle a 429 in your own integration.

SkedCast's API rate limits (not Instagram's)

Public REST API (/v1)

Per API key or connected OAuth app, unless your plan sets a different value

120 requests / minute

MCP server

Per connected MCP client (one total budget, all tools)

60 requests / minute

Destructive MCP tools

Delete, cancel and the batch-undo tool — a tighter slice of the MCP budget above

10 requests / minute

Every response carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers. A refused request returns 429 with a Retry-After header (seconds). For the full endpoint reference, authentication and everything beyond rate limits, see the developer documentation. Instagram's own Graph API enforces its own separate rate limits, set and documented by Meta — not the numbers on this page.

How to read your own rate limit

Check the response headers. Every SkedCast API and MCP response includes RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, so you can see your budget on every call.
Know which budget you are drawing from. REST calls through /v1 draw on the API budget, while MCP tool calls draw on a separate MCP budget, and a handful of destructive MCP tools share an even tighter one.
Handle a 429 with backoff, not a retry loop. A refused request returns 429 with a Retry-After header in seconds — wait at least that long before trying again rather than retrying immediately.
Batch where the API supports it. A batch request still costs one unit per item it contains, so batching does not bypass the limit, but it does cut the number of round trips your integration needs.
Ask about a higher limit if you are hitting the ceiling. Plans can set a different requests-per-minute value than the default, so a consistently full budget is worth raising with SkedCast rather than working around.

Worked examples

A workspace on the default plan limit

A workspace with no custom rate-limit override draws on the default 120 requests per minute for /v1 and 60 per minute for MCP — most single-app integrations stay well under both.

A batch of 40 posts in one request

Scheduling 40 posts through one batch endpoint call still costs 40 units against the per-minute budget, not 1 — the batch saves round trips, not rate-limit budget.

A delete tool hitting its own ceiling

An MCP client calling the delete or cancel tool 11 times in one minute hits the separate 10-per-minute destructive-action budget on the 11th call, even if its general MCP budget still has room.

API rate limit FAQ

What is SkedCast’s API rate limit?: Unless your plan sets a different value, the default is 120 requests per minute for the public /v1 REST API, counted per API key or connected OAuth app.
What is the rate limit for the MCP server?: The default MCP budget is 60 requests per minute per connected client, with a separate, tighter 10-per-minute budget for destructive tools such as delete, cancel and the batch-undo tool.
How does a batch request count against the rate limit?: A single request costs 1 unit, but a batch request costs one unit per item it contains — scheduling 20 posts in one batch call uses 20 units of that minute’s budget.
What happens when you exceed the rate limit?: The request is refused with a 429 status and a Retry-After header stating how many seconds to wait before trying again; the response also names which specific budget was exhausted.
How do I see my current rate limit usage?: Every response carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, so your own integration can track its budget without a separate call, and connected-app usage is also visible from the workspace’s own settings.
Can my rate limit be higher than the default?: Yes — the per-minute budgets are set per plan, so a workspace on a higher plan, or with a specific limit configured for a connected app, can have a higher ceiling than the default.
Where can I read the full API reference?: SkedCast’s developer documentation covers the full REST and MCP reference, authentication, and every endpoint in detail beyond what this rate-limit summary covers.

Ready to broadcast everywhere?

Sign up free — no credit card. You land on the Free plan, and you can start a one-time 7-day Studio trial from your workspace whenever you are ready. Connect your first accounts, import a batch, and watch one post fan out across every platform.

Start free Log in to your console