> For the complete documentation index, see [llms.txt](https://docs.rektgames.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rektgames.io/whitepaper/platform-economy/revenue-streams.md).

# Revenue Streams

This section is dedicated to the multiple ways parties involved with REKT Games can benefit from the platform:

REKT Games' Revenue Streams:

1. Battle Pass Price Tag&#x20;
2. Exclusive NFT Minting &#x20;
3. Character Customization&#x20;
4. Third-party NFT Integration&#x20;
5. 2.5% Royalties from Marketplace Transactions
6. 30% cut from revenue generated through third-party games&#x20;

Revenue Streams for the User&#x20;

1. Revenue Sharing – 30% of REKT Games' total revenue&#x20;
2. Trading NFT on the marketplace&#x20;
3. Battle Pass ROI&#x20;

Revenue Streams for Creators&#x20;

1. Monetizing their games. Either through exclusive NFT created for the game, or through a traditional price tag, or both. &#x20;
2. Top 4 performing games in terms of engagement reward their creators with up to 10% of REKT Gaems' total revenue.


---

# 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://docs.rektgames.io/whitepaper/platform-economy/revenue-streams.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.
