quotas & limits

12 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Management API standard rate limit

The Management API applies a standard rate limit of 120 requests per 1 minute, per user, per project/organization. When exceeded, all subsequent API calls return a 429 Too Many Requests response for the remainder of the minute. The quota resets when the time window expires.

Rate limit scope isolation

Rate limits are applied with per-user plus per-scope isolation. Project scope means rate limits apply independently to each project, so requests to Project A do not count toward the limit of Project B. Organization scope means rate limits apply independently to each organization. A user can make 120 requests to Project A and 120 requests to Project B within the same minute without hitting rate limits.

Rate limit response headers

Every Management API response includes three rate limit headers: X-RateLimit-Limit shows the maximum number of requests allowed in the current time window; X-RateLimit-Remaining shows the number of requests remaining before hitting the rate limit; X-RateLimit-Reset shows the number of seconds remaining until the rate limit resets.

Rate limit tracking identifiers

Requests are identified and tracked in this order of priority: OAuth App ID if authenticated via an OAuth application; User ID if authenticated with a personal access token; IP Address if unauthenticated. Each identifier is combined with the scope (project or organization) to create a unique tracking key.

Management API endpoint rate limit exceptions

The following endpoints have stricter rate limits than the standard 120 requests per minute: GET /v1/projects/:ref/endpoints/logs.all (30 requests per 1 minute) for analytics log queries; GET /v1/projects/:ref/endpoints/usage.api-counts (30 requests per 1 minute) for analytics aggregation; GET /v1/projects/:ref/endpoints/usage.api-requests-count (30 requests per 1 minute) for analytics aggregation; GET /v1/projects/:ref/database/context (10 requests per 1 minute and 1 request per 1 second burst limit) for database context operations; POST /v1/projects/:ref/config/custom-hostname/initialize (10 requests per 1 minute); POST /v1/projects/:ref/config/custom-hostname/reverify (10 requests per 1 minute); DELETE /v1/projects/:ref/config/custom-hostname (10 requests per 1 minute); GET /v1/projects/:ref/config/vanity-subdomain (10 requests per 1 minute). POST /v1/projects/:ref/database/migrations has 120 requests per 3 minutes.

Database context dual rate limiting

The GET /v1/projects/:ref/database/context endpoint has dual rate limiting: up to 10 requests per minute and no more than 1 request per second. This dual limit prevents both sustained high volume and burst traffic.

Rate limit best practices

Monitor the X-RateLimit-Remaining header to see how many requests remain, and slow down when it approaches 0. Implement exponential backoff when receiving a 429 response, using the X-RateLimit-Reset header to determine wait duration. Batch operations to combine multiple requests into fewer API calls. Use caution with expensive endpoints like analytics, database context, and domain endpoints which have stricter limits.

Quota overage billing on paid plans

If you are on a paid plan and have Spend Cap disabled or your organization is on Team Plan or above, you will pay for any overages beyond your quota limits.

Quota overage grace period on Free Plan or with Spend Cap enabled

When you exceed your quotas while on a Free Plan or with Spend Cap enabled, you will receive a notification to your billing email address and be placed under a grace period. Refer to the Fair Use Policy for more details.

Realtime peak connections pricing and quotas

Realtime peak connections cost $10 per 1,000 peak connections for usage exceeding the subscription plan's quota. The Free plan includes 200 peak connections with no overage charges. The Pro plan includes 500 peak connections and charges $10 per 1,000 peak connections for usage above the quota. The Team plan includes 500 peak connections and charges $10 per 1,000 peak connections for usage above the quota. The Enterprise plan has custom quotas and custom pricing.

Realtime messages pricing per million

Realtime messages cost $2.50 per 1 million messages for over-usage charges. Users are only charged for usage exceeding their subscription plan's quota.

Realtime messages quota by plan

Free plan includes 2 million messages per month. Pro plan includes 5 million messages per month with $2.50 per 1 million messages over-usage charge. Team plan includes 5 million messages per month with $2.50 per 1 million messages over-usage charge. Enterprise plan has custom quota and custom over-usage pricing.

Give your agent this brain