> ## 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. MCP clients sign in with OAuth and need no API key; application code reads CONTEXT_DEV_API_KEY.

# Rate limits

> Pace requests by API key and use the separate organization limits for management APIs.

Core API limits apply per API key in fixed calendar-minute windows. [Plan limits](/account/billing#plan-limits) give the allowance for each plan; Crawl consumes ten units per request.

## Rate limits

| Bucket | Scope | Limit per minute |
| - | - | - |
| Core data APIs | API key | Plan allowance; most calls weigh 1, Crawl weighs 10. |
| Batches | Organization | 1,000 units; submit weighs 50, other calls 1. |
| Monitors | Organization | 1,000 requests. |
| Webhook deliveries | Organization | 600 requests. |
| Request logs | Organization | 60 requests. |
| Agent feedback | Organization | 10 requests. |

Multiple keys share the organization’s balance but have separate core rate windows. Separate management limits still apply across the organization.

## Headers and 429

```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. On a rate-limited request, wait at least `Retry-After` seconds before trying again. Core retry delays range from 1 to 60 seconds.

Use a bounded queue, spread requests through the minute, 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 request-rate limits.