Skip to main content
Rate limits control the velocity of API usage, protecting against runaway processes and ensuring fair resource distribution across teams.

​
Setting Rate Limits

  1. In your Integration settings, navigate to Workspace Provisioning
  2. Select which workspaces should have access:
    • All Workspaces: Grants access to every workspace in your organisation
    • Specific Workspaces: Choose individual workspaces that need access
  3. Click on the Edit Budget & Rate Limits icon to edit the rate limits for the selected workspace
  4. Set your desired rate Limits
  5. Optionally, Select the Apply to every workspace where this integration is enabled checkbox to apply the same rate limits to all workspaces where this integration is enabled

​
Configuration Options

Limit Types:
  • Request-based: Limit number of API calls (e.g., 1000 requests/minute)
  • Token-based: Limit token consumption rate (e.g., 1M tokens/hour)
Time Windows: Choose from three different time intervals for your rate limits:
  • Per Minute: Limits reset every minute, ideal for fine-grained control
  • Per Hour: Limits reset hourly, providing balanced usage control
  • Per Day: Limits reset daily, suitable for broader usage patterns
Key Considerations for Rate Limits
  • Rate limits can be set as either request-based or token-based
  • Time intervals can be configured as per minute, per hour, or per day
  • Setting the limit to 0 disables the provider
  • Rate limits apply immediately after being set
  • Once set, rate limits cannot be edited by any organisation member
  • Rate limits work for all providers available on the AI Gateway and apply to all organisation members who use the provider
  • After a rate limit is reached, requests will be rejected until the time period resets

​
Use Cases for Rate Limits

  • Cost Control: Prevent unexpected usage spikes that could lead to high costs
  • Performance Management: Ensure your application maintains consistent performance
  • Fairness: Distribute API access fairly across teams or users
  • Security: Mitigate potential abuse or DoS attacks
  • Provider Compliance: Stay within the rate limits imposed by underlying AI providers

​
Exceeding Rate Limits

When a rate limit is reached:
  • Subsequent requests are rejected with a specific error code
  • Error messages clearly indicate that the rate limit has been exceeded
  • The limit automatically resets after the specified time period has elapsed

​
Policy-Based Rate Limits

The limits above are set on an Integration and apply to every provider created from it. For finer control — limits scoped by user, API key, model, provider, or MCP server, in requests or tokens per minute, hour, or day — use a rate limit policy instead. Policies are defined through the Admin API and evaluated per request. See Usage & Rate Limit Policies for the targets, condition keys, and twenty worked examples.
Last modified on September 15, 2026