> For the complete documentation index, see [llms.txt](https://docs.scoredetect.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scoredetect.com/api/scoredetect-api/usage-policy.md). # Usage Policy The ScoreDetect API operates under a usage policy that is determined by the services we utilize. This policy ensures the reliable and efficient functioning of the ScoreDetect API. However, we understand that some users may encounter specific challenges or have unique usage requirements that require modifications to their **rate limits**, **API response times**, or **other aspects** of the ScoreDetect API service. If you are experiencing any issues or have specific requirements that hinder your effective utilization of the ScoreDetect API, we encourage you to reach out to us for assistance. Please contact our support team at , and we will be more than happy to help you with your needs and provide a suitable solution. At ScoreDetect, we value our users and strive to ensure a positive experience when utilizing our API. We are committed to addressing your concerns and working together to find the optimal approach for integrating the ScoreDetect API into your application or system. --- # 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.scoredetect.com/api/scoredetect-api/usage-policy.md?ask=&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.