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

# Token Utility

**Core Utilities of the CREO Token**

1. **Governance Participation:**\
   CREO Token holders can engage in the platform's decision-making processes, influencing updates and development directions.
2. **Staking Rewards:**\
   Users who stake CREO Tokens receive additional tokens as rewards, promoting active participation and long-term commitment.
3. **Marketplace Transaction Fees:**\
   Transactions within the CreoPlay marketplace are settled using CREO Tokens, streamlining the economic flow.
4. **NFT Purchases:**\
   CREO Tokens are utilized for acquiring NFTs within the platform, encompassing in-game items and collectibles.
5. **Liquidity Provision:**\
   CREO Tokens maintain liquidity across both centralized (CEX) and decentralized exchanges (DEX), ensuring accessibility.
6. **Developer Staking Requirements:**\
   Game developers are required to stake CREO Tokens to participate in the ecosystem, fostering commitment and quality contributions.
7. **Incubation Program Support:**\
   In the future, the CREO Token is employed in project incubation initiatives, aiding the development and launch of new games within the ecosystem.
8. **Play-to-Earn (P2E) Rewards:**\
   Players earn CREO Tokens through participation in P2E games, aligning incentives and enhancing engagement.

***

The CREO Token's multifaceted utility underpins the CreoPlay ecosystem, ensuring a cohesive and dynamic environment for all participants.


---

# 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://creoengine.gitbook.io/whitepaper/creo-engine-token-creo/token-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.