Quantum Nexus Cross Reference API
Bidirectional link between in-force statutory articles and the CENDOJ judgments that apply them.
Bidirectional link between in-force statutory articles and the CENDOJ judgments that apply them.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/nexusquantum-legal:nexusquantum-legal-cross-reference-api"
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.
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: 3.2.0
info:
title: Nexus Legal Cross Reference 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: Cross-reference
description: Bidirectional link between in-force statutory articles and the CENDOJ judgments that apply them.
paths:
/api/v1/cruce/sentencias-de-articulo:
get:
tags:
- Cross-reference
summary: Judgments applying a statutory article
description: 'Returns the top-N judgments from the jurisprudencia_docs corpus citing a specific article, sorted by mention count and date desc. Cost: 0 LLM.'
parameters:
- name: articulo
in: query
required: true
schema:
type: string
example: '1902'
- name: norma_id
in: query
required: false
schema:
type: string
format: uuid
- name: norma_alias
in: query
required: false
schema:
type: string
example: CC
- name: jurisdiction
in: query
required: false
schema:
type: string
example: ES
description: ISO code. REQUIRED (this parameter or its `jurisdiccion` alias) — no default (400 MISSING_JURISDICTION if both are missing, v1.28).
- name: jurisdiccion
in: query
required: false
schema:
type: string
example: ES
description: Spanish-language alias of `jurisdiction`.
- name: top
in: query
required: false
schema:
type: integer
minimum: 1
maximum: 50
default: 10
responses:
'200':
description: '{ articulo, top, sentencias[] }'
'400':
description: MISSING_JURISDICTION (`jurisdiction`/`jurisdiccion` alias required — no default, v1.28) | MISSING_ARTICULO | MISSING_NORMA | INVALID_NORMA_ID
'402':
description: INSUFFICIENT_CREDITS — paywall from minute one (balance > 0 required; the lookup does not deduct credits).
content:
application/json:
schema:
$ref: '#/components/schemas/InsufficientCreditsError'
'403':
description: CONTENT_NOT_ENTITLED — the account does not have the case-law add-on (Layer 3) active.
content:
application/json:
schema:
$ref: '#/components/schemas/ContentNotEntitledError'
operationId: getApiV1CruceSentenciasDeArticulo
x-operation-id-source: derived
/api/v1/cruce/articulos-de-sentencia:
get:
tags:
- Cross-reference
summary: Statutory articles cited by a judgment
description: 'For a judgment (UUID in jurisprudencia_docs), returns the articles it cites grouped by statute + article with a mention count. Cost: 0 LLM.'
parameters:
- name: jurisprudencia_id
in: query
required: true
schema:
type: string
format: uuid
responses:
'200':
description: '{ jurisprudencia_id, articulos[] }'
'400':
description: INVALID_JURIS_ID
'402':
description: INSUFFICIENT_CREDITS — paywall from minute one (balance > 0 required; the lookup does not deduct credits).
content:
application/json:
schema:
$ref: '#/components/schemas/InsufficientCreditsError'
'403':
description: CONTENT_NOT_ENTITLED — the account does not have the case-law add-on (Layer 3) active.
content:
application/json:
schema:
$ref: '#/components/schemas/ContentNotEntitledError'
operationId: getApiV1CruceArticulosDeSentencia
x-operation-id-source: derived
components:
schemas:
ContentNotEntitledError:
type: object
required:
- error
description: 403 emitted by the content endpoints (case law, legislation, cross-reference) when the account does not have the content add-on (Layer 3) active for the requested jurisdiction. Stripe-style format.
properties:
error:
type: object
required:
- type
- code
- message
properties:
type:
type: string
example: permission_error
code:
type: string
example: CONTENT_NOT_ENTITLED
message:
type: string
example: Your account does not have access to ES case law. This is a content add-on (Layer 3).
request_id:
type: string
details:
type: object
properties:
jurisdiction:
type: string
example: ES
kind:
type: string
enum:
- caselaw
- legislation
error_message:
type: string
description: Backward-compat alias of error.message.
code:
type: string
description: Backward-compat alias of error.code.
example: CONTENT_NOT_ENTITLED
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_...