> 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/developer-docs/overview.md). # Overview #### SparkleX Earn SparkleX Earn Vault is built on OpenZeppelin ERC4626 codebase and allows users to deposit crypto for yield. Upon successful deposit, a share token will be minted to the depositor's address (or designated receiver). The share token will accumulate yield steadily through SparkleX AI-empowered earning strategies which efficiently and safely distribute investments among leading DeFi protocols like AAVE and Pendle. Currently, this yield-earn product is supported on Ethereum. #### SparkleX Farming SparkleX Farming is built with AI agents to allow users to enjoy easy LP farming in popular DEXes like Uniswap and PancakeSwap. Currently, this farming product is supported on Ethereum, Base and BNB Chain. --- # 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/developer-docs/overview.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.