Service and system
Confirm readiness and discover the environment in which Insight is running. These endpoints expose logs, optional tool availability, Neat component status, platform build metadata, and the LAN address inferred for browser-facing links.
Check service readiness
A lightweight readiness probe that also reports the startup-scoped browser network configuration applied to vf and MediaMTX. Call this first from automation; a `200` response confirms that the Flask backend can accept subsequent API requests. A present but invalid `browser-ice-address` configuration prevents Insight from starting. A full HTTP(S) `launch-url` is reduced to its origin; an invalid launch URL preserves legacy request-host/port-map URL generation.
Read recent service log lines
Reads a bounded tail of a whitelisted system log without exposing arbitrary filesystem paths. Use `EV74` for accelerator/runtime messages and `syslog` for broader platform diagnostics; the response is plain text rather than JSON.
Check optional media tools
Reports whether the helper executables used for probing, transcoding, and streaming are available on the backend `PATH`. This is a capability check only; a reported tool may still fail for an unsupported codec or input.
Get Neat system and component status
Runs the Neat system-information command and enriches its structured result with Insight URL and port data. Use it for a broad installation snapshot; use the diagnostics endpoints for live transport-level investigation.
Get deployment environment flags
Identifies whether Insight is running directly on a SiMa DevKit and whether a remote DevKit was configured through the environment. Frontends use these flags to select appropriate workflows and messaging; this endpoint does not modify deployment configuration.
Get local or remote platform build information
Returns parsed SiMa release and platform metadata for the active environment. On a remote-DevKit installation the backend retrieves the target's build information; without a DevKit it falls back to host platform details. A `502` generally means the configured remote target could not be reached or read.
Get the browser-reachable backend IP
Resolves the address that browser-facing links should use, preferring `CONTAINER_HOST_IP`, then an inferred LAN address, and finally `127.0.0.1`. This is intended for URL construction in container and bridge-network deployments, not as a complete network-interface inventory.