> For the complete documentation index, see [llms.txt](https://limitless.gitbook.io/rammlend/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://limitless.gitbook.io/rammlend/products/universal-lending-pool/liquidity-efficiency.md).

# Liquidity Efficiency

Under this system, active participation from the managers will allow all lending pools connected to a vault to reach an equilibrium state with similar risk-adjusted returns, which mitigates inefficiencies associated with liquidity fragmentation.&#x20;

If one lending pool has a higher utilization rate compared to its risk(high apr vs risk of collateral), managers will redeem(withdraw capital) from another lending pool with a lower risk-adjusted return(either low utilization rate or more risky collateral) and supply to the higher pool. This allows the lending pools to have a completely isolated structure(one collateral per token to be borrowed) without sacrificing much efficiency.&#x20;

{% hint style="info" %}
Managers are incentivized to constantly rebalance the pools to maximize their profit, which will also direct capital to instruments that need it most.&#x20;
{% endhint %}


---

# 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:

```
GET https://limitless.gitbook.io/rammlend/products/universal-lending-pool/liquidity-efficiency.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
