> For the complete documentation index, see [llms.txt](https://vaultbook.gauntlet.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vaultbook.gauntlet.xyz/vaults/morpho-vaults/vault-curation-considerations-a-deeper-dive/asset-liquidity.md).

# Asset Liquidity

Morpho introduces “idle markets” that allow Gauntlet, as a curator, to ensure that some amount of liquidity is always available for withdrawals.

We constantly monitor overall market liquidity and leverage and rebalance our vault supply allocation in accordance with the solution to the following optimization problem:

Determine a supply allocation that maximizes vault APY subject to the following constraints:

* Expected liquidations under specified price and liquidity drawdowns should remain below a predetermined tolerance level based on current market conditions.
* Resulting borrow and supply rates competitively must stay within a predetermined tolerance of relevant market rates.
* Market utilization must stay between 88-92%.
* Liquidity available for immediate withdrawals must be greater than a predetermined withdrawal amount (e.g., 10% of vault deposits available for immediate withdrawal at all times).


---

# 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://vaultbook.gauntlet.xyz/vaults/morpho-vaults/vault-curation-considerations-a-deeper-dive/asset-liquidity.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 `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.