Rate Limiting

SMO1 uses Redis-based rate limiting to protect the API.

Limits

Rate limit information is included in response headers:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 95
X-RateLimit-Reset: 1704067200

When the rate limit is exceeded, the API returns:

HTTP/1.1 429 Too Many Requests
Retry-After: 3600

{
  "error": "rate limit exceeded",
  "retry_after": 3600
}

Rate limits are per API key or per IP address
Rate limiting requires Redis; if Redis is unavailable, rate limiting is disabled
Different limits may apply per plan tier