> For the complete documentation index, see [llms.txt](https://whitepaper.luxeya.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.luxeya.io/native-token-usdluxa/utility.md).

# Utility

The $LUXA token is the core utility asset of the LUXEYA ecosystem, powering all major platform functions:

* **Mystery Box Access**\
  Used to purchase Mystery Boxes at discounted rates, giving players access to NFTs, sweepstakes entries, and luxury rewards.
* **Sweepstakes Rewards Distribution**\
  All sweepstakes prizes—whether in tokens, NFTs, or real-world assets—are distributed through $LUXA.
* **Luxury Marketplace Transactions**\
  Used to bid on, buy, and sell tokenized real-world assets (RWA NFTs) such as watches, tech, and other luxury items.
* **DAO Governance**\
  Holders of $LUXA can vote on platform decisions, including new features, game modes, prize types, and operational upgrades.


---

# 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://whitepaper.luxeya.io/native-token-usdluxa/utility.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.