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

# Kawa

<figure><img src="https://3884080488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fm7znLoAnTYeZQSlOpoa6%2Fuploads%2FbuEnEMoHbD0Ue2Sgjc40%2Fbanner%20gitbook-02.png?alt=media&amp;token=cdad8b84-c4b3-4613-add8-842e3e5325f8" alt=""><figcaption></figcaption></figure>

## *Kawa is a* pioneering *cross-chain lending protocol, designed to offer a seamless, decentralized experience for borrowing and lending assets across multiple networks*&#x20;

Whether you are looking to borrow against your existing assets or earn interest on your crypto holdings, Kawa offers a user-friendly platform that is intuitive and accessible to anyone.&#x20;

* *With Kawa, users can easily access, communicate and manage liquidity for their assets on any supported chain.*
* By utilizing innovative technologies such as Kawa Core, Kawa Ports, and the XCM Aggregator, Kawa ensures enhanced security, speed, and interoperability, providing a powerful solution to the evolving DeFi landscape.<br>

With initial deployments on Sei, Ethereum, BSC, and expansion to other Layer 2 and EVM compatible blockchains, Kawa is committed to providing a truly cross-chain solution for decentralized finance.

*Join us on the cutting edge of the DeFi revolution and experience the benefits of seamless cross-chain liquidity with Kawa*

### ***Stay liquid!*** :ocean:


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kawa-fi.gitbook.io/kawa/kawa.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.