> For the complete documentation index, see [llms.txt](https://whitepaper.werate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.werate.io/using-the-werate-app/revenue-model/user-generated-revenue.md).

# User-Generated Revenue

WeRate is the first platform that leverages blockchain technology, GameFi, SocialFi, and token incentives in a revolutionary concept to reward reviews. Being the first to market with this novel approach gives us headway in creating a large user base in an efficient manner, before competitors gain access to market share. This will result in general brand awareness across the entire crypto-ecosystem, resulting in an initial target market of around 500 million crypto users worldwide. This does not account for the annual growth in crypto users.

Revenue generation from users will be realized through:

* Bohemian purchases and trading
* Wallet transaction and trading fees
* In-app reservations
* Subscription model to unlock benefits


---

# 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.werate.io/using-the-werate-app/revenue-model/user-generated-revenue.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.
