> For the complete documentation index, see [llms.txt](https://docs.aozo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aozo.io/aozo-earn/transparency/liquidity-and-withdrawals.md).

# Liquidity and withdrawals

How liquidity can affect your withdrawal timing and amount.

### Standard withdrawal

Standard withdrawal follows a request, settlement, and claim process. It depends on available cash and funds recovered from strategies.

1. Submit a withdrawal request.
2. Wait for the applicable settlement and funding process.
3. Claim USDC once the request is funded and settled.

{% hint style="info" %}
Requests follow the product rules and available funds. Strategy exits and settlement can delay completion. No fixed completion time is promised.
{% endhint %}

### Fast withdrawal

Where available, fast withdrawal may provide access to some funds sooner at a different price. It depends on immediately available liquidity after reserve and withdrawal limits apply.

{% hint style="warning" %}
The amount may be discounted. Only part of a request may complete. The remainder may stay in the standard withdrawal queue. A quote does not guarantee execution.
{% endhint %}

Check the terms and quoted amount before confirming a withdrawal.

Read [Deposits, shares, and withdrawals](/aozo-earn/aozo-earn/deposits-shares-and-withdrawals.md) and [Fees](/aozo-earn/aozo-earn/fees.md) for related details.


---

# 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.aozo.io/aozo-earn/transparency/liquidity-and-withdrawals.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.