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

# Value Propositions

How Mito sets itself apart

### **Automated Trading Vaults**

The diverse range of vaults employ advanced algorithms like the Avellaneda-Stoikov Market Making (ASMM) or Constant Product Marketing Making (CPMM) strategies, designed to deliver returns while minimizing risk. Users can select from a spectrum of strategies tailored to their needs and target returns.

### **Transparent Operations**

Mito offers full transparency. Access detailed performance data, on-chain contract addresses, and even the underlying logic of trading algorithms. Every single parameter is fully on-chain, allowing users to make informed data-driven decisions.

### **Vault Tokenization**

Each vault issues its own token representing your share of the underlying assets and accrued returns. These tokens simplify portfolio management and allow users to deposit for additional rewards.

### **Integration with Injective**

Built on Injective, Mito benefits from its robust infrastructure and low transaction fees. In addition, Injective’s orderbook in the Exchange Module powers omnichain liquidity across all facets of the broader dApp ecosystem.&#x20;

Mito’s launchpad platform serves as a base for both fair token launches and efficient liquidity bootstrapping. By being built on Injective, Mito vaults enjoy the power of a truly on-chain liquidity and one of the fastest growing ecosystems in all of crypto.

<br>


---

# 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.mito.fi/introduction/value-propositions.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.
