> For the complete documentation index, see [llms.txt](https://docs.mezz.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mezz.finance/introduction/readme.md).
# Welcome to Mezzanine
## Tranche Anything
Mezzanine is a framework for creating structured vaults around individual assets and yield strategies.
Each strategy operates through its own vault. A vault may hold a single asset, deploy a simple yield position, or execute a more complex strategy across multiple protocols. Each vault has its own parameters, including yield allocation, tranche capacity, withdrawal periods, fees, reserve requirements, and loss mechanics.
Users deposit the asset supported by the vault and select a risk tranche. The protocol bundles the required transactions, allowing the user to move directly from the deposit asset into their selected tranche.
> For example:
>
> **USDC** → **Senior Prime** or **Junior Prime**\
> \
> Behind the scenes, **USDC** is converted into **mxPrime**, the Prime Vault’s non-yield-bearing, **super-senior base token**, before being deposited into the selected tranche. This intermediate step is abstracted from the normal user experience.
---
# 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://docs.mezz.finance/introduction/readme.md?ask=&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.