> 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/setup/installation-and-delivery.md).
# Installation & Delivery
How to receive and install DrFx resources safely.
Follow this checklist before installing any DrFx resource.
### 1. Complete the purchase
Purchase or claim the resource from using the correct Tebex and FiveM account.
### 2. Download the resource
Free and standard packages are available through your Tebex purchase history. Escrow-protected FiveM resources are delivered through the CFX Keymaster account linked during checkout.
### 3. Read the included files
Open the packaged README and configuration files before renaming folders or changing code. Product-specific instructions take priority over this general guide.
### 4. Install on the server
Move the complete resource folder into your server resources directory. Keep the internal folder structure unchanged.
### 5. Start the resource
Add the required ensure line to server.cfg after all required dependencies. Restart the server and review the console for dependency or configuration errors.
### 6. Verify in game
Join the server, test the main feature, and confirm that the resource still works after a server restart.
### Need help?
Join and open a support ticket with the product name, your framework version, console errors, and the steps you already tried.
---
# 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/setup/installation-and-delivery.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.