> For the complete documentation index, see [llms.txt](https://lucia-protocol.gitbook.io/lucia-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lucia-protocol.gitbook.io/lucia-protocol/low-collateralized-ratio-100.md).
# Low Collateralized Ratio (100%)
Within the traditional lending ecosystem, borrowers often find themselves restrained by high collateral requirements—commonly set at 120% of the loan value. This mandates that borrowers lock in assets exceeding the credit they wish to procure, limiting their financial agility. Lucia Protocol challenges this convention by introducing a revolutionary 100% Collateralized Ratio.
In Lucia's model, this ratio can go as low as 100%, signifying that borrowers can leverage their entire collateral to access equivalent credit amounts. This innovation expands the borrowers' potential for more significant credit access, effectively democratizing financial inclusivity.
By setting the Collateralized Ratio at 100%, Lucia Protocol amplifies the ability for borrowers to fully capitalize on their assets, offering a more flexible and accessible credit framework.
---
# 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://lucia-protocol.gitbook.io/lucia-protocol/low-collateralized-ratio-100.md?ask=&goal=
```
`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.