GET /health — NSP Daemon Liveness Probe Endpoint - NSP

The /health endpoint tells you whether the NSP daemon is running and ready to serve requests. It requires no authentication and returns immediately — making it safe to use from monitoring systems, load balancers, container health checks, and CI pipelines. Call it before any other endpoint to confirm the daemon is up before your agent begins work.

Endpoint

GET /health

No X-Substrate-Key header is required.

Response

{
  "status": "ok",
  "version": "1.0.0",
  "uptime_secs": 7200,
  "tracked_processes": 4,
  "auth_enabled": true
}

string

Always "ok" when the daemon is healthy and accepting requests.

string

Semantic version of the running NSP daemon, for example "1.0.0".

integer

Number of seconds elapsed since the daemon process started.

integer

Number of application processes the daemon is currently tracking. A value of 0 is valid — it means no apps have been attached yet.

boolean

true when API key authentication is enforced on all other endpoints. If false, the daemon is running in an unauthenticated development mode.

Examples

curl http://127.0.0.1:7842/health

# ping() never raises — it returns True if the daemon is up, False otherwise
is_up = await client.ping()

if not is_up:
    raise RuntimeError("NSP daemon is not running")

Error Responses

Status	Description
`503`	The daemon process is not running or is not yet ready to serve requests.

Endpoints

Data Models

GET /health — NSP Daemon Liveness Probe Endpoint

Endpoint

Response

Examples

Error Responses

​Endpoint

​Response

​Examples

​Error Responses

Endpoint

Response

Examples

Error Responses