Quantum Nexus White Label API

The White-label API from Quantum Nexus — 1 operation(s) for white-label.

GitHub OpenAPI

Operations 2

GET /api/v1/branding Returns the white-label configuration of the calling API key #
PUT /api/v1/branding Update the white-label configuration #

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/nexusquantum-legal:nexusquantum-legal-white-label-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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

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

OpenAPI Specification

nexusquantum-legal-white-label-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Nexus Legal White Label API
  version: 1.95.0
  description: 'Multi-jurisdictional legal analysis API with a multi-agent architecture and Zero Retention. ## Output language


    `language` (and the language implied by the jurisdiction) sets the language the text is written in. For `es` and `en` the delivered text is also measured: when a substantial part of it came back in the other of the two, a block headed `⚠️ LANGUAGE OF THIS REPORT` (`⚠️ IDIOMA DE ESTE INFORME` when `es` was requested) is added at the end of the text. It works the same with any engine, BYO included. - **When there is no block**: it is not a confirmation. Other languages are not measured, and neither is a text too short or too mixed to tell. - **With BYO**: how closely the output follows the request depends on your engine. - **If the output language is essential to your workflow**: check it on your side against the `analysis` string. ## The verdict travels INSIDE the text — read this before you parse a response


    Every string this API returns that a lawyer reads — `analysis`, `answer`, `report`, `draft`, `synthesisText`, and the string fields of structured results like `applicableLaw[]` — carries the citation verdict **inline**, not only in the `citationChecks` object beside it. **What you will actually see:**


    ```

    An acknowledgement does not revive a claim already barred: section 29(7) of the

    Limitation Act 1980 【✓】. See also [2019] EWHC 3556 (Comm)

    【◻ not checked — the reason is in this citation''s note】. ---

    DETERMINISTIC CITATION CHECK (against the official corpus)

    1 verified · 1 not checked. ◻ **Not checked** — they were not compared against any official corpus…

    ```


    - **Inline marker**: a `【…】` block immediately after each citation, in the response language. The glyph carries the verdict: `✓` verified · `⚠` a warning (e.g. the decision exists but a party you named does not appear in it) · `⛔` broken · `◻` not checked. - **Footer**: a `---` block at the end with the tally and, for anything not clean, the list of citations and why. **Why it is in the text and not only in the JSON.** Whoever copies an answer into an email, a brief or a .docx takes the PROSE. The `citationChecks` object does not travel with it. A verdict that only exists in a field beside the text is a verdict the reader can lose without noticing. **If you parse these strings**: markers are the only `【…】` sequences we emit, so they are safe to strip with a single regex if your pipeline needs the raw prose — but do not strip them from anything a human will read. `citationChecks` remains the machine-readable source of truth for counts and per-citation status; the markers are the same verdict, placed where it cannot get lost. **Idempotent**: annotating an already-annotated text does not duplicate markers or the footer. ## Streaming: `verifiedText` on the `done` event


    On SSE routes the client already holds the raw prose by the time the verifier finishes, so the closing `{type:"done"}` event carries `verifiedText`: the same answer with the verdict already in it. **If it is present, render it in place of the concatenated `text_delta` chunks.** It is omitted when there is nothing to annotate, in which case the deltas are already final. The REST wrappers do this for you — `/v1/consulta`, `/v1/chat` and the rest aggregate server-side and hand you the annotated text — so this only concerns you if you consume the SSE stream directly. ## Base capabilities


    - **Mode=deep**: the Node A (Claude Opus 4.7) + Node B (DeepSeek V4-Pro) chain audits adversarially. 2 credits. Returns an `audit` object with structured findings (hallucinations, false citations, omissions). - **Direct models**: calls through the providers'' own APIs (Anthropic, DeepSeek) with no proxies — lower latency, better rate limits. - **Stable Stripe-style error format**: `error.type`, `error.code`, `error.request_id`, `error.details` + backward-compat aliases. ## Errors and rate limits


    - **Branch on `error.code`.** A code you do not recognise is handled by its `error.type`.'
  contact:
    name: Nexus Legal
    email: support@nexusquantum.legal
    url: https://legal.nexusquantum.legal/developers
  license:
    name: Commercial
    url: https://nexusquantum.legal/terms
