> For the complete documentation index, see [llms.txt](https://docs.akto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akto.io/api-protection/concepts/api-rate-limit.md).

# Dynamic Api Rate Limiting

### Akto's Next Gen API Rate Limits Discovery:

Traditional rate limits require predefined RPM per API. At scale (hundreds of APIs), this is impractical. As organizations evolve, API traffic patterns change, making static limits brittle.

Traffic varies by endpoint (e.g., `/cancel-booking` vs `/book`) and over time (e.g., marketing spikes). Akto learns per-endpoint baselines and adapts as patterns shift.

#### Key Innovations

**Adaptive Learning:** Learns real usage over time.

**Endpoint-Specific Baselines:** Builds per-endpoint limits.

**Dynamic Adaptation:** Adjusts to spikes and longer-term shifts.

<figure><img src="/files/8Vm0D5oiH1VUUbmGdO1n" alt=""><figcaption></figcaption></figure>

## How to configure

By default, Akto Threat Protection applies a global rate limit rule.

To change settings, go to **Settings → Threat Configuration**.

### Default Configuration

Global dynamic rule that auto-learns per-endpoint baselines over 2 days. Uses p75 with 20% overflow and 0.5 confidence to throttle anomalies.

* **Rule Name**: `Global Rate Limit Rule`
* **Period**: `5 minutes`
  * Window duration
* **Behaviour**: `Dynamic`
  * Uses auto‑learned limits
* **Baseline Period**: `2 days`
  * Days used to learn usage patterns
* **Percentile**: `p75`
  * Requests made by 75% of users
* **Overflow Percentage**: `20`
  * Allowed burst above baseline
* **Rate Limit Confidence**: `0.5`
  * Minimum confidence in learned patterns

<figure><img src="/files/ZMTGVV8JYO2F2mztjci6" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akto.io/api-protection/concepts/api-rate-limit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.