> For the complete documentation index, see [llms.txt](https://guide.moontrader.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.moontrader.com/en-moontrader-docs/trading/trading-algorithms/general-algorithm-settings/price-step-filter.md).

# Price Step Filter

The "Price Step" filter allows the algorithm to place orders only if the price step (as an absolute percentage of the current price) is within the specified range.

### How to Use

Specify the price step range in percentages from minimum to maximum value.

**How it works:** The algorithm checks whether the trading pair's price step falls within the specified range. If yes — orders are placed, if no — the pair is excluded from trading.

**Example:** If you set a range from 0% to 0.25%, the algorithm will only work on pairs where the minimum price change is no more than 0.25% of the current price.

### What is Price Step

**Price Step** is the minimum possible price change for an instrument on the exchange. It determines how much the price can change between two orders.

**Why this is important:** To avoid trading on low-volatility coins, use a small price step.

### Application

Enable the filter and set the range. The algorithm will only work with pairs whose price step meets your requirements.


---

# 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://guide.moontrader.com/en-moontrader-docs/trading/trading-algorithms/general-algorithm-settings/price-step-filter.md?ask=<question>&goal=<user_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.
