> For the complete documentation index, see [llms.txt](https://cs-ai.gitbook.io/coinscreener.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cs-ai.gitbook.io/coinscreener.ai/platform-features/signals.md).

# Signals

## Trading Signals

Maximize your trading opportunities with signals produced through advanced technical analysis & AI algorithms which could help you Increase profitability, reduce risk and avoid emotional trading.

<figure><img src="https://lh6.googleusercontent.com/SDsbSeDE04W4wSsLHZiSI7bnWDzxfBGfR8g-n5SC6LKHvR9ldpXIKu9x9sLWgRnF13Ucc3jOv87aFvmP7SKyo_M2frKxxJrvdgOpFBiz2AUftvEzFPXBtrwYjxdMsr13Ld6wChIxNW0nHhOuDu4oRc0Sl4HK_eEN0xK1n3d6FkbV_NfCdz0Emzi7xOvI" alt=""><figcaption></figcaption></figure>

### 1. Display Open Signals

When the pro user logs in and navigates Open Signals from the left side navigation, open signals will be displayed in a table on the right screen, with the following information:&#x20;

● Positions (Long/Short)

● Market

● Entry price

● Target 1

&#x20;     ○ Target Price.

&#x20;     ○ Target Risk: Reward ratio (R:R)

&#x20;     ○ Target Return on Investment (ROI)

● Target 2

&#x20;     ○ Target Price.

&#x20;     ○ Target Risk: Reward ratio (R:R)

&#x20;     ○ Target Return on Investment (ROI)

● Stop Loss price.

● Time - when the open signal was created.

<figure><img src="https://lh6.googleusercontent.com/NuEEIXa_BPv1oZuzuQwLw_ErF9E0aobl3W-RHoSF1Xd_da8qiLAMr_QvI4xJHjVBXELjZRCuD6SUYWAB441QAY8CVvlAThth0_AZJo4WJADgMMjTTL_Ktb7zVVMosNGg9IRZgZwSyjFAM20vHiXWivllXBcOgB5MiqFcQgFVvabmgQXVmOKGFFPn22yX" alt=""><figcaption><p>Open Signals are only available for users in Pro plan. These Open signals are system-generated, running to reach targets.</p></figcaption></figure>

### 2. Display History Signals

These History Signals are available for all users including visitors. History Signals show closed signals which hit take-profit or stop loss.

**● Take-profit hit:**

&#x20;     ○ Signals reach at least target 1.

&#x20;     ○ Signals that reach target 1 and hit stop-loss will still be categorized as take-profit hits.

&#x20;     ○ Signals reach target 2 will auto-be closed and categorized as a take-profit hit.

**● Stop-loss hit:**

&#x20;     ○ Signals haven't reached any targets and have been closed due to a stop-loss hit.

When the users navigate History Signals from the left navigation, closed signals will be

displayed in a table on the right screen, with the following information:

● Positions (Long/Short)

● Market

● Result (Take-profit Hit/Stop-loss Hit)

● Entry price

● Target 1

&#x20;     ○ Target Price

&#x20;     ○ Target Risk: Reward ratio (R:R)

&#x20;     ○ Target Return on Investment (ROI)

● Target 2

&#x20;     ○ Target Price

&#x20;     ○ Target Risk:Reward ratio (R:R)

&#x20;     ○ Target Return on Investment (ROI)

● Stop Loss price

● Closed Time

<figure><img src="https://lh3.googleusercontent.com/DNLHJfLbyTz31T1E8o4yVTGKHdw7YziUhUl3BwRcyTivUGwXYmWC-66BvnGKqfUxuARODo8TtgvD2NIAZ_8wa7p9dUi4J9RhDtyRzRZkldpEMo3YlQZFMm8nFQCZdcUNl2Jyao8n8aFSIRiTeZIVwMNwWBbH-RfHCUfBGtpZj-kYN-cs4rOKmtCV71X_" 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 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://cs-ai.gitbook.io/coinscreener.ai/platform-features/signals.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.
