Rate limits

Sandbox rate limits use token buckets keyed by account and policy per server process. Multiple instances each grant an allowance; these numbers are not a fleet-wide quota. Live-mode limits and sessions are not available. Do not build against a promised live rate.

Current sandbox limits

Calls	Allowance per process
Checks (`POST /v1/checks`)	20 per second
Generations (`POST /v1/generations`)	5 per second
Other authenticated operations	5 per second
Public receipt reads	10 per minute per IP address

Short bursts are absorbed until the bucket is empty. Test verification requires a key.

Headers

Every response carries the IETF RateLimit-Policy and RateLimit header fields for the limit the call counted against:

HTTP/1.1 200 OK
Request-Id: req_8f2k4m6p8r0t2v4x6z8b0d2f4h
RateLimit-Policy: "checks";q=20;w=1
RateLimit: "checks";r=18;t=1

Field	Parameter	Meaning
`RateLimit-Policy`	`q`	The quota: requests allowed per window.
`RateLimit-Policy`	`w`	The window, in seconds.
`RateLimit`	`r`	Requests remaining in the current window.
`RateLimit`	`t`	Seconds until the quota resets.

The supported policy names are checks, generations and default.

When you exceed a limit

The call fails with 429 rate_limited and a Retry-After header in seconds. Nothing ran: no check was decided and no object was created.

HTTP/1.1 429 Too Many Requests
Content-Type: application/problem+json
Retry-After: 1

{
  "type": "https://docs.reflections.ai/errors/rate_limited",
  "title": "Too many requests",
  "status": 429,
  "code": "rate_limited",
  "request_id": "req_8f2k4m6p8r0t2v4x6z8b0d2f4h"
}

Wait Retry-After seconds, then retry with the same Idempotency-Key. The retry function in Idempotency does both. Sessions are planned and cannot be used yet.

A 429 on a check is not permission. Do not generate a named talent until a retry returns allow.

Stay under the limits

Read RateLimit and slow down before r reaches zero.
Retry unknown outcomes with the same persisted Idempotency-Key and body.
Poll an escalated check or asynchronous generation no faster than once every five seconds.
Webhooks, the name index and usage batching remain planned; they are not current alternatives to polling.

Service status is at status.reflections.ai. Rate-limit increases and production capacity require an explicit service agreement; they are not self-service features.

Errors

Every error code and what to do.

Caching and outages

Reuse windows, the revocation feed and retries.

Overview

Account

Talent

Facets

Resolutions

Licenses

License requests

Connections

Files

Checks

Generations

Sessions

Receipts

Verifications

Revocations

Usage records

Statements

Mandates

Escalations

License drafts

Webhook endpoints

Events

Discovery

OAuth

Test helpers

Webhooks

Real-time

Formats

MCP

Current sandbox limits

Headers

When you exceed a limit

Stay under the limits

Errors

Caching and outages

​Current sandbox limits

​Headers

​When you exceed a limit

​Stay under the limits

​Related

Errors

Caching and outages

Current sandbox limits

Headers

When you exceed a limit

Stay under the limits

Related