> For the complete documentation index, see [llms.txt](https://sparklexai.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sparklexai.gitbook.io/docs/core-concepts/the-vaults.md). # The Vaults Vaults turn strategy into action. They sit on-chain, hold assets, and carry out only the operations written into their code — reallocate, claim, compound, hedge (where enabled). Vaults do not guess. They do not improvise. If a proposed move fails a safety check, nothing happens.\ \ Every SparkleX vault enforces risk limits, protocol permissions, and accounting rules that were audited before launch. No one — not SparkleX, not the AI, not even you via a UI shortcut — can force the vault to break those rules.\ \ SparkleX supports two vault types: **Earning Vaults** and **Farming Vaults**. They share the same security principles yet serve different goals. --- # 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://sparklexai.gitbook.io/docs/core-concepts/the-vaults.md?ask=&goal= ``` `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.