> For the complete documentation index, see [llms.txt](https://docs.algosniper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algosniper.com/buy-and-sell-indicator.md).

# Buy and Sell Indicator

![](https://3541426626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaJ7Vv6oQJL7Ywy4bmbsR%2Fuploads%2FeDPtz7ukWx4DIYbDltBW%2FBTCUSDT.P_2025-06-29_21-02-30.png?alt=media\&token=26bb9ec0-3c6d-4834-bab1-00f4509b865e)

The Buy and Sell indicator is designed to highlight potential trading opportunities by signaling a possible upward or downward move. While this indicator alone can sometimes be highly accurate—and may even suffice in certain scenarios—it should not be used in isolation. Successful trading requires confluence from multiple indicators and a strong understanding of market dynamics.

Consider this tool as a signal that suggests the probability of a price movement in a particular direction. For example, a "Buy" alert indicates that the price may likely rise, while a "Sell" alert suggests a possible decline. However, these alerts are not absolute instructions to take action. AlgoSniper includes additional indicators specifically built to help filter out false signals.

The full strategy—how to use this indicator effectively in combination with others—will be explained in more detail later.


---

# 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.algosniper.com/buy-and-sell-indicator.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.
