Quantum Nexus Deadlines API

Spanish LEC deadline calculator with CGPJ national + regional holidays (17 autonomous communities).

GitHub OpenAPI

Operations 1

POST /api/v1/plazos/calcular Procedural time limits — ES (LEC) and England and Wales (CPR r 2.8) #

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-deadlines-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-deadlines-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Nexus Legal Deadlines 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: Deadlines
  description: Spanish LEC deadline calculator with CGPJ national + regional holidays (17 autonomous communities).
paths:
  /api/v1/plazos/calcular:
    post:
      tags:
      - Deadlines
      summary: Procedural time limits — ES (LEC) and England and Wales (CPR r 2.8)
      description: 'Computes the due date of a procedural time limit under the law of a SPECIFIC forum. **`jurisdiction` is required and has no default (v1.61)**: a period counted under another jurisdiction''s rules produces a date the client may act on, and a missed limitation period cannot be undone.


        - **`ES`** — LEC + LOPJ, national CGPJ holidays and, optionally, the holidays of the autonomous community given in `ccaa`. August counts as non-working by default (Art. 183 LOPJ).

        - **`GB-EAW`** — CPR r 2.8 for England and Wales: **clear days**; if the period is **5 days or less**, Saturdays, Sundays, bank holidays, Christmas Day and Good Friday are excluded, and if it is **more than 5 days all days are counted**. There is **no August vacation**: the courts'' Long Vacation does not suspend CPR time limits. `tipo_computo` takes a day count only (`meses`/`anios` return 400) and the answer comes back as `clear_days`. Set `acto_en_oficina` when the act must be done at the court office, so r 2.8(5) applies.


        Scotland (`GB-SCT`) and Northern Ireland (`GB-NIR`) return 400 rather than an approximation: their rules and their bank holidays differ — 2 January is a holiday in Scotland and not in England. Cost: 0 LLM, pure in-memory computation.'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - jurisdiction
              - fecha_base
              - cantidad
              - tipo_computo
              properties:
                jurisdiction:
                  type: string
                  enum:
                  - ES
                  - GB-EAW
                  example: GB-EAW
                  description: Forum whose procedural rules govern the count. REQUIRED, no default.
                fecha_base:
                  type: string
                  format: date
                  example: '2026-05-24'
                cantidad:
                  type: integer
                  minimum: 1
                  maximum: 36500
                  example: 20
                tipo_computo:
                  type: string
                  enum:
                  - habiles
                  - naturales
                  - meses
                  - anios
                  description: GB-EAW takes a day count only; the response reports `clear_days`.
                ccaa:
                  type:
                  - string
                  - 'null'
                  pattern: ^ES(-[A-Z]{2})?$
                  example: ES-MD
                  description: ES only.
                agosto_inhabil:
                  type: boolean
                  default: true
                  description: ES only. There is no August vacation under the CPR.
                acto_en_oficina:
                  type: boolean
                  default: false
                  description: 'GB-EAW only — CPR r 2.8(5): the act must be done at the court office, so the period is extended if it ends on a day the office is closed.'
      responses:
        '200':
          description: '{ jurisdiction, fecha_vencimiento, tipo_computo, regla_aplicable, ajustes_aplicados, ... }'
        '400':
          description: MISSING_JURISDICTION (required, no default — v1.61) | JURISDICTION_NOT_SUPPORTED (incl. GB-SCT / GB-NIR) | TIPO_COMPUTO_NOT_APPLICABLE (months/years under the CPR) | CALENDAR_NOT_LOADED (outside the years of the England and Wales bank-holiday calendar) | INVALID_FECHA_BASE | INVALID_CANTIDAD | INVALID_TIPO_COMPUTO | INVALID_CCAA
        '402':
          description: INSUFFICIENT_CREDITS — paywall from minute one (balance > 0 required; the calculation does not deduct credits).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/InsufficientCreditsError'
      operationId: postApiV1PlazosCalcular
      x-operation-id-source: derived
components:
  schemas:
    InsufficientCreditsError:
      type: object
      required:
      - error
      - balance
      - required
      properties:
        error:
          type: string
          example: INSUFFICIENT_CREDITS
        balance:
          type: number
          description: User's current credit balance.
        required:
          type: number
          description: Credits required for this operation.
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: nlk_...