> For the complete documentation index, see [llms.txt](https://docs.yieldoor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yieldoor.com/readme.md). # Welcome to Yieldoor **Yieldoor** is a DeFi yield protocol built to make your capital work harder through optimized, automated strategies across liquidity management, lending, and leveraged yield. We combine some of the most powerful concepts in DeFi—like concentrated liquidity, fixed-yield arbitrage, and capital-efficient leverage—into a seamless platform for both passive and active users. Whether you're looking for: * **Stable, passive returns** * **Active, high-yield strategies** * Or **leveraged opportunities with greater upside** Yieldoor offers the tools and infrastructure to help you earn more—without needing to manage positions manually or chase the latest trend. {% hint style="info" %} Something you don't understand? Something missing? Send a message to [@deadrosesxyz](https://x.com/deadrosesxyz) on Twitter/X he'd be more than happy to help! {% 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.yieldoor.com/readme.md?ask=&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 `build a script that syncs our docs to a CMS` 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.