Readiness probe for Kubernetes and orchestration systems

Returns 200 when the service is fully configured and ready to handle traffic. Returns 503 with a list of issues when the service is degraded or not ready…

GET /ready

cURL

curl --request GET \
  --url 'https://api.nsr.stateset.com/ready' \
  --header "X-API-Key: $STATESET_NSR_API_KEY"

200

{
  "issues": [
    "string"
  ],
  "ready": true,
  "status": "pending",
  "version": "2026-08-01",
  "warnings": [
    "string"
  ]
}

Returns 200 when the service is fully configured and ready to handle traffic. Returns 503 with a list of issues when the service is degraded or not ready. Checks Performed

• API keys are configured (production safety)
• Persistence is configured (data safety)
• Database is reachable when NSR_DATABASE_URL is configured
• Engine is initialized and operational Example

curl -X GET 'https://api.nsr.stateset.com/ready'

Response

ReadyResponse

issues · string[]

List of issues blocking readiness

ready · boolean · required

status · string · required

ready | degraded

version · string · required

warnings · string[]

Status codes

Code	Meaning
200	Service is ready to receive traffic
503	Service is not ready

cURL

curl --request GET \
  --url 'https://api.nsr.stateset.com/ready' \
  --header "X-API-Key: $STATESET_NSR_API_KEY"

200

{
  "issues": [
    "string"
  ],
  "ready": true,
  "status": "pending",
  "version": "2026-08-01",
  "warnings": [
    "string"
  ]
}