FAQ

Frequently asked questions

Browse through these FAQs to find answers to commonly asked questions.

faq boy with logos

A signal is defined by one or more indicators, and a set of conditions or rules.

For example, you can set up a signal that looks at the RSI indicator, with the condition RSI crosses above 70. When the RSI crosses above 70, the signal is triggered.

Another example is a signal that looks at 2 Exponential Moving Averages, with the condition EMA 20 crosses above EMA 50. When the EMA 20 crosses above the EMA 50, the signal is triggered.

A monitor is a 'scanner' that looks at a signal, and sends you notifications when the signal is triggered by an asset.

Monitors looks a different tickers. This is defined by a group of assets. In crypto this might be all USDT pairs on Binance. Or it might be an index, such as the S&P 500.

A monitor will thus scan these assets for signals, and when a signal is triggered, you will receive a notification.

Shortlists are a way to make 'shorter' 'lists' out of asset groups. For example, you might want to shorten the S&P 500 list down to only assets where the EMA20 is above the EMA50. Thus indicating a bullish trend. A monitor can then 'scan' this shorter list and send notifications when signals are triggered.

A scanner is something that iterates over a list of assets and looks for signals.

A scanner can either be a monitor or a shortlist.

A notification is a message that is sent to you when a signal is triggered.

Notifications can be sent via email, Telegram, Slack or Webhook.

A Webhook is a way to send notifications to a custom URL. You can use Webhooks to to trigger custom actions on your own server or app when a signal is triggered.

For example, you can create a Webhook that notifies your own server when a signal is triggered. Your server can then take further actions, for example, place a trade on an exchange.

The 'scan rate' dictates how many tickers / time unit we will scan the markets for signals. 20 tickers / minute means that we will scan 20 tickers per minute for signals.

For example, if you have a monitor that scans 100 tickers, it will take 5 minutes to scan all the tickers for signals.

If you have a monitor that scans 1000 tickers, it will take 16.7 minutes to scan all the tickers for signals at the rate of 1 ticker / second.

500 tickers / 60 tickers per minute = 8.3 minutes
For additional information, please Contact Us