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

# API Rate Limiting

API access is rate limited per user. The 10 requests per second (rps) baseline is adequate for most applications and users. The 10 rps allows for data access, while also minimizing the risk of resource outages due to excessive service calls or requests from any single access node or user cohort. If you require a higher rate limit for your API key, please write to <info@scicrunch.org> including documentation of the reasons for such enhanced access. We may then grant a higher rate limit for your existing API key.&#x20;

{% hint style="info" %}
API access is rate limited to 10 requests per second.  If you require enhanced access please contact <info@scicrunch.org>
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scicrunch.io/api-service-gateway-overview/api-rate-limiting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.