> For the complete documentation index, see [llms.txt](https://docs.krillprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.krillprotocol.com/krill-protocol-docs/mechanics-and-yield/revenue-model.md).

# Revenue Model

Krill Protocol maintains a transparent and aligned fee structure:

| Fee Category                | Rate    | Description                                                           |
| --------------------------- | ------- | --------------------------------------------------------------------- |
| **Deposit Fee**             | **0%**  | Zero entry charges on user capital.                                   |
| **Withdrawal Fee**          | **0%**  | Users can exit at any time with no penalty.                           |
| **Performance / Yield Fee** | **10%** | Deducted strictly from generated lending yield prior to distribution. |

## Financial Projections

* **Protocol Revenue**: Built on sustainable real yield without relying on inflationary governance token emissions.
* **Value Accrual**: 100% of collected protocol fees fund ongoing operation, security audits, and ecosystem expansion.


---

# 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.krillprotocol.com/krill-protocol-docs/mechanics-and-yield/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.