> For the complete documentation index, see [llms.txt](https://drfx-store.gitbook.io/drfx-store-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://drfx-store.gitbook.io/drfx-store-docs/documentation/support-and-policies/purchase-and-license.md).

# Purchase & License

Account, delivery, and license guidance for DrFx resources.

DrFx resources are distributed through Tebex. Some FiveM products use CFX Asset Escrow and are tied to the CFX account used at checkout.

### Before purchasing

* Confirm that the product supports your framework and required dependencies.
* Sign in with the intended Tebex and CFX accounts.
* Review the current product page for price, availability, and requirements.

### After purchasing

* Keep the Tebex confirmation and transaction information.
* Download only from the official delivery platform.
* Store a private backup of your configuration, not a redistributed copy of the product.

### License safety

Do not share paid files, license keys, Keymaster access, or account credentials. Support staff do not need your password.

### Store availability

Products may be updated, hidden, or removed. The live store at <https://drfx.tebex.io/> is the source of truth for the current 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://drfx-store.gitbook.io/drfx-store-docs/documentation/support-and-policies/purchase-and-license.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.