COSTRINITY Assessment API

The assessment API from COSTRINITY — 6 operation(s) for assessment.

GitHub OpenAPI

Operations 6

POST /api/engage/start Door 2: start a fixed-scope assessment engagement without a call #
POST /api/engage/accept Accept the scope agreement. #
POST /api/engage/intake Return the intake questionnaire. #
POST /api/webhooks/cal cal.com booking webhook. Creates an engagement and sends the pre-call packet #
POST /api/webhooks/paypal PayPal webhook. #
GET /api/cron/engage-chase Deposit chase, day 3 and day 7 after acceptance, then never. #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/costrinity-xyz:costrinity-xyz-assessment-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

costrinity-xyz-assessment-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: VITNA API (Phase 1) Assessment 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: Assessment
paths:
  /api/engage/start:
    post:
      summary: 'Door 2: start a fixed-scope assessment engagement without a call'
      tags:
      - Assessment
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - companyLegalName
              - contactName
              - contactEmail
              properties:
                companyLegalName:
                  type: string
                contactName:
                  type: string
                contactEmail:
                  type: string
                  format: email
      responses:
        '200':
          description: '{ok:true, next} where next is the signed scope-agreement URL'
        '400':
          description: company, name and email are all required; malformed email
        '429':
          description: IP rate limited (5 / 15 min)
        '503':
          description: SALES_ENABLED is false, or links cannot be signed
      operationId: postApiEngageStart
      x-operation-id-source: derived
  /api/engage/accept:
    post:
      summary: Accept the scope agreement.
      tags:
      - Assessment
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - e
              - t
              - clientLegalName
              - clientAddress
              - name
              - title
              - agreed
              properties:
                e:
                  type: string
                  format: uuid
                t:
                  type: string
                  description: signed engage token, purpose "agreement"
                clientLegalName:
                  type: string
                clientAddress:
                  type: string
                name:
                  type: string
                title:
                  type: string
                agreed:
                  type: boolean
                  enum:
                  - true
      responses:
        '200':
          description: '{ok:true, invoiceUrl, checkoutUrl} — either may be null if PayPal was unreachable'
        '400':
          description: incomplete link, or named missing fields
        '403':
          description: token invalid or expired
        '409':
          description: already accepted, or not in a state that accepts a signature
        '410':
          description: engagement cancelled
        '429':
          description: IP rate limited (10 / 15 min)
        '503':
          description: SALES_ENABLED is false, or the write failed; nothing recorded
      operationId: postApiEngageAccept
      x-operation-id-source: derived
  /api/engage/intake:
    post:
      summary: Return the intake questionnaire.
      tags:
      - Assessment
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - e
              - t
              - intake
              properties:
                e:
                  type: string
                  format: uuid
                t:
                  type: string
                  description: signed engage token, purpose "intake"
                intake:
                  type: object
                  description: company, systems[], controls, pressure, access — see lib/intakeSchema
      responses:
        '200':
          description: '{ok:true, answered, total}'
        '400':
          description: no AI systems listed
        '403':
          description: token invalid or expired
        '409':
          description: the questionnaire is closed (delivered or cancelled)
        '429':
          description: IP rate limited (30 / hour)
      operationId: postApiEngageIntake
      x-operation-id-source: derived
  /api/webhooks/cal:
    post:
      summary: cal.com booking webhook. Creates an engagement and sends the pre-call packet
      tags:
      - Assessment
      description: Authenticated by HMAC-SHA256 over the raw body in x-cal-signature-256. Always 200 once the signature verifies, because cal.com retries a non-2xx.
      responses:
        '200':
          description: acknowledged; body says whether an engagement was created
        '400':
          description: invalid JSON
        '401':
          description: signature missing or wrong
        '503':
          description: CAL_WEBHOOK_SECRET is not configured
      operationId: postApiWebhooksCal
      x-operation-id-source: derived
  /api/webhooks/paypal:
    post:
      summary: PayPal webhook.
      tags:
      - Assessment
      description: Handles PAYMENT.CAPTURE.COMPLETED and INVOICING.INVOICE.PAID. Verified by asking PayPal via /v1/notifications/verify-webhook-signature, so a verification that could not be performed returns 503 and is redelivered rather than accepted.
      responses:
        '200':
          description: acknowledged; body says whether the settlement matched and moved
        '400':
          description: invalid JSON
        '401':
          description: PayPal rejected the signature
        '503':
          description: PayPal unconfigured, PAYPAL_WEBHOOK_ID unset, or verification unavailable
      operationId: postApiWebhooksPaypal
      x-operation-id-source: derived
  /api/cron/engage-chase:
    get:
      summary: Deposit chase, day 3 and day 7 after acceptance, then never.
      tags:
      - Assessment
      parameters:
      - name: dry
        in: query
        schema:
          type: string
          enum:
          - '1'
        description: decide and report, send nothing
      responses:
        '200':
          description: '{considered, due, sent, failures}'
        '401':
          description: missing or wrong CRON_SECRET bearer
      operationId: getApiCronEngageChase
      x-operation-id-source: derived
components:
  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.