> For the complete documentation index, see [llms.txt](https://ezfi.gitbook.io/ez-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ezfi.gitbook.io/ez-finance/overview/whats-ez-fi.md).

# What's EZ-Fi?

EZ Fi is the first leveraged yield farming protocol on Aptos and Sui. There are a total of 3 parties who play an important role in EZ Fi: Lenders, Yield farmers, and Liquidators

* **Lenders** can lend many assets to earn a higher lending interest rate compared to most of the other lending protocols as the lending interest comes from leveraged yield farmers/liquidity providers who borrow these assets to yield farm/provide liquidity.
* **Yield farmers/Liquidity providers** can perform leveraged yield farming/liquidity providing on many asset pairs and DEXes in their preference and get even higher farming APY and trading fees compared to traditional yield farming with no leverage. By taking on leverage, EZ Fi would borrow the specified assets on behalf of the users to yield farm.
* **Liquidators** can perform liquidation on active positions that are at a 100% debt ratio to earn up to 5% bounty incentives.

{% hint style="info" %}
*Note that users can navigate through the* EZ Fi *dApp once connected with the supported wallet and can switch between available chains by toggling on the network options.* 
{% endhint %}


---

# 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:

```
GET https://ezfi.gitbook.io/ez-finance/overview/whats-ez-fi.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.