> 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/why-liquify.md).

# Why Liquify?

Liquify is the solution to the biggest challenges in token management and vesting in the crypto space.&#x20;

Here’s why Liquify stands out:

1. **Solves Illiquidity**\
   With traditional vesting, tokens are locked for months or years, leaving investors stuck. Liquify’s **Liquid Vesting** turns these locked tokens into **liquid tokens** that can be traded immediately, giving investors flexibility and access to funds.
2. **Simplifies Token Management**\
   For project creators, managing token allocations can be a nightmare—manual processes, errors, and inefficiencies waste time and money. Liquify automates the entire process, making it easier to set up and manage projects, vesting schedules, and distributions.
3. **Provides a Secondary Market**\
   Liquify includes a **secondary market with order books**, allowing investors to buy, sell, or trade tokens efficiently and transparently. This ensures ongoing liquidity and price discovery for token investments.

By addressing these challenges, Liquify empowers both investors and project creators to focus on what matters—growing projects and engaging communities.&#x20;


---

# 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.liquify.ventures/welcome/why-liquify.md?ask=<question>&goal=<user_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.
