Your trading rule, in plain English, tested before it is saved.
Build a signal with the visual builder, write it in NexusScript, or describe it to Nexus. You see the rule in plain English, where it fired on recent bars and a backtest net of costs. Nothing is saved until you confirm.
“Buy when RSI crosses up through 30 while price is above the 200-day EMA, 2 ATR stop.”
Buy (long) on 1d bars when RSI crosses above 30 and close is above the 200 EMA. Stop: 2 × ATR(14). Target: 2 × the risk. Exit after 20 bars at the latest.
A language that can’t run code.
NexusScript compiles to the same safe, declarative rules as the visual builder: a fixed list of indicators, comparisons, stops and targets. There is no eval, no imports and no loops — your rule is data, never a program.
// NexusScript compiles to a signal spec; it is never executed as code. signal rsi_reversal_long "RSI oversold bounce above the 200 EMA" timeframe 1d side long let rsi = rsi(length=14) let trend = ema(length=200) when rsi crosses above 30 and close > trend stop atr(mult=2, length=14) target r(2) hold 20
Earned, not assumed.
Ask Nexus to draft
Markers on the chart
Backtest net of costs
Saved only when you confirm
Versioned
Autopilot after 14 days on paper
Build your first signal on paper.
Set a goal, see whether it’s realistic, and watch AlgoNexus work with simulated money first. No card needed for the 14-day trial.