> For the complete documentation index, see [llms.txt](https://credix-1.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://credix-1.gitbook.io/docs/introduction/what-is-credix.md).
# What is CrediX?
is a money market abstraction infrastrcuture protocol designed to optimize and simplify how users interact with lending and borrowing platforms. It acts as a **unified aggregator and optimizer** that allows users to deposit or borrow assets without manually researching across multiple protocols like Aave, Compound, or Morpho.
***
### Vision
CrediX envisions a open market where capital efficiency, risk management, and accessibility are core components. By offering smart routing, real-time rebalancing, and integrated protocol access, CrediX makes DeFi lending and borrowing intuitive, profitable, and safe for all user types.
***
### Problem Space
The current DeFi ecosystem is fragmented. Users are forced to:
* Compare multiple protocols manually for rates.
* Manage positions across different UIs.
* Miss yield opportunities due to static deposits.
* Face inefficient capital usage when borrowing.
CrediX solves this with **automation, intelligence, and composability**.
###
---
# 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://credix-1.gitbook.io/docs/introduction/what-is-credix.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.