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

# Rate Limits

To keep the Linkie Public API fast and reliable for everyone, Linkie enforces rate limits on API traffic. This protects the platform from accidental request storms and helps ensure fair usage across all keys.

### Default Limit

The Linkie Public API has a rate limit of `60 requests/minute per key`.

### Suggestions

* Cache profile identifiers and reuse them instead of refetching on every action.
* Cache identifiers (such as `_id` and `link_in_bio_id`) and reuse them instead of re-fetching them on every action.

### Exceeding the limit

If you send too many requests in a short period, you should expect a `429 Too Many Requests` response.

{% hint style="info" %}
Rate limiting is a normal part of API usage. If you receive a `429 Too Many Requests` response, wait briefly before retrying the request.
{% 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 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://linkie.bio/docs/getting-started/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.