> 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. 

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. 


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.liquify.ventures/welcome/why-liquify.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.