> 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/readme.md).

# Welcome

Mito is the Web3 finance hub for crypto. It is built on Injective, offering lightning fast transaction times, the lowest fees, and an unparalleled gateway for DeFi as a whole.

The protocol provides users with a suite of DeFi products with a current focus on automated trading vaults and a launchpad platform for token generation events and liquidity bootstrapping.

**Mito’s goals for every user, regardless of financial background or experience level, are to:**

1. Provide institutional-grade financial tools that simplify both liquidity provisioning and advanced trading techniques.
2. Create a launchpad system to bootstrap projects in a sustainable and fair process for all parties.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mito.fi/introduction/readme.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 `build a script that syncs our docs to a CMS` 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.