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

# Revenue Model

Our protocol currently operates on three primary revenue models.

\
Buy and Sell Fees

The bot charges a 3% buy fee and a 2.5% sell fee on every leverage trade. This is calculated on the total position size, which includes both the user’s initial funds and borrowed funds. For example, a trade with 5x leverage on a $100 initial investment would have the buy fee calculated on $500, not just the $100 initial. The same applies to the sell fee, which is taken from the total sold amount regardless of whether the trade was in profit or loss.

\
API Whitelabel Integration

Teams that integrate our utility as a whitelabel service will operate under a hardcoded fee structure. A percentage of fees generated by their project will automatically be sent to 0xLeverage. These fees will be added to our revenue pool and distributed to revenue share holders using the same 50% model.

\
Revenue Share to Holders

As outlined in the revenue share section, 50% of all revenue generated from both buy and sell fees and API whitelabel integrations is distributed to holders with at least 0.25% of the 0xLeverage token supply (2.5 million tokens). To date, more than $150,000 USD (45 ETH) has been distributed to holders from real bot-generated revenue.\ <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://docs.0xleverage.io/technicals/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.
