Detector Installation

After Provider is running, Detector can be attached as the signal-generation service. Detector analyzes Provider-owned market data, evaluates strategy rules, and makes signal context available to Advisor, Inspector, Studio, and API clients through Provider.

What Detector Does

• evaluates configured strategies and indicators;
• produces structured signal context;
• registers behind Provider for health and proxy access;
• leaves public and Studio access on the Provider gateway.

Configuration

Use the current Detector configuration template from the trading workspace or deployment bundle. Configure:

• Provider endpoint and auth using the current deployment secret names;
• runtime network access to Provider and required infrastructure;
• enabled strategies and plugins;
• health/heartbeat settings expected by Provider.

Do not publish tokens, private runtime URLs, or internal channel names in shared docs or screenshots.

Verification

Use Provider health, Provider OpenAPI, and the Provider proxy target list to confirm Detector is registered and healthy. In Studio, Detector should appear as an available runtime target with recent heartbeat data.

For current routes, use Provider API reference and Detector API reference.