> For the complete documentation index, see [llms.txt](https://kreioslabsdocs.gitbook.io/kreioslabs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kreioslabsdocs.gitbook.io/kreioslabs/how-tos/how-to-use-setup-cards/pullback-setup.md).

# Pullback Setup

#### PARAMETERS

Price makes a pullback below short-term MA but still above mid-term MA, usually good coins here resemble bull flags.

#### EXAMPLE

This is a trade I personally took, FTM (H4). The arrow represents the time where KreiosLabs classified it as a pullback setup. As you can see usually, there's a big impulse followed by a pullback resembling a bull flag.\
\
There will be some coins that KreiosLabs will classify as pullback but won't look like this—it's better to avoid those. Focus on recognizing what good pullback coins look like and use that as a filter.

If in the case there are multiple coins under Pullback, you can **sort** them by RSI, %change, or volume traded or **filter** them by Top 10 daily gainers or Top 20 weekly gainers.

<figure><img src="/files/1suSiRYxz34r7DrcgObA" alt=""><figcaption><p>FTM 4h Chart</p></figcaption></figure>

#### TIPS

Check the coins listed under this setup on the **DAILY** timeframe, stalk the strongest coins, and play them on a lower time frame using different setups (momentum, pullback, etc) on the next coming days.&#x20;

#### REMARKS

{% hint style="warning" %}
You may notice that sometimes the coin is not even in a pullback.
{% endhint %}

Yes, this happens sometimes. You still need to check if the coin in pullback setup looks good. The screener will mechanically detect a pullback based on moving averages and not discretion. So ideally, look at the coins the screener tells you and then apply filter / sort and then decide.


---

# 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://kreioslabsdocs.gitbook.io/kreioslabs/how-tos/how-to-use-setup-cards/pullback-setup.md?ask=<question>&goal=<endgoal>
```

`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.