> For the complete documentation index, see [llms.txt](https://docs.kyberswap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyberswap.com/~/changes/1kQEhDNzHMDf7SwOE6Yu/liquidity-solutions/kyberswap-elastic/user-guides.md). # User Guides Simple Step-By-Step Tutorials The following user guides are targeted at KyberSwap Elastic liquidity providers and covers the end-to-end flow from liquidity provision, yield farming, and liquidity position exits. This section was created as the liquidity provision steps differs between Classic and Elastic. If you're still unsure which protocol best suites your needs, you can visit the [Classic vs Elastic](/~/changes/1kQEhDNzHMDf7SwOE6Yu/liquidity-solutions/classic-vs-elastic.md) page. Alternatively, you can start at the beginning of your yield generation journey by visiting [Earn Yield By Contributing Liquidity](/~/changes/1kQEhDNzHMDf7SwOE6Yu/kyberswap-solutions/kyberswap-interface/user-guides/earn-yield-by-contributing-liquidity.md). For all other use cases (swaps, wallet management, etc.) please refer to the [User Guides](/~/changes/1kQEhDNzHMDf7SwOE6Yu/kyberswap-solutions/kyberswap-interface/user-guides.md) section under KyberSwap Interface. --- # 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://docs.kyberswap.com/~/changes/1kQEhDNzHMDf7SwOE6Yu/liquidity-solutions/kyberswap-elastic/user-guides.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 `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.