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

# Revenue Model

Seerdex generates revenue through a diversified set of mechanisms embedded within the protocol:

* **Trading fees** across prediction markets, binary options, and perpetual contracts.
* **Market creation fees** for launching new markets.
* **Token listing fees** for adding new cross-chain assets.
* **Liquidation fees** within leveraged positions.

A portion of this revenue may be redistributed to $SEERX holders or reinvested into the ecosystem to fund development, liquidity, and user incentives. This creates a sustainable economic model that scales with platform adoption — as activity grows, so does the value flowing back to the community.


---

# 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://seerdex.gitbook.io/seerdex-whitepaper/revenue-model.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.