> For the complete documentation index, see [llms.txt](https://leviascripts.gitbook.io/levia-scripts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leviascripts.gitbook.io/levia-scripts/levia-inventory/installation.md).

# Installation

### Asset Download

To access your asset, you must have purchased it using your own **Keymaster account**.

Once purchased through our official store, the asset will automatically appear in your **Cfx.re Portal**, where you can download it directly from your dashboard.

Assets can also be transferred between Keymaster accounts using the official transfer system if needed.

***

### Requirements

Before installing, ensure the following dependencies are installed and running correctly:

* ox\_lib
* oxmysql
* MugShotBase64 (Optional)
* Game build **6116 or higher**

***

### Installation Steps

1. Ensure all dependencies are properly installed and started.
2. (Optional) Adjust configuration files to your preference.
3. Drag and drop `ox_inventory` into your `resources` folder.
4. Add the resource to your `server.cfg`:

```
ensure ox_inventory
```

5. Make sure it starts **after all dependencies**.
6. Restart your server.


---

# 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://leviascripts.gitbook.io/levia-scripts/levia-inventory/installation.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.