> For the complete documentation index, see [llms.txt](https://vertexbsc.gitbook.io/afterburner-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vertexbsc.gitbook.io/afterburner-finance/protocol-basics/auto-liquidity-engine.md).

# Auto-Liquidity Engine

Market liquidity plays a crucial role in protocol health and has the utmost importance. \
\ <mark style="color:blue;">**The automatic liquidity engine will automatically inject liquidity into the market every 24 hours.**</mark>

4% of the tax from each buy and sell is automatically stored on the Auto-LP wallet in the form of $ARB tokens. The AMM algorithm (Automated Market Maker) embedded into the Auto-Liquidity Engine adds accumulated BNB and token holdings at a 50/50 amount as extra liquidity so the liquidity will be increased.\
\
Auto Liquidity engine does this procedure every 24 hours and consequently saves holders from volatility by strengthening the market structure and reducing slippage as well as prolonging the runway of AFTERBURNER.


---

# 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://vertexbsc.gitbook.io/afterburner-finance/protocol-basics/auto-liquidity-engine.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.