> 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/api-ingestion-releases/readme.md). # API Ingestion Cortex Cloud discovers cloud resources by calling cloud service provider APIs. Each discovery capability is a resource ingestion type (RIT), identified by a RIT name and mapped to an asset type. The pages here record which RITs were added, changed, or deprecated in each release, with the cloud service provider, service, required permission, asset type ID, and API action for each. Use them to see what new coverage a release brought, to work out which permissions to grant when you adopt it, and to find out when coverage you relied on was withdrawn. For the complete list of API ingestions across all releases, rather than the delta for one, see the [Cortex Cloud Discovery Catalog](https://cortex-docs.paloaltonetworks.com/discovery-catalog/). --- # 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/api-ingestion-releases/readme.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.