COSTRINITY Billing API

The billing API from COSTRINITY — 4 operation(s) for billing.

GitHub OpenAPI

Operations 5

POST /api/upgrade/paypal/order Create the PayPal order for a Pro or Team plan, for the signed-in owner (since… #
POST /api/upgrade/razorpay/order Create Razorpay INR order (DPDP-IN owners). #
POST /api/webhooks/razorpay Razorpay payment webhook #
GET /api/licenses/mine The signed-in owner's VITNA Desktop licence key #
POST /api/licenses/mine Create the licence key ({ "create": true }) or regenerate it ({ "regenerate"… #

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-billing-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-billing-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: VITNA API (Phase 1) Billing 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: Billing
paths:
  /api/upgrade/paypal/order:
    post:
      summary: Create the PayPal order for a Pro or Team plan, for the signed-in owner (since…
      description: 'Body { plan: "pro" | "team", currency?: "USD" | "CAD" }; nothing else is read, and never a price. The currency is the account''s lock (the currency of its first PayPal payment), else the switch (currency, else the vitna_currency cookie), else the region (x-vercel-ip-country CA is CAD, anything else USD). The server creates the order with its own credentials at the price table''s price in that currency (USD: Pro 29.00, Team 79.00; CAD: Pro 15.00, Team 40.00), with a sealed reference to the account, plan and currency in custom_id, and answers { id, currency, value } for PayPal''s buttons; the reference is never in the answer. Signed-in owner only: an API key in any header form is refused 403 session_required.'
      tags:
      - Billing
      security:
      - Session: []
      responses:
        '200':
          description: '{ id, currency, value }'
        '400':
          description: A plan other than pro or team, or a currency other than USD or CAD
        '401':
          description: 'no_session: nobody signed in'
        '403':
          description: 'session_required: an API key; or origin_rejected: not from our own page'
        '409':
          description: 'currency_locked: the currency asked for is not the one the account pays in'
        '429':
          description: More than 20 orders in 10 minutes from one network
        '503':
          description: 'checkout_unavailable (PAYPAL_MERCHANT_ID unset or malformed, PayPal or the database unavailable, or an order PayPal made for another payee or without naming its payee), or needs_migration (Canadian dollars before migration 0032: "Paying in Canadian dollars opens shortly.")'
      operationId: postApiUpgradePaypalOrder
      x-operation-id-source: derived
  /api/upgrade/razorpay/order:
    post:
      summary: Create Razorpay INR order (DPDP-IN owners).
      tags:
      - Billing
      security:
      - Session: []
      responses:
        '200':
          description: Order created
        '503':
          description: Skip-mode — Razorpay env triple not configured
      operationId: postApiUpgradeRazorpayOrder
      x-operation-id-source: derived
  /api/webhooks/razorpay:
    post:
      summary: Razorpay payment webhook
      tags:
      - Billing
      parameters:
      - name: x-razorpay-signature
        in: header
        schema:
          type: string
      responses:
        '200':
          description: OK
        '401':
          description: Signature invalid
      operationId: postApiWebhooksRazorpay
      x-operation-id-source: derived
  /api/licenses/mine:
    get:
      summary: The signed-in owner's VITNA Desktop licence key
      description: 'Signed-in owner only. A request carrying an API key (any header form, a restricted trial key included, even beside a session cookie) is refused 403 session_required and nothing is read. VITNA Desktop does not call this route: it activates a pasted key with POST /api/licenses/activate.'
      tags:
      - Billing
      security:
      - Session: []
      responses:
        '200':
          description: '{ license_key, tier, expires_at } or { license_key: null }'
        '403':
          description: session_required
        '500':
          description: 'The key could not be read; never answered as { license_key: null }'
      operationId: getApiLicensesMine
      x-operation-id-source: derived
    post:
      summary: 'Create the licence key ({ "create": true }) or regenerate it ({ "regenerate"…'
      description: 'Signed-in owner only, as GET. A request carrying an API key is refused 403 session_required before anything is minted or revoked. create returns the key the account already has if it still works (created: false) and otherwise mints one, revoking only an expired key; it is not emailed. regenerate mints a fresh key and revokes the old one; emailed says whether it also went out by email. The key ends with the latest active paid period, or after 30 days when there is none; an owner whose plan the expiry sweep never ends (plan_override_reason) always gets 30 days.'
      tags:
      - Billing
      security:
      - Session: []
      responses:
        '200':
          description: '{ license_key, tier, expires_at, created, emailed }'
        '400':
          description: No paid plan, or nothing to do
        '403':
          description: session_required
        '409':
          description: 'plan_ended: the paid period is over and the daily sweep has not yet ended the plan; nothing is minted or revoked'
      operationId: postApiLicensesMine
      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.