> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/faqs/my-organization-has-made-an-excessive-number-of-requests-to-sharinpix-for-today-how-do-i-fix-this.md).

# My organization has made an excessive number of requests to SharinPix for today. How do I fix this?

![](https://751044238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi8tH1o5AHthxksYgF6ij%2Fuploads%2Fcmhchpbik6UsEiK8dhW1%2Fimage%20\(26\).png?alt=media\&token=5a6be4d1-1171-4859-a24c-c431c395eaac)

If you are seeing the above error on your SharinPix components, it means that your organization has exceeded the number of requests allowed. This is likely due to an overuse of SharinPix, with respect to the number of SharinPix users in the organization. All features will automatically be restored within 24 hours. For any critical issues, contact <support@sharinpix.com>.

[SharinPix's Fair Use Policy document](https://sharinpix.com/fair-usage-policy/) contains more details on applicable rate limits and examples of how they can be exceeded. It also describes how to request higher rate limits and immediate restoration of features.

To keep an eye on your limits, admins can log on the SharinPix admin dashboard and check out the "Current Rate Limit" value under the "Settings" tab.

![](https://751044238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi8tH1o5AHthxksYgF6ij%2Fuploads%2FIVMwIJoM7HwjxGQT9k16%2Fimage%20\(27\).png?alt=media\&token=05e28e1b-a9a2-4a52-9e33-a389daac8508)


---

# 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.sharinpix.com/faqs/my-organization-has-made-an-excessive-number-of-requests-to-sharinpix-for-today-how-do-i-fix-this.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.