> For the complete documentation index, see [llms.txt](https://docs.liquify.ventures/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquify.ventures/welcome.md). # Welcome Invest in the future, trade in the present.
*** ## **What is Liquify?** Liquify is a decentralized platform designed to simplify and revolutionize how token allocations are managed in blockchain projects. Whether you’re a project creator, an investor, or part of a community VC, Liquify gives you the tools to access liquidity, transparency, and efficiency. *** ## **Why Choose Liquify?** * **Unlock Liquidity**: Trade or hold tokens even before they’re unlocked. * **Seamless Management**: Automate token vesting and distributions effortlessly. * **Trust and Transparency**: Powered by audited smart contracts, ensuring secure and fair transactions. *** ## **Who is it for?** Liquify is built for: * **Initiators**: Project creators, KOLs, VCs, community VCs, validators and more. * **Investors**: Individuals or groups looking to participate in early-stage projects. *** ## **What’s Next?** Explore the docs to learn more about how Liquify works, its unique features, and how you can become part of the future of decentralized finance. Get started today and take control of your blockchain investments like never before! --- # 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.liquify.ventures/welcome.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.