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

# Why INVAST?

INVAST provides the first complete solution for the tokenization and trading of RWAs while respecting ownership rights. 

INVAST will feature integrated applications that simplify the entire RWA lifecycle:

* **Real Estate Tokenization:** Enable fractional ownership, backed by official title deeds, and streamline trading of real estate assets.
* **Lending & Borrowing Platform:** Unlock liquidity by using tokenized assets as collateral for capital access.
* **Native DEX:** Provide deep liquidity and allow investment in RWA-backed pools, generating real-world yield.
* **Plug-and-Play Compliance Solutions:** Streamline KYC/KYB processes, ensuring a frictionless, compliant user experience.

**Not our platform, not your asset.**


---

# 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.invast.io/overview/why-invast.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.