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

# Revenue Generation Strategy

RAWLI’s revenue model is designed to be sustainable, diversified, and aligned with long-term platform growth. Revenue is generated across three major pillars: Prediction Market Activity, Staking & Liquidity Operations, and Agentic AI Services. These streams strengthen the RAWLI ecosystem while continuously increasing token value and demand. 

## ***The revenues that the platform generates are listed below:***

●	Trading Fees
\
●	Market entry fees
\
●	Settlement fees
\
●	Liquidity provider fees
\
●	Market Creation Fees
\
●	Staking Yield (Protocol Revenue Sharing)
\
●	Agent Subscription <br>


---

# 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://rawlianalytics.gitbook.io/rawli-analytics-docs/basics/markdown.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.