Detector API reference

Overview

Detector is the signal engine. Public clients use Detector capabilities through Provider, not through direct Detector URLs or downstream route inventories.

Public Capabilities

Provider may expose Detector-facing capabilities such as:

• Detector health and active-state visibility.
• Signal summaries and signal history.
• Strategy and instance diagnostics.
• Performance summaries.
• Provider-owned risk or operator actions that are explicitly published.

Use Provider OpenAPI for exact methods, route names, query parameters, request bodies, and response shapes.

Plugins

Detector plugin endpoints are compatibility/runtime surfaces only when Provider publishes them explicitly. Public plugin documentation should use Provider-owned plugin routes.

Real-Time Data

For real-time signal updates, use Provider WebSocket and the current Provider event catalog. You do not need to connect to Detector or an internal event bus.

Next Steps

• Provider API reference
• Building with the API