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

# Claim Purchase

Find and download the Striga scripts you bought.

Striga scripts are sold through the **Cfx.re** store system. When you buy one, it is added to the **Cfx.re account** you logged in with at checkout.

{% hint style="info" %}
Buy Striga scripts at [striga.tebex.io](https://striga.tebex.io). Log in at checkout with the Cfx.re account that owns your server's license key.
{% endhint %}

{% stepper %}
{% step %}

### Open the Cfx.re Portal

Go to [portal.cfx.re](https://portal.cfx.re) (this replaced the old **Keymaster**) and log in with the **same Cfx.re account** you used to buy the script.
{% endstep %}

{% step %}

### Open your granted assets

Go to **Assets** → **Granted Assets**. Every script you bought is listed there.
{% endstep %}

{% step %}

### Download

Press **Download** next to the script. You get a `.zip` file.
{% endstep %}

{% step %}

### Install

Unzip it into your server's `resources` folder. Do not rename the folder. Then follow the **Installation & Configuration** page of that script.
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
Your server must use a **license key from the same Cfx.re account** that owns the script (`sv_licenseKey` in `server.cfg`). A key from another account gives an escrow error. See [FiveM Escrow Errors](/docs/fivem-escrow-errors.md).
{% endhint %}

## Get striga-core

Every Striga script needs **striga-core**. Make sure you have it too, and install it first.

{% content-ref url="/pages/k3Cvtdo9uJ60DuIMm4fd" %}
[Installation & Configuration](/docs/striga-core/installation-and-configuration.md)
{% endcontent-ref %}

## FAQ

<details>

<summary>The script is not in my granted assets</summary>

* Check you are logged in with the Cfx.re account you used at checkout.
* Wait a few minutes after the payment and refresh the page.
* Still missing? Open a ticket on [Discord](https://discord.gg/yr54pFC7KG) with your Tebex order ID.

</details>

<details>

<summary>Can I move the script to another account?</summary>

Assets stay on the Cfx.re account that bought them. Contact support on [Discord](https://discord.gg/yr54pFC7KG) if you need help.

</details>

<details>

<summary>Where do I get updates?</summary>

Download the script again from **Granted Assets**. See [Updates & Versions](/docs/updates-and-versions.md).

</details>


---

# 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://striga.gitbook.io/docs/claim-purchase.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.