GET /api/health - Sector8

Request

GET /api/health HTTP/1.1
Host: sdkapi.sector8.ai

No request body or authentication headers are required. Public examples use the production host. Use the endpoint issued to your environment.

Use /api/health for external checks and load balancer probes. The service also exposes /health, but /api/health is the stable public path used in deployment verification.

Health proves the gate endpoint is reachable and configured. It does not prove a customer app is protected. Enforcement is proven only by a routed evaluate call that the application honors before dispatch.

Response

{
  "status": "healthy",
  "service": "running",
  "database": "healthy",
  "timestamp": "2026-03-22T15:35:30.652651+00:00",
  "policy_version_id": "v7.0-phase2",
  "invariants_active": 7,
  "phase": "2",
  "capabilities": {
    "admission_controller": true,
    "multi_turn_analyzer": true,
    "semantic_engine": true,
    "pre_filter": true,
    "output_compliance": true,
    "file_scanner": true,
    "rag_integrity": true,
    "memory_integrity": true,
    "guard_mcp_server": true
  }
}

Response fields

Field	Type	Description
`status`	string	Service health status. Healthy deployments return `"healthy"`.
`service`	string	Runtime state, typically `"running"`.
`database`	string	Database connectivity state, typically `"healthy"` or `"unhealthy"`.
`timestamp`	string	UTC timestamp for the health response.
`policy_version_id`	string	Active policy version or runtime policy identifier loaded by the gate.
`invariants_active`	number	Number of active invariants. Healthy production deployments should report `7`.
`phase`	string	Active rollout phase for the service.
`capabilities`	object	Boolean flags for major gate capabilities.

If health fails, or invariants_active is less than 7, treat the deployment as degraded and do not route live actions until the gate is healthy again.

See Evaluate for the enforcement contract and Quickstart for the first routed evaluate-before-dispatch proof.