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

# Fees Structure

#### Fees Structure

Lend Bridge operates with a **transparent and minimal fee structure** to ensure fair and efficient lending operations. The fees are structured as follows:

* **Borrowing Fee (1%)**: A small fee charged when users take out a loan. This fee helps maintain liquidity and funds protocol operations.
* **Loan Repayment Fee (0.5%)**: When a borrower repays their loan, a 0.5% fee is applied, ensuring seamless protocol maintenance and continued development.
* **Withdrawal Fee (0.3%)**: Users withdrawing their collateral or loaned funds pay a nominal fee to support network functionality and gas costs.
* **Liquidation Fee (2%)**: In cases where a borrower fails to maintain the required collateral ratio, the protocol automatically liquidates the collateral. A 2% liquidation fee is imposed to compensate for liquidation execution and incentivize liquidators who help maintain system stability.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://whitepaper.lendbridge.xyz/fees-structure.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.