whoisgeni-us Health API

openapi: 3.2.0
info:
  title: WhoisGenius Health API
  description: 'Domain intelligence platform with AI-powered operator attribution Responses are JSON by default; request the compact, token-efficient TOON format with the `Accept: application/toon` header.'
  version: 0.1.0
tags:
- name: Health
paths:
  /health:
    get:
      tags:
      - Health
      summary: Health Check
      description: Basic health check -- always returns ok if the service is running.
      operationId: health_check_health_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties:
                  type: string
                type: object
                title: Response Health Check Health Get
  /version:
    get:
      tags:
      - Health
      summary: Version
      description: 'Build provenance probe (SRE W3-7).


        Reports the git SHA this image was built from (injected as GIT_SHA into the

        task definition at deploy time). The deploy pipeline polls this endpoint

        until the reported SHA matches the commit being deployed, replacing the

        ad-hoc ``curl /health`` warmup loops — a 200 from a still-draining OLD task

        can no longer satisfy readiness and mask a regression or trigger a false

        rollback. Exposes only a commit hash (no internal architecture details).'
      operationId: version_version_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties:
                  type: string
                type: object
                title: Response Version Version Get
  /health/ready:
    get:
      tags:
      - Health
      summary: Readiness Check
      description: 'Readiness check -- verifies database and Redis connectivity.


        Returns only aggregate status publicly. Individual collector names

        and their enabled/disabled state are intentionally omitted to avoid

        leaking internal architecture details to unauthenticated callers.'
      operationId: readiness_check_health_ready_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Readiness Check Health Ready Get
  /health/auth:
    get:
      tags:
      - Health
      summary: Auth Pipeline Check
      description: 'Auth pipeline health check -- tests JWKS fetch, DB, full auth readiness.


        Exercises the real JWKS HTTP endpoint that ``decode_cognito_token`` uses

        (not just the boto3 ``describe_user_pool`` that ``/health/ready`` tests).

        This catches NAT Gateway latency, JWKS endpoint unreachability, and

        DNS resolution failures that would cause ``Failed to fetch`` in browsers.'
      operationId: auth_pipeline_check_health_auth_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Auth Pipeline Check Health Auth Get
components:
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer