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

# Revenue Model

## 📊 Lends Protocol's Economic Model

The Lends protocol employs a **sustainable economic model** that aims to create value for all participants. It does this by charging a 10% fee on the interest received by lenders. This revenue generated is then divided between liquidity providers and stakers. Specifically, 70% of these revenues are returned to liquidity providers, while the remaining 30% are used to reward stakers.

## 💰 GMX-Inspired Fee Distribution

The distribution of protocol fees follows a *GMX-inspired model*. This model is designed to ensure a fair distribution of rewards and incentives for both liquidity providers and Lends token stakers. By adopting this approach, the LENDS protocol encourages users to actively contribute to the platform, fostering a healthy ecosystem that benefits all participants.


---

# 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.lends.so/tokenomics/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.