> 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/smart-money.md).

# smart money

Key support and resistance levels where institutional players are active

The Smart Money component maps out the exact price zones where the biggest players in the market — institutions, whales, and large funds — are buying and selling. These aren't arbitrary levels. They're where the real money moves.

### The two zones

Red zones

Areas where large players are selling. These act as resistance — price approaching a red zone is likely to face rejection and reverse downward.

Green zones

Areas where large players are buying. These act as support — price pulling back into a green zone is likely to hold and reverse upward.

### How to trade them

Resistance

Price rallies into a red zone — look for a short entry or take profit on existing longs. The zone is where sellers step in aggressively.

Support

Price pulls back into a green zone — look for a long entry or add to existing longs. The zone is where buyers absorb selling pressure.

Breakout

If price closes convincingly through a zone, the level has flipped. A broken red zone becomes support. A broken green zone becomes resistance. Adjust your bias accordingly.

Confluence

The highest-probability setups occur when a Smart Money zone aligns with the Sniper Cloud midline or the Super Trend. Multiple layers of confluence = higher conviction entry.

### Key principles

Don't enter blindly at a zone — wait for a reaction. Let price show you a rejection candle or a reclaim before committing to a position.

The wider the zone, the more significant the level. A thick red or green band means there is heavy institutional activity at that price range — treat it with more weight than a thin zone.

Use Smart Money zones as your map. Before entering any trade, identify the nearest red zone above and green zone below. That gives you your targets and your invalidation levels before you even enter.

<figure><img src="https://3541426626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaJ7Vv6oQJL7Ywy4bmbsR%2Fuploads%2FIO04kfEo2MUAZIIyo9fe%2FBTCUSDT.P_2025-06-29_21-30-17.png?alt=media&amp;token=21e6e225-7486-461f-b79c-851cbde2af0f" alt=""><figcaption></figcaption></figure>


---

# 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/smart-money.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.
