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

# Rate Limits

API rate limits specify how many requests a user or application can make to an API within a specific time period. These limits help ensure fair usage and maintain performance across the platform. Rate limits can vary depending on the plan or product used. Check the rate limit details at the product level to optimize your usage and avoid interruptions.

## Data APIs

The following rate limits apply to search, collect, bulk collect, search preview, and webhook requests and depend on the plan you use. Check all plan features on the [Pricing](/pricing/pricing.md) page.

| Rate limits \ Plans    | Free trial | Mini    | Starter | Pro      | Growth   | Premium  | Scale     | Elite      |
| ---------------------- | ---------- | ------- | ------- | -------- | -------- | -------- | --------- | ---------- |
| Rate limits (Data API) | 5 req/s    | 5 req/s | 5 req/s | 10 req/s | 20 req/s | 50 req/s | 100 req/s | 100+ req/s |

## Agentic Search API

[Agentic Search API](/agentic-search-api/agentic-search-api.md) rate limits depend on the endpoint used.

| Endpoint                      | Requests per time period |
| ----------------------------- | ------------------------ |
| /v2/agentic\_search/fast      | 1 request per second     |
| /v2/agentic\_search/reasoning | 10 requests per hour     |


---

# 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.coresignal.com/api-introduction/rate-limits.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.