strategy-values

To build JSON value expressions for trading bot strategy filters, you must map specific value types—such as literals, indicator reads, and bot state globals—using a structured syntax that defines required fields and return types like Float, Direction, or String.

Available value types for real-time analysis signals include literals, bot state globals, variables, indicator reads, position and order reads, chart-level checks, and computed expressions, each returning specific categories like Float, Direction, or Chart.

Constructing a TP/SL formula involves combining Math, Pick, and Indicator value types into a single computed JSON expression, ensuring each nested object specifies its required fields and return types for the strategy engine to parse.

Yes, you can combine bot state globals and variables within the same JSON expression for risk management, utilizing computed expressions to evaluate arithmetic and analysis-derived signals while returning valid Float or String data types.

Strategy value expressions fail when optional indicator reads return None because the JSON schema requires safe usage notes, meaning you must implement guards for optional None results to prevent unexpected processing errors in your filters.

Yes, strategy-values supports chart-level checks and order type reads by providing a complete reference for constructing JSON expressions, specifying the exact JSON shape required to execute these actions within automated trading strategies.