> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/getting-started/subscribe-to-xygeni.md).
# Subscribe to Xygeni
## Subscribe to Xygeni
To upgrade from the Free tier to a paid plan, go to the Subscription section.
Please navigate to **Settings** >> **Subscription**
{% hint style="info" %}
You can check the complete information of Subscription Section in Settings block in the following page of the documentation: [Subscription](/xygeni-administration/platform-administration/subscription.md)
{% endhint %}
## Access to Subsciption section
Open the **Settings** menu and select **Subscription**. The subsequent screen with appear:
## Subscribe
Click the **Upgrade plan** to commence the selection of plans and determine the quantity of daily scans. Visit the [pricing page](https://xygeni.io/pricing/) for detailed information on plans and pricing.
Once you've chosen your subscription preferences, you'll be directed to a secure external payment platform. Xygeni does not store or handle any payment details or personal information related to your transactions.
Your license will be updated upon successful payment confirmation, allowing you to utilize the Xygeni platform.
---
# 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.xygeni.io/getting-started/subscribe-to-xygeni.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.
