COSTRINITY Health API

openapi: 3.2.0
info:
  title: VITNA API (Phase 1) Health API
  version: 1.1.0
  description: 'The compliance evidence layer for AI agents. Pre-flight compliance checks agents call before they act (consent, breach reportability, EU AI Act classification, cross-border), and audit-grade, signed records of what they did. Phase 1 surface covers region routing labels (one database region is in use today), DPIA/ROPA generation, Data Subject Rights (scoped: answerable only for events linked to a subject via principal_ref at ingest, from the point linkage begins; earlier events are permanently unattributable and cannot be linked retroactively), consent lifecycle, Sahamati AA integration, breach notification, and INR/Razorpay billing for DPDP-IN owners (switched off pending merchant onboarding). Also includes one-command agent self-provisioning (/api/setup, mints a restricted trial key with no signup), a destructive-action safety pre-flight (/api/preflight/action-check), scoped engagement sessions with signed evidence bundles (/api/engagement/*), and account claim by a person, from the claim link (/claim).'
  contact:
    name: COSTRINITY
    email: dpo@costrinity.xyz
    url: https://www.costrinity.xyz/
  license:
    name: Proprietary
    url: https://vitna.costrinity.xyz/terms
servers:
- url: https://vitna.costrinity.xyz
  description: Production
- url: https://vigil-staging.vercel.app
  description: Staging (preview branch)
tags:
- name: Health
paths:
  /api/health/regions:
    get:
      summary: List provisioned Supabase regions
      tags:
      - Health
      responses:
        '200':
          description: OK
      operationId: getApiHealthRegions
      x-operation-id-source: derived
  /api/health/phase1:
    get:
      summary: Phase 1 readiness probe
      tags:
      - Health
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Phase1Health'
      operationId: getApiHealthPhase1
      x-operation-id-source: derived
components:
  schemas:
    Phase1Health:
      type: object
      properties:
        ok:
          type: boolean
        phase:
          type: string
          enum:
          - '1'
        generated_at:
          type: string
          format: date-time
        required:
          type: object
          properties:
            primary_supabase_reachable:
              type: boolean
            cron_secret_configured:
              type: boolean
            resend_configured:
              type: boolean
        optional:
          type: object
          properties:
            dpia_snapshots_migration_applied:
              type: boolean
            razorpay_configured:
              type: boolean
            sahamati_strict_mode:
              type: boolean
            regions_provisioned:
              type: array
              items:
                $ref: '#/components/schemas/RegionId'
        surface:
          type: object
          additionalProperties:
            type: array
            items:
              type: string
    RegionId:
      type: string
      description: A routing label stored on the account, not a place. 'us-east-1' labels the primary database project, which runs in AWS us-west-2 (Oregon, USA). No ap-south-1 or eu-west-1 database is provisioned today, so every account's data is stored in the primary. The generated documents print where the data is, not the label.
      enum:
      - us-east-1
      - ap-south-1
      - eu-west-1
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: x-vigil-key
      description: 'Per-agent API key. Format: vitna_<64-char-hex>; legacy vigil_ keys remain valid. Send on /api/ingest.'
    Bearer:
      type: http
      scheme: bearer
      bearerFormat: vitna_<key> (legacy vigil_<key> accepted)
      description: 'Same key as x-vigil-key, sent as `Authorization: Bearer <key>`.'
    Session:
      type: apiKey
      in: cookie
      name: vigil_session
      description: 'Operator dashboard session cookie. Set by a sign-in: the second step of a password sign-in (/api/auth/verify-pin), or, for an address whose mail Google handles (Gmail or a Google Workspace domain) while VITNA''s mail cannot reach Gmail, the password alone (/api/owners); GitHub; a passkey; or a claim.'
    CronSecret:
      type: http
      scheme: bearer
      description: Bearer ${CRON_SECRET}. Only the Vercel cron infrastructure should hold this.