Rate Limits and Quota
Server-side limits enforced per API key and subscription.
The gateway uses Redis for minute-window rate limiting and PostgreSQL for durable quota. Redis never replaces the subscription and usage ledger in PostgreSQL.
Billable paths fail closed when the Redis limiter is unavailable. When quota is exhausted, the backend blocks the request before selecting a provider.
Key points
- Rate limits apply per API key and subscription from the active plan.
- Quota is reserved before dispatch and settled or released from the outcome.
- Internal retry and fallback do not automatically charge the user multiple times.
- Usage and realtime quota screens are views; enforcement always remains in the backend.
- Streaming clients must bound total bytes, event and buffer sizes, and accumulated output.