> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/add-ons/add-on-activation.md).

# Add-on activation

#### What happens when you purchase an add-on?

This guide explains the next steps when you purchase an add-on on AppMySite. The activation process varies depending on whether you’ve bought a Service add-on or a Feature add-on.

#### Service add-ons

* After purchasing a service add-on, you’ll receive a confirmation email outlining the next steps.
* Our support team will then reach out with more details and guidance to help you get started.
* If any additional information or setup is required, the team will share clear instructions to complete the process.

#### Feature add-ons

* Feature add-ons are activated automatically as soon as your purchase is successful.
* You can begin using the feature immediately without any additional setup or approval.

{% hint style="success" %}
All add-on purchases are processed instantly. Service-based add-ons include follow-up communication from our support team, while feature add-ons activate automatically upon purchase.
{% endhint %}


---

# 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://docs.appmysite.com/app/add-ons/add-on-activation.md?ask=<question>&goal=<endgoal>
```

`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.