> 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/onboard-cortex-xdr/cortex-aes-tenants.md).

# Cortex AES tenants

Learn about the Cortex AES tenant you receive with the standalone AES license.

Cortex AES is a tenant type that you receive when you purchase the standalone AES license, which you can also purchase with Flex Credits. You receive a Cortex AES tenant even if you already have a Cortex XDR tenant. A Cortex AES tenant includes only the pages you need to deploy Targeted agents and manage Agentic Endpoint Security (AES).

Cortex AES tenants support only the Targeted agent type. You manage AES under **Modules** <i class="fa-arrow-right">:arrow-right:</i> **Agentic Endpoint Security**.

{% hint style="info" %}

#### Note

If you purchase Cortex XDR ONE, which includes AES, you receive a Cortex XDR tenant instead of a Cortex AES tenant. If you have Cortex XDR Pro, you can upgrade your Cortex XDR tenant to Cortex XDR ONE.
{% endhint %}

### Pairing with an existing tenant

If you already have a Cortex XDR tenant, you can pair your Cortex AES tenant with your Cortex XDR tenant. After pairing, the Agentic Endpoint Security module from your Cortex AES tenant appears in your Cortex XDR tenant, and you can run AES on your existing Standard agents. Pairing can take up to 1 hour. For prerequisites and steps, see [Pair Cortex AES for existing Cortex XDR customers](https://cortex-docs.paloaltonetworks.com/cortex-xdr/onboard-cortex-xdr/cortex-aes-tenants/pair-cortex-aes-for-existing-cortex-xdr-customers.md).

{% hint style="warning" %}

#### Important

* If you plan to manage Agentic Endpoint Security from your Cortex XDR tenant, pair before you set up the Cortex AES tenant. Pairing doesn't transfer configuration or data from the Cortex AES tenant.
* If you plan to manage Agentic Endpoint Security from the Cortex AES tenant, see [Set up a Cortex AES tenant](https://cortex-docs.paloaltonetworks.com/cortex-xdr/onboard-cortex-xdr/cortex-aes-tenants/set-up-a-cortex-aes-tenant.md).
  {% endhint %}

### Upgrading to Cortex XDR ONE

You can upgrade a Cortex AES tenant to Cortex XDR ONE. Your AES settings and data carry over to the upgraded tenant. After the upgrade, your agents keep the Targeted agent type. To add full Cortex XDR capabilities to the agents, [change their agent type to Standard](https://cortex-docs.paloaltonetworks.com/cortex-xdr/protect-your-endpoints/install-and-manage-endpoints/set-up-endpoint-protection/change-an-agent-type.md).


---

# 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/onboard-cortex-xdr/cortex-aes-tenants.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.
