# Rate Limits

A rate limit is the number of API calls an app or user can make within a given time period. If this limit is exceeded or if CPU or total time limits are exceeded, the app or user may be throttled. API requests made by a throttled user or api will fail.

**All API requests are subject to rate limits.**

{% hint style="info" %}
Did you know? You can [contact us](https://www.serphouse.com/#contact-us) if you are on custom monthly plan and needs to increase a rate limit.&#x20;
{% endhint %}

#### Standard Rate Limit

| Plan                                                                      | Rate limit |
| ------------------------------------------------------------------------- | ---------- |
| Free Trial                                                                | 60         |
| Basic                                                                     | 60         |
| Regular                                                                   | 60         |
| [Custom Plan](https://www.serphouse.com/enterprise-custom-plan-offering/) | As needed  |

Above mentioned rate limits are calculated per minutes.&#x20;

#### Error Codes <a href="#error-codes" id="error-codes"></a>

When an app or user has reached their rate limit, requests made by that app or user will fill and the API will respond with an error code.

| Status code | Description       |
| ----------- | ----------------- |
| 429         | Too many requests |

#### Response Example

```json
{
    "message": "Too Many Attempts."
}

```

<br>


---

# Agent Instructions: 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:

```
GET https://docs.serphouse.com/introduction/rate-limits.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
