hot-monitor

Querying AI hot topics via HTTP API bypasses the web dashboard by sending direct HTTP requests to the local hot-monitor service. The system automatically probes ports 8000 and 8001 to discover the active service and returns filtered, sorted topic lists as structured output.

Managing platform account monitoring through API calls allows you to add, enable, disable, and delete keyword and account rules programmatically. You can also view hit records directly, eliminating the need for manual frontend interaction.

Local service discovery for HTTP API monitoring uses dual-port probing to automatically detect the active hot-monitor service. By probing both port 8000 and 8001, the system ensures seamless connection to the local backend without manual port configuration.

You do not need a specific port configured to trigger a manual hot topic scan task. The system supports automatic port detection for both 8000 and 8001, and uses idempotent scan triggering to prevent duplicate tasks from being created.

Securely updating system scan and notification settings via API involves sending HTTP requests to modify scan intervals, notification thresholds, API keys, and SMTP settings. The API ensures sensitive configuration fields are handled securely during transmission and storage.

Idempotent scan triggering matters for AI hot topic monitoring because it prevents duplicate scan tasks from executing when multiple API requests are sent. This ensures system stability and avoids redundant processing during automated polling or retry scenarios.