servers:
- url: https://legal.nexusquantum.legal
  description: Production
security:
- ApiKeyAuth: []
tags:
- name: White-label
paths:
  /api/v1/branding:
    get:
      summary: Returns the white-label configuration of the calling API key
      description: Every API key (master or solo) has its own white-label configuration. Sub-keys (role=child) automatically inherit the one of the master of their organization. Useful for the partner (Distributor) to check how analysis output is currently signed.
      operationId: getBranding
      security:
      - ApiKeyAuth: []
      tags:
      - White-label
      responses:
        '200':
          description: Current configuration.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BrandingConfig'
        '401':
          description: Invalid API key.
    put:
      summary: Update the white-label configuration
      description: 'Updates the branding applied to analysis outputs and emails. If the key is master of an organization, the changes propagate automatically to ALL child sub-keys. Sub-keys can NOT edit their own branding (403 FORBIDDEN_CHILD_KEY) — only the master can.


        Available modes:

        - `nexus` (default): outputs keep ''Nexus Legal''.

        - `partner`: replaces ''Nexus Legal'' with `partner_brand_name` in the body of the analysis. The technical NEXUS-AUDIT-TRAIL block is preserved.

        - `none`: removes the mentions of ''Nexus Legal'' from the body.


        Anti-SSRF validation: `partner_logo_url` and `partner_website` must be public https URLs (no localhost, no private IPs, no metadata services). Same pattern as `/api/v1/webhooks`.'
      operationId: updateBranding
      security:
      - ApiKeyAuth: []
      tags:
      - White-label
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BrandingConfig'
            example:
              branding: partner
              partner_brand_name: Acme Legal AI
              partner_legal_name: Acme Legal S.A.
              partner_logo_url: https://cdn.example.com/logo.png
              partner_primary_color: '#1A5F8B'
              partner_support_email: support@example.com
              partner_website: https://example.com
      responses:
        '200':
          description: Configuration saved. Returns `applied_to_keys` with the number of affected keys (1 if solo, N if master of an org).
          content:
            application/json:
              schema:
                type: object
                required:
                - ok
                - applied_to_keys
                - config
                properties:
                  ok:
                    type: boolean
                  applied_to_keys:
                    type: integer
                    description: Number of keys it was applied to (1 if solo, N if a master propagated to children).
                  config:
                    $ref: '#/components/schemas/BrandingConfig'
                  requestId:
                    type: string
        '403':
          description: A sub-key (role=child) cannot edit branding. Use the master of the organization.
        '422':
          description: Validation failed (invalid hex color, malformed email, anti-SSRF URL, etc.).
components:
  schemas:
    BrandingConfig:
      type: object
      description: White-label configuration of an API key. Sub-keys inherit from the org master key.
      properties:
        branding:
          type: string
          enum:
          - nexus
          - partner
          - none
          default: nexus
          description: Branding mode. `nexus` keeps 'Nexus Legal'. `partner` replaces it with `partner_brand_name`. `none` removes the mentions.
        partner_brand_name:
          type:
          - string
          - 'null'
          maxLength: 80
          description: Partner trade name. Replaces 'Nexus Legal' in the analysis body when `branding='partner'`. Required when mode is `partner`.
          example: Acme Legal AI
        partner_legal_name:
          type:
          - string
          - 'null'
          maxLength: 200
          description: Registered legal name. Used in the audit-trail PDF and in DPA generation.
          example: Acme Legal S.A.
        partner_logo_url:
          type:
          - string
          - 'null'
          format: uri
          description: Public https URL of the logo. Anti-SSRF (no localhost, no private IPs).
          example: https://cdn.example.com/logo.png
        partner_primary_color:
          type:
          - string
          - 'null'
          pattern: ^#[0-9a-fA-F]{6}$
          description: 'Hex color #RRGGBB for emails and dashboards.'
          example: '#1A5F8B'
        partner_support_email:
          type:
          - string
          - 'null'
          format: email
          description: Reply-to in webhook notifications + system messages.
          example: soporte@example.com
        partner_website:
          type:
          - string
          - 'null'
          format: uri
          description: Partner website URL. Used in the email footer.
          example: https://example.com
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: nlk_...