Skip to content

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs(rate-limits): consolidate into the reference page, drop the duplicate /docs guide

Palash Kala6a3b76039069
diff --git a/docs/content/docs/meta.json b/docs/content/docs/meta.json
index b7055a1b3..57f4b8b03 100644
--- a/docs/content/docs/meta.json
+++ b/docs/content/docs/meta.json
@@ -32,7 +32,6 @@
"proxy-execute",
"projects",
"observability",
- "rate-limits",
"signing-up-as-an-agent",
"common-faq",
"glossary",
diff --git a/docs/content/docs/rate-limits.mdx b/docs/content/docs/rate-limits.mdx
deleted file mode 100644
index 1e6e4775c..000000000
--- a/docs/content/docs/rate-limits.mdx
+++ /dev/null
@@ -1,105 +0,0 @@
----
-title: Rate limits & usage
-description: How Composio's API rate limits work, the headers to read, how to handle 429s, how upstream provider limits differ, and what to do for high-volume multi-tenant usage.
-keywords: [rate limit, rate limits, "429", too many requests, retry-after, x-ratelimit, throttling, quota, suspension, account suspended, abuse, high volume, multi-tenant, sla, status]
----
-
-There are **two independent kinds of rate limit** when you use Composio, and most confusion comes from mixing them up:
-
-1. **Composio platform limits**: how many requests your organization can make to the Composio API per minute.
-2. **Upstream provider limits**: limits the *external* service (Gmail, Slack, Google Ads, etc.) enforces on the calls Composio makes on your behalf.
-
-This page covers both, plus how to handle `429`s and what to do for high-volume, multi-tenant workloads.
-
-## Composio platform rate limits
-
-Composio limits are applied **per organization**, on a **fixed one-minute window**, shared across all of your `userId`s, API keys, and endpoints (tool execution, connected accounts, triggers). The window resets at the start of each minute.
-
-### Read your limit from the response headers
-
-Your live limit is always returned on **every** response, so you never have to hardcode a number:
-
-| Header | Meaning |
-| --- | --- |
-| `X-RateLimit` | Your current request limit for the window |
-| `X-RateLimit-Remaining` | Requests remaining in the current window |
-| `X-RateLimit-Window-Size` | Window length, e.g. `60s` |
-
-Treat these headers as the source of truth and drive your client off them.
-
-### Default limits by plan
-
-These are the current **default** per-organization, per-minute ceilings. Your authoritative value is always `X-RateLimit` (limits can be raised for an account), but as an anchor for planning:
-
-| Plan | Requests per minute (per org) |
-| --- | --- |
-| Hobby / Starter | 2,000 |
-| Growth | 10,000 |
-| Enterprise | Custom |
-
-### When you exceed the limit
-
-You get an **HTTP `429`** with a `Retry-After` header (seconds until the window resets):
-
-```json
-{ "message": "Rate limit exceeded. Limit: 2000 requests per 1 minutes" }
-```
-
-A `429` is a **throttle, not a cutoff**. The window auto-resets the next minute and you can continue, and nothing about your account changes.
-
-### Will I get suspended for going over?
-
-<Callout type="info">
-**No.** Composio does **not** automatically suspend, review, or restrict accounts based on request volume, concurrency, or error rates. Exceeding your limit only returns `429` throttling that clears on the next minute. There is no automated abuse trigger and no separate "account review" process.
-</Callout>
-
-The only hard block is a **manual** action by our team in rare cases (e.g. confirmed abuse). If that ever happens you'll receive an **HTTP `403`** with `Organization temporarily blocked. Please contact technical support.` It is never automatic, and support is the path to resolve it.
-
-### Handling 429s
-
-A small, well-behaved retry loop is all you need:
-
-- **Honor `Retry-After` first.** If it's present, wait that many seconds.
-- Otherwise wait for the window to roll over (`X-RateLimit-Window-Size`).
-- Otherwise fall back to **exponential backoff with jitter**, and cap retries (e.g. 5) before surfacing an error.
-- Watch `X-RateLimit-Remaining` and slow down *before* you hit zero.
-
-```python
-import time, random
-
-def with_backoff(make_request, max_retries=5):
- for attempt in range(max_retries):
- resp = make_request()
- if resp.status_code != 429:
- return resp
- retry_after = resp.headers.get("Retry-After")
- delay = float(retry_after) if retry_after else min(2 ** attempt, 30) + random.random()
- time.sleep(delay)
- raise RuntimeError("Composio rate limit: retries exhausted")
-```
-
-Other good practices: cache tool definitions and other static data, batch where you can, and avoid tight polling loops.
-
-## Upstream provider rate limits
-
-These are **separate** from Composio's limits. When Composio calls Gmail, Slack, Google Ads, etc. on your behalf, that provider enforces *its own* limits and can return `429` / `RESOURCE_EXHAUSTED`. Composio surfaces those errors back to you.
-
-The most common cause of provider `429`s in production is **Composio's shared managed auth**: many organizations connect through the same shared OAuth app, so you share that app's rate-limit bucket with everyone else (Slack in particular throttles non-Marketplace apps aggressively).
-
-<Callout type="warn">
-For production and high-volume workloads, use **your own OAuth app** via a [custom auth config](/docs/custom-app-vs-managed-app) instead of Composio-managed auth. Your own app gets its own isolated bucket and the provider's full per-app limits. Managed auth is best for development and prototyping.
-</Callout>
-
-## High-volume and multi-tenant usage
-
-If you run a multi-tenant app, the recommended pattern is **one Composio account with a unique `userId` per end-user**, exactly the single-key fan-out many teams already use. You do **not** need per-tenant sub-accounts; that adds complexity without raising your limit.
-
-To scale throughput, **move to a higher plan** (which raises your per-org limit) and use your own OAuth apps for the providers you call heavily, rather than splitting into multiple accounts.
-
-## Need a higher limit?
-
-Per-organization limits can be raised. If you're approaching your ceiling, [reach out](https://calendly.com/composiohq/enterprise) and we'll find the right limit for your workload. Custom, higher-volume limits come with the Enterprise plan.
-
-## Reliability & SLA
-
-A formal uptime SLA, support-response commitments, and a dedicated escalation contact are part of the **Enterprise** plan; [talk to us](https://calendly.com/composiohq/enterprise) if you need them. For security and compliance details, see [trust.composio.dev](https://trust.composio.dev).
diff --git a/docs/content/reference/rate-limits.mdx b/docs/content/reference/rate-limits.mdx
index aeef66756..73769a3a7 100644
--- a/docs/content/reference/rate-limits.mdx
+++ b/docs/content/reference/rate-limits.mdx
@@ -1,12 +1,17 @@
---
title: Rate Limits
-description: Composio API rate limits by plan, rate limit headers, and best practices
-keywords: [API rate limits, rate limiting, throttling, 429 too many requests, API quotas, request limits]
+description: Composio API rate limits by plan, the headers to read, how to handle 429s, and how upstream provider limits differ
+keywords: [API rate limits, rate limiting, throttling, 429 too many requests, API quotas, request limits, suspension, multi-tenant, retry-after, x-ratelimit]
---
-Rate limits are enforced **per organization** on a fixed one-minute window (aligned to the start of each minute). Your live limit is always returned in the `X-RateLimit` header; the table below lists the current defaults.
+There are two independent kinds of rate limit when you use Composio:
-## Rate limits by plan
+1. **Composio platform limits**: how many requests your organization can make to the Composio API per minute.
+2. **Upstream provider limits**: limits the external service (Gmail, Slack, Google Ads, etc.) enforces on the calls Composio makes on your behalf.
+
+## Composio platform limits
+
+Rate limits are enforced **per organization** on a fixed one-minute window (aligned to the start of each minute), shared across all of your `userId`s, API keys, and endpoints. Your live limit is always returned in the `X-RateLimit` header; the table below lists the current defaults.
| Plan | Rate Limit | Window |
|------|------------|--------|
@@ -19,9 +24,9 @@ Rate limits are enforced **per organization** on a fixed one-minute window (alig
All authenticated API endpoints share your organization's rate limit. This includes tool execution, connected accounts, triggers, and all other API operations.
</Callout>
-## Rate limit headers
+### Rate limit headers
-API responses include headers to help you track your usage:
+Every response includes headers, so you never have to hardcode a number:
| Header | Description |
|--------|-------------|
@@ -30,9 +35,11 @@ API responses include headers to help you track your usage:
| `X-RateLimit-Window-Size` | Window size (e.g., `60s` for 60 seconds) |
| `Retry-After` | Seconds until the window resets (only on 429 responses) |
-## Rate limit response
+Treat these as the source of truth and drive your client off them.
-When you exceed the rate limit, you'll receive a `429 Too Many Requests` response:
+### When you exceed the limit
+
+You get an `HTTP 429 Too Many Requests` with a `Retry-After` header:
```json
{
@@ -40,17 +47,53 @@ When you exceed the rate limit, you'll receive a `429 Too Many Requests` respons
}
```
-## Best practices
+A `429` is a throttle, not a cutoff. The window auto-resets the next minute and you can continue; nothing about your account changes.
+
+### Will I get suspended for going over?
+
+<Callout type="info">
+**No.** Composio does not automatically suspend, review, or restrict accounts based on request volume, concurrency, or error rate. Exceeding your limit only returns `429` throttling that clears on the next minute. There is no automated abuse trigger.
+</Callout>
+
+The only hard block is a manual action by our team in rare cases (e.g. confirmed abuse), which returns `HTTP 403` with `Organization temporarily blocked. Please contact technical support.` It is never automatic, and support is the path to resolve it.
+
+### Handling 429s
+
+- Honor `Retry-After` first; otherwise wait for the window (`X-RateLimit-Window-Size`); otherwise fall back to exponential backoff with jitter, capping retries (e.g. 5) before surfacing an error.
+- Watch `X-RateLimit-Remaining` and slow down before you hit zero.
+- Cache tool definitions and other static data, batch where you can, and avoid tight polling loops.
+
+```python
+import time, random
+
+def with_backoff(make_request, max_retries=5):
+ for attempt in range(max_retries):
+ resp = make_request()
+ if resp.status_code != 429:
+ return resp
+ retry_after = resp.headers.get("Retry-After")
+ delay = float(retry_after) if retry_after else min(2 ** attempt, 30) + random.random()
+ time.sleep(delay)
+ raise RuntimeError("Composio rate limit: retries exhausted")
+```
+
+## Upstream provider limits
+
+These are separate from Composio's limits. When Composio calls Gmail, Slack, Google Ads, etc. on your behalf, that provider enforces its own limits and can return `429` / `RESOURCE_EXHAUSTED`, which Composio surfaces back to you.
-1. **Monitor your usage** - Check the `X-RateLimit-Remaining` header to track how close you are to the limit.
+The most common cause in production is **Composio's shared managed auth**: many organizations connect through the same shared OAuth app, so you share that app's rate-limit bucket (Slack in particular throttles non-Marketplace apps aggressively).
+
+<Callout type="warn">
+For production and high-volume workloads, use your own OAuth app via a [custom auth config](/docs/custom-app-vs-managed-app) instead of Composio-managed auth. Your own app gets its own isolated bucket and the provider's full per-app limits. Managed auth is best for development and prototyping.
+</Callout>
-2. **Implement backoff** - When you receive a `429`, wait for the duration specified in `Retry-After` before retrying.
+## High-volume and multi-tenant usage
-3. **Cache responses** - Cache tool definitions and other static data to reduce unnecessary API calls.
+For multi-tenant apps, the recommended pattern is one Composio account with a unique `userId` per end-user. You do not need per-tenant sub-accounts. To scale throughput, move to a higher plan (which raises your per-org limit) and use your own OAuth apps for the providers you call heavily.
## Need higher limits?
-If you're hitting rate limits regularly, consider upgrading your plan or [talk to us](https://calendly.com/composiohq/enterprise) to discuss custom limits for your use case.
+If you're hitting rate limits regularly, [talk to us](https://calendly.com/composiohq/enterprise) to discuss custom limits for your use case. Custom, higher-volume limits come with the Enterprise plan.
<Cards>
<Card title="Errors" href="/reference/errors">
diff --git a/docs/content/reference/v3/rate-limits.mdx b/docs/content/reference/v3/rate-limits.mdx
index 3dc3ab871..f7d5604b9 100644
--- a/docs/content/reference/v3/rate-limits.mdx
+++ b/docs/content/reference/v3/rate-limits.mdx
@@ -1,12 +1,17 @@
---
title: Rate Limits
-description: Composio API rate limits by plan, rate limit headers, and best practices
-keywords: [API rate limits, rate limiting, throttling, 429 too many requests, API quotas, request limits]
+description: Composio API rate limits by plan, the headers to read, how to handle 429s, and how upstream provider limits differ
+keywords: [API rate limits, rate limiting, throttling, 429 too many requests, API quotas, request limits, suspension, multi-tenant, retry-after, x-ratelimit]
---
-Rate limits are enforced **per organization** on a fixed one-minute window (aligned to the start of each minute). Your live limit is always returned in the `X-RateLimit` header; the table below lists the current defaults.
+There are two independent kinds of rate limit when you use Composio:
-## Rate limits by plan
+1. **Composio platform limits**: how many requests your organization can make to the Composio API per minute.
+2. **Upstream provider limits**: limits the external service (Gmail, Slack, Google Ads, etc.) enforces on the calls Composio makes on your behalf.
+
+## Composio platform limits
+
+Rate limits are enforced **per organization** on a fixed one-minute window (aligned to the start of each minute), shared across all of your `userId`s, API keys, and endpoints. Your live limit is always returned in the `X-RateLimit` header; the table below lists the current defaults.
| Plan | Rate Limit | Window |
|------|------------|--------|
@@ -19,9 +24,9 @@ Rate limits are enforced **per organization** on a fixed one-minute window (alig
All authenticated API endpoints share your organization's rate limit. This includes tool execution, connected accounts, triggers, and all other API operations.
</Callout>
-## Rate limit headers
+### Rate limit headers
-API responses include headers to help you track your usage:
+Every response includes headers, so you never have to hardcode a number:
| Header | Description |
|--------|-------------|
@@ -30,9 +35,11 @@ API responses include headers to help you track your usage:
| `X-RateLimit-Window-Size` | Window size (e.g., `60s` for 60 seconds) |
| `Retry-After` | Seconds until the window resets (only on 429 responses) |
-## Rate limit response
+Treat these as the source of truth and drive your client off them.
-When you exceed the rate limit, you'll receive a `429 Too Many Requests` response:
+### When you exceed the limit
+
+You get an `HTTP 429 Too Many Requests` with a `Retry-After` header:
```json
{
@@ -40,17 +47,53 @@ When you exceed the rate limit, you'll receive a `429 Too Many Requests` respons
}
```
-## Best practices
+A `429` is a throttle, not a cutoff. The window auto-resets the next minute and you can continue; nothing about your account changes.
+
+### Will I get suspended for going over?
+
+<Callout type="info">
+**No.** Composio does not automatically suspend, review, or restrict accounts based on request volume, concurrency, or error rate. Exceeding your limit only returns `429` throttling that clears on the next minute. There is no automated abuse trigger.
+</Callout>
+
+The only hard block is a manual action by our team in rare cases (e.g. confirmed abuse), which returns `HTTP 403` with `Organization temporarily blocked. Please contact technical support.` It is never automatic, and support is the path to resolve it.
+
+### Handling 429s
+
+- Honor `Retry-After` first; otherwise wait for the window (`X-RateLimit-Window-Size`); otherwise fall back to exponential backoff with jitter, capping retries (e.g. 5) before surfacing an error.
+- Watch `X-RateLimit-Remaining` and slow down before you hit zero.
+- Cache tool definitions and other static data, batch where you can, and avoid tight polling loops.
+
+```python
+import time, random
+
+def with_backoff(make_request, max_retries=5):
+ for attempt in range(max_retries):
+ resp = make_request()
+ if resp.status_code != 429:
+ return resp
+ retry_after = resp.headers.get("Retry-After")
+ delay = float(retry_after) if retry_after else min(2 ** attempt, 30) + random.random()
+ time.sleep(delay)
+ raise RuntimeError("Composio rate limit: retries exhausted")
+```
+
+## Upstream provider limits
+
+These are separate from Composio's limits. When Composio calls Gmail, Slack, Google Ads, etc. on your behalf, that provider enforces its own limits and can return `429` / `RESOURCE_EXHAUSTED`, which Composio surfaces back to you.
-1. **Monitor your usage** - Check the `X-RateLimit-Remaining` header to track how close you are to the limit.
+The most common cause in production is **Composio's shared managed auth**: many organizations connect through the same shared OAuth app, so you share that app's rate-limit bucket (Slack in particular throttles non-Marketplace apps aggressively).
+
+<Callout type="warn">
+For production and high-volume workloads, use your own OAuth app via a [custom auth config](/docs/custom-app-vs-managed-app) instead of Composio-managed auth. Your own app gets its own isolated bucket and the provider's full per-app limits. Managed auth is best for development and prototyping.
+</Callout>
-2. **Implement backoff** - When you receive a `429`, wait for the duration specified in `Retry-After` before retrying.
+## High-volume and multi-tenant usage
-3. **Cache responses** - Cache tool definitions and other static data to reduce unnecessary API calls.
+For multi-tenant apps, the recommended pattern is one Composio account with a unique `userId` per end-user. You do not need per-tenant sub-accounts. To scale throughput, move to a higher plan (which raises your per-org limit) and use your own OAuth apps for the providers you call heavily.
## Need higher limits?
-If you're hitting rate limits regularly, consider upgrading your plan or [talk to us](https://calendly.com/composiohq/enterprise) to discuss custom limits for your use case.
+If you're hitting rate limits regularly, [talk to us](https://calendly.com/composiohq/enterprise) to discuss custom limits for your use case. Custom, higher-volume limits come with the Enterprise plan.
<Cards>
<Card title="Errors" href="/reference/v3/errors">