--- title: Rate Limits description: Configure rate-limits for your project. --- Agentic's durable rate-limiting is built on top of Cloudflare's global infrastructure. Customize the default rate-limits, change them based on a customer's pricing plan, or create custom tool-specific overrides. ## Rate Limit Whether or not this rate limit is enabled. The interval at which the rate limit is applied. Either a positive integer expressed in seconds or a valid positive [ms](https://github.com/vercel/ms) string (eg, `10s`, `1m`, `8h`, `2d`, `1w`, `1y`, etc). The maximum number of API requests per interval (unitless). How to enforce the rate limit: `strict` (more precise but slower) or `approximate` (the default; faster and asynchronous but less precise). The default rate-limiting mode is `approximate`, which means that requests are allowed to proceed immediately, with the limit being enforced asynchronously in the background. This is faster than `strict` mode, but it is less consistent if precise adherence to rate-limits is required. With `strict` mode, customer requests are blocked until the current limit has been confirmed. The downside with this approach is that it introduces more latency to every request by default. The advantage is that it is more precise and consistent. ## Example Rate Limits The default platform rate limit for `requests` is a limit of 1000 requests per minute per customer. ```ts { enabled: true, interval: '1m', limit: 1000 } ``` This example rate limit restricts customers to 100 requests per day. It uses `strict` mode which adds a little extra latency but guarantees that customers will never exceed the limit. ```ts { enabled: true, interval: '1d', limit: 100, mode: 'strict' } ``` This is an example of a disabled rate limit. ```ts { enabled: false } ```