> 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-agentix/learn-about-cortex-agentix/understand-cortex-agentix-licenses.md). # Understand Cortex AgentiX licenses Cortex AgentiX requires a yearly license per user. Multi-year licenses are available. #### License usage This table describes the types of Cortex AgentiX licenses which are used in the following circumstances: | Version | Usage | Description | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | Cortex AgentiX Enterprise | Built for customers who need a complete security automation solution, including threat intel management. | Cortex AgentiX SOAR with threat intel includes 4 users, six months of hot storage for incidents, and 800 compute units per year. | | Cortex AgentiX Base | Built for security operations and incident response customers who need case management with collaboration and playbook-driven automation. | Cortex AgentiX SOAR includes 2 users, six months of hot storage for incidents, and 400 compute units per year. | #### Development/Production tenants In Cortex AgentiX you can use a content management system with a remote repository to develop and test content. If you want a development tenant, you need a development tenant license. The development tenant license allows many users to build, test, and refine automations. It is not limited to your purchased user licenses, and it enables multiple stakeholders to work on these tasks. This supports faster innovation, more reliable workflows, and scalable solutions as your organization grows. #### License quota The following table describes the license quotas of each version in Cortex AgentiX. | | Cortex AgentiX Base | Cortex AgentiX Enterprise | | ------------------------------ | --------------------------------------------------------------- | ----------------------------------------- | | Users | Two users, additional users can be added | Four users, additional users can be added | | Compute units | 400 compute units per year\* | 800 compute units per year\* | | Integrations | Unlimited | Unlimited | | Incident Management | 180-day history\* | 180-day history\* | | Incident Triggered Automations | Unlimited | Unlimited | | Job Triggered Automations | Unlimited | Unlimited | | Intel Feeds | 5 active feeds, 100 indicators/fetch | Unlimited | | Threat Intel Library | Intelligence detail view and relationship data are not included | Unlimited | {% hint style="info" %} ### Note \*\*You can purchase additional compute units. \*You can extend incident retention by purchasing an add-on. For more information, see [Data retention policy](/cortex-agentix/learn-about-cortex-agentix/data-retention-policy.md). Intel feed quotas are based on the selected **Fetches Indicators** field in the integration instance settings, not the enabled status. Disabling an integration instance does not affect the intel feed quota. For example, if the AWS Feed is enabled and is fetching indicators and you don't want to include this in your quota, open the integration settings and clear the **Fetches Indicators** checkbox. {% endhint %} #### Cortex AgentiX users Cortex AgentiX has the following users: **Audit user** Audit users have read-only permission in Cortex AgentiX, meaning they cannot edit system components and data or run commands, scripts, and playbooks. Audit users can view incidents, dashboards, and reports. **Full user** Full users have read-write permission in Cortex AgentiX, meaning they can view and edit system components and data. They can investigate incidents, run scripts and playbooks, chat in the War Room, and more. Full users’ access to Cortex AgentiX is determined by their assigned role. --- # 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://cortex-docs.paloaltonetworks.com/cortex-agentix/learn-about-cortex-agentix/understand-cortex-agentix-licenses.md?ask=&goal= ``` `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.