# Introduction Leveros is a **lending platform** on Ethereum, built on top of **Morpho Markets** and **Euler**, designed to optimize the use of these platforms by providing enhanced features for both borrowers and lenders. Leveros takes advantage of the robust infrastructure of Morpho and Euler to enable a seamless and efficient lending experience, while adding innovative features that set it apart from traditional lending protocols. **Key Features:** * **Spot Leverage**: Leveros allows borrowers to access spot leverage, which means users can borrow more than their initial capital to take larger positions in supported assets. * **Leveraged Farming**: Borrowers can also engage in **leveraged yield farming**, allowing them to farm tokens using borrowed assets, thus unlocking increased yields for themselves and indirectly benefiting lenders by increasing demand for borrowing. These features provide **higher yields for lenders** by enabling borrowers to increase their capital efficiency through leverage, creating more activity and revenue in the system. **AI Chatbot for User Support:** To ensure an optimal user experience, Leveros provides an **AI-powered chatbot** to assist users with any questions or issues. This AI chatbot delivers real-time support and guidance, helping users navigate the platform. By combining **lending optimization**, **leveraged opportunities**, and **AI-driven support**, Leveros offers a unique platform for maximizing capital efficiency in decentralized finance. --- # Agent Instructions: 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://docs.leveros.finance/introduction.md?ask= ``` 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.