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

# Introduction

## What is a vault?

A vault is a smart contract that automates depositing capital into a DeFi protocol. Vaults also commonly pool capital from various users and create economies of scale through reducing gas costs and achieving higher levels of protocol incentives.

Vaults are a great way to participate in DeFi:

* Minimal maintenance (compared to manually using a protocol)
* Useful metrics to help evaluate opportunities (vault user interfaces commonly show APY, overall value locked in an opportunity, deposit history, etc.)
* Helpful with discovering new protocols
* Often cheaper to use than protocols directly, sometimes with higher returns

### Guides: Jump right in

Follow our handy guides to get started on the basics as quickly as possible:

### Fundamentals: Dive a little deeper

Learn the fundamentals of Yagi to get a deeper understanding of our main features:

{% content-ref url="/pages/wqk63WkHqlVVENeJaEwP" %}
[ERC4626](/products/vaults/erc4626.md)
{% endcontent-ref %}


---

# 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.yagi.fi/products/vaults/introduction.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.