> For the complete documentation index, see [llms.txt](https://docs.dahlia.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dahlia.xyz/readme.md). # What is Dahlia? Dahlia is a permissionless, modular lending protocol that emphasizes advanced risk control and liquidity aggregation, built atop the [Royco Protocol](https://royco.org). Designed to optimize capital efficiency and expand access to liquidity across a wider array of assets, Dahlia offers a flexible framework for market participants to manage risk while facilitating seamless borrowing and lending. Dahlia empowers users to create markets, lend, borrow, repay, and withdraw seamlessly, supporting a comprehensive range of crypto lending and borrowing activities. Its modular design enables participants to maximize capital efficiency through limit orders while interacting with multiple liquidity pools. This adaptability not only improves capital allocation but also strengthens the overall functionality and resilience of the ecosystem. --- # 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.dahlia.xyz/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.