> For the complete documentation index, see [llms.txt](https://docs.volven.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.volven.io/strategies/slicer.md). # Slicer SC <\> ## What is the Volven Slicer? A Slicer is a dynamic execution strategy and can be described as a short-term TWAP strategy. The strategy will spread the executions of the order up to 15 min from the start (default value 1 min). Slicer aims to trade at market VWAP or better in a given time window. The Slicer is given the discretion to capture crypto momentum, volume surprises, and optimal order placement levels. It is a strategy that works well when you have decided on a level where you are happy to add or sell without being static in the market. Slicer focuses highly on order handling and the importance of having the highest possible fill rate of passive executions. This will lower the commission and increase spread capture ### How to place a Volven Slicer? <\> ### Optional parameters
ParameterPurpose
Price LimitUpper barrier for buying, or lower barrier for selling. Prevents your strategy from buying at an unfavorable price.
--- # 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://docs.volven.io/strategies/slicer.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.