Skip to main content
The Autousers API enforces two limits independently:
  1. RPM — a sliding-window cap on requests per minute, per team.
  2. Monthly quotas — counts of autouser ratings, human ratings, and evaluations created per team per billing period.
Both are tied to your subscription plan.
Beta status (2026-05-04): tier-aware RPM and monthly quota enforcement is rolling out. During beta, the server logs every over-limit request with its X-Request-Id but does not yet block. The X-RateLimit-* headers are populated on a best-effort basis. Watch the Changelog for the flip-the-switch announcement before you rely on these limits in production. Build to the contract below now; nothing changes when enforcement lands.

Per-plan limits

These mirror the pricing page exactly. Limits apply to the team the API key is bound to, not the user. Multiple keys on one team share the same budget.

Response headers

Every /v1 response carries: Read these on every response — not just 429s. Throttling proactively is cheaper than retrying.

The 429 response

Monthly-quota exhaustion uses code: quota_exceeded and does not carry Retry-After — the quota resets at the start of the next billing period (visible at GET /v1/usage).

Self-throttling

Call GET /v1/usage to read the team’s plan and remaining budget without firing a real workload request:

Exponential backoff with jitter

Treat 429 and 5xx as retryable. Cap at 5 attempts; add jitter so retries don’t synchronise across replicas.

Limits on specific routes

A handful of routes have stricter per-user limits independent of plan tier: These are documented per-route in the API reference.

What does not count

  • GET /v1/auth/whoami — free, unmetered, ping anytime.
  • GET /v1/usage — free, unmetered.
  • Webhook deliveries (us → you). Your endpoint receiving a webhook is not a request you made; it doesn’t consume RPM.

Enterprise

Custom RPM, unmetered monthly quotas, and dedicated capacity are available on Enterprise. Contact sales@autousers.ai.