> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/learn-about-cortex-xdr-5.x/fair-usage-policy-for-cortex-xdr.md). # Fair Usage policy for Cortex XDR Understand fair-use expectations for data ingestion, connected data sources, and API usage. To ensure the reliability, efficiency, and availability of Cortex XDR for all the users, we expect our customers to use it fairly, reasonably, and in a manner that does not adversely impact the product’s overall system performance. Cortex XDR offers various features for connecting external resources to Cortex XDR, including without limitation, frequency and/or volume of data ingestion, number of connected data sources, and API usages. Overuse or misuse of these features may adversely affect the reliability, efficiency, and/or availability of Cortex XDR. You are therefore required to utilize a reasonable volume of data ingestion, number of connected data sources, and API usage, based on your number of cloud assets protected by Cortex XDR (“Fair Usage Policy”). If, in our sole and reasonable discretion, we determine that your usage of Cortex XDR violates this Fair Usage Policy, we reserve the right to take appropriate action regarding such use, including without limitation, limiting the frequency and/or volume of data ingestions, limiting the number of connected data sources, and/or limiting the API usage, to bring your usage of Cortex XDR in alignment with this Fair Usage policy. --- # 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://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/learn-about-cortex-xdr-5.x/fair-usage-policy-for-cortex-xdr.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.