API

Rate limits and quotas

RTIE enforces tenant-level monthly request quotas on authenticated /v1 API routes. Edge rate limiting may also protect public surfaces during traffic spikes.

Plan quotas

429 response

When a tenant exceeds its quota, RTIE returns 429 with usage details. Clients should stop high-volume retries, wait for the next quota window, or route the operator to a plan upgrade.

{
  "error": "quota_exceeded",
  "message": "Monthly request quota exceeded.",
  "used": 10000,
  "limit": 10000
}

Client guidance

• Use exponential backoff for transient 429, 500, 502, and 503 responses.
• Do not retry non-idempotent writes unless your integration supplies its own idempotency key or dedupe guard.
• Subscribe through webhooks or MCP tool responses instead of polling high-volume session state.
• Contact dev@rtie.ai for enterprise quota planning before launch traffic tests.