> For the complete documentation index, see [llms.txt](https://docs.krystal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.krystal.app/products/liquidity-management/lp-transactions.md). # Manage Liquidity Position > **Handling LP transactions has long been a cumbersome process for liquidity providers, involving multiple steps to add or remove liquidity, challenges in claiming or compounding fees, and complexities in rebalancing without automation tools. To address these issues, we've integrated a comprehensive suite of LP transaction features into Krystal, designed to simplify these processes and provide an efficient, cost-effective solution for all your liquidity management needs.** Our LP transaction features currently include six key functions: Provide Liquidity, Remove Liquidity, Claim Fees, Compound, Rebalance, and Auto-Rebalance. We’re also working on additional automated features like Auto-Compound and Auto-Exit, which will be released soon. Further information can be found in the following sections. --- # 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.krystal.app/products/liquidity-management/lp-transactions.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.