Skip to main content
Rimp enforces a sliding-window rate limit per API key. Limits are tied to your plan.

Default limits

You can have multiple API keys per organization, each with its own rate-limit bucket.

Headers

Every response includes:
X-RateLimit-Reset is a Unix timestamp (seconds) — wait until then to be safe.

429 response

Honor Retry-After (seconds). It’s always smaller than 60 for RPM limits.

Anomaly detection

If your spending in any hour exceeds 10× your weekly hourly average, Rimp pauses new requests for 30 minutes and emits a usage.anomaly_detected webhook to your account. This protects against credential leaks and runaway loops. You’ll see:
To resume immediately, contact support@rimp.example with your request_id.

Raising your limits

  • Pro / Studio: limits raise automatically when you upgrade in /billing.
  • Team: write to sales@rimp.example with your expected RPM and concurrency.
  • Burst handling: we don’t charge for unused capacity — burst-bias your traffic into evening windows if practical.