> For the complete documentation index, see [llms.txt](https://docs.cedro.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cedro.finance/cedro-as-an-ecosystem.md).

# Cedro as an Ecosystem

<figure><img src="/files/7zUmCDJo7DheSdnbJVte" alt=""><figcaption></figcaption></figure>

One of the major goals of Cedro Finance is to act as a cross-chain Liquidity Layer over time. Builders will be able to use Cedro's Liquidity and codebase to build their applications without having to worry about liquidity on their platform. A few out of the many applications that can be built using Cedro as the infrastructure are:

* Overcollateralized Decentralized Omnichain Stablecoins (ex. DAI for cross-chain)
* Peer-to-Peer Cross-chain Lending & Borrowing Platforms (ex. Morpho for cross-chain)
* Cross-chain DEXs (ex. Stargate)
* Omnichain Yield Aggregators (ex. Yearn for cross-chain)
* Cross-chain Perpetual Trading Platforms
* Credit line for fiat Platforms

And many more...

Some of these applications will be built in-house and, at the same time, builders will be incentivized through various programs to help build the Cedro Ecosystem.


---

# 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://docs.cedro.finance/cedro-as-an-ecosystem.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.