SignalVortex memberships are available now— Signals, intelligence, and automation across multiple markets.
Documentation

Set up SignalVortex with a controlled, paper-first process.

A practical overview of installation, Discord monitoring, parser setup, safeguards, and testing.

Getting started

SignalVortex is designed to keep monitoring off until the user intentionally starts it. Complete setup in small, testable stages instead of connecting every feature at once.

Install → Verify access → Sign into Discord → Add one channel → Configure parsing → Connect paper broker → Test → Expand

1. Sign into Discord

Open the embedded Discord login from the Copy Trading / Monitor page. Sign in using the normal Discord login flow. Complete two-factor authentication when requested. SignalVortex does not require you to paste a Discord user token.

2. Add monitored channels

Add the Discord channel ID for each supported source. Begin with one row, save it, confirm the app can locate the channel, and then start that row. SignalVortex should wait for new messages instead of reading old history as new activity.

  • Each row can be started and stopped independently.
  • Discord must be logged in before a monitor starts.
  • The app should remain responsive while monitoring multiple channels.
  • Detected but unapproved messages should still be visible in activity status.

3. Configure AI parsing

Add your supported AI API key and select a compatible model. Use the built-in connection test before starting a live monitor. Keep the key private and remove it from diagnostic bundles.

4. Connect paper brokerage

Connect the supported paper-trading account first. Confirm account detection, quotes, option contracts, and order permissions. Do not assume that a successful connection means every alert type has been tested.

5. Review safeguards

  • Duplicate Order Protection
  • Avoid Stacking Same Ticker
  • Double-Down Protection
  • Maximum trade size
  • Slippage tolerance
  • Trade-management rules for trims and exits

6. Test the entire lifecycle

Use controlled paper tests for a single call, single put, call spread, put spread, trim, full exit, duplicate alert, same-ticker block, missing broker connection, invalid message, and update/restart flow.