> ## Documentation Index
> Fetch the complete documentation index at: https://docs.context.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Setting up Context.dev for a user? Follow https://docs.context.dev/agent-quickstart.md. Start by signing the user up and getting an API key through https://www.context.dev/auth.md; application code reads CONTEXT_DEV_API_KEY.

# Rate limits

> Stay within your plan's concurrency limit and the separate organization limits for management APIs.

Core API limits cap how many requests your organization can have in flight at once. [Plan limits](/account/billing#plan-limits) give the concurrency for each plan. Organizations created before concurrency limits keep per-minute limits per API key; the dashboard shows which limit applies to you.

## Rate limits

| Bucket | Scope | Limit |
| - | - | - |
| Core data APIs | Organization | Plan concurrency; each in-flight request uses one slot until its response finishes. |
| Core data APIs on per-minute plans | API key | Plan allowance per minute; most calls weigh 1, Crawl weighs 10. |
| Batches | Organization | 1,000 units per minute; submit weighs 50, other calls 1. |
| Monitors | Organization | 1,000 requests per minute. |
| Webhook deliveries | Organization | 600 requests per minute. |
| Request logs | Organization | 60 requests per minute. |
| Agent feedback | Organization | 10 requests per minute. |

All keys in an organization share its concurrency limit and credit balance. On per-minute plans, each key has its own core rate window. Management limits apply across the organization on every plan.

## Headers and 429

A request that arrives while every concurrency slot is in use returns `429` with these headers:

```text theme={null}
X-RateLimit-Limit: 10
X-RateLimit-Remaining: 0
X-RateLimit-Mode: concurrency
Retry-After: 1
```

Wait for one of your in-flight requests to finish, or at least `Retry-After` seconds, before trying again.

On per-minute plans, a rate-limited request returns:

```text theme={null}
X-RateLimit-Limit: 200
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1790470860
Retry-After: 12
```

`X-RateLimit-Reset` is a Unix timestamp in seconds. Per-minute retry delays range from 1 to 60 seconds.

Size your worker pool to your concurrency limit, and add jitter to retries. Missing or invalid credentials can also trigger authentication protection; fix credentials instead of increasing retry traffic.

Concurrency caps for [batches](/batches/limits-and-errors) and the number of [monitors](/monitors/limits-and-errors) are separate from these request limits.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.