> For the complete documentation index, see [llms.txt](https://vaultbook.gauntlet.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vaultbook.gauntlet.xyz/vaults/morpho-vaults.md). # Morpho Vaults Welcome to our Morpho VaultBook, where you can learn about our Morpho Vaults, our approach to curation, and the various risk considerations that inform our strategies. We began curating vaults on Morpho in early 2024. We now curate 70+ vaults across Ethereum, Base, Arbitrum, OP Mainnet, Katana, and Unichain. Vaults are categorized into three distinct risk levels:
Cover image
Gauntlet Prime Vaults offer risk-adjusted yield from very low insolvency risk strategies, with blue chip, highly liquid assets as collateral.vaultbook-cover-prime.pngPrime Vaults
Gauntlet Balanced Vaults offer higher yield, with low insolvency risk strategies with a blend of blue chip and small-cap assets as collateral.vaultbook-cover-core.pngBalanced Vaults (Previously Core)
Gauntlet Frontier Vaults offer the highest yields, allocating to riskier markets that may lead to higher risks of insolvency.vaultbook-cover-frontier.pngFrontier Vaults
**Gauntlet Partner Vaults** can also be deployed in partnership with DeFi protocols that wish to integrate Gauntlet Vaults into their product stack. These can be either Prime, Balanced, or Frontier. --- # 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://vaultbook.gauntlet.xyz/vaults/morpho-vaults.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.