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-payments-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: 3.2.0
info:
title: Nexus Legal Payments 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: Payments
description: 'Payment initiation for the key owner (E6, checkout→URL/token): Paddle/NOWPayments checkout, multi-provider subscription, content add-on and entitlement reads. Jurisdiction-agnostic where applicable (no ES default). The wrapper NEVER debits: credit/entitlement is granted by the post-payment webhook. API-ONLY for checkout/subscribe/content-addon (initiating payments from an LLM connector is deliberately avoided — NO MCP tool); `payments/entitlements` does have the `nexus_account_entitlements` tool.'
paths:
/api/v1/payments/entitlements:
get:
tags:
- Payments
summary: Contracted content (entitlements) · 0 credits
description: 'Reads `content_entitlements` `.eq(user_id, userId).eq(active, true)` — the key owner''s active content (Layer 3). Thin loopback to `/api/payments/entitlements`. No charge. Scope: mcp | *. MCP tool: `nexus_account_entitlements`.'
responses:
'200':
description: '{ entitlements: [{ jurisdiction, kind, source }] }'
content:
application/json:
schema:
type: object
'401':
description: Invalid API key.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
operationId: getApiV1PaymentsEntitlements
x-operation-id-source: derived
/api/v1/payments/checkout/paddle:
post:
tags:
- Payments
summary: Start Paddle checkout · 0 credits (checkout→URL)
description: 'Creates a Paddle checkout for the key owner (email via `user_profiles`, `guardCheckoutCreation` anti-carding). Returns `{ url, transaction_id }` (Paddle URL). Credit is granted by the post-payment webhook — does NOT debit. API-ONLY (no MCP tool: initiating payments from an LLM connector is deliberately avoided). Scope: mcp | *.'
requestBody:
required: true
content:
application/json:
schema:
type: object
responses:
'200':
description: '{ url, transaction_id }'
content:
application/json:
schema:
type: object
'400':
description: Invalid data.
operationId: postApiV1PaymentsCheckoutPaddle
x-operation-id-source: derived
/api/v1/payments/checkout/nowpayments:
post:
tags:
- Payments
summary: Start crypto checkout (NOWPayments) · 0 credits (checkout→URL)
description: 'Creates a NOWPayments checkout (`order_id = "userId:quantity"` with the resolved user, no override). Returns `{ url, invoice_id }` (NOWPayments URL). Credits are granted by the post-payment IPN webhook — does NOT debit. API-ONLY. Scope: mcp | *.'
requestBody:
required: true
content:
application/json:
schema:
type: object
responses:
'200':
description: '{ url, invoice_id }'
content:
application/json:
schema:
type: object
'400':
description: Invalid data.
operationId: postApiV1PaymentsCheckoutNowpayments
x-operation-id-source: derived
/api/v1/payments/content-addon:
post:
tags:
- Payments
summary: Start content add-on purchase · 0 credits (checkout→URL)
description: 'Jurisdiction-agnostic: `sku` ∈ addons + `jurisdiction` validated (isValidJurisdiction), NO ES default. Returns `{ url, transaction_id, sku, jurisdiction, amount }` (Paddle URL). The entitlement is granted by the webhook — does NOT debit. API-ONLY. Scope: mcp | *.'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- sku
- jurisdiction
properties:
sku:
type: string
jurisdiction:
type: string
description: ISO code. REQUIRED — no ES default.
responses:
'200':
description: '{ url, transaction_id, sku, jurisdiction, amount }'
content:
application/json:
schema:
type: object
'400':
description: MISSING_JURISDICTION | invalid sku/jurisdiction.
operationId: postApiV1PaymentsContentAddon
x-operation-id-source: derived
/api/v1/payments/subscribe:
post:
tags:
- Payments
summary: Start subscription (multi-provider) · 0 credits (checkout→URL)
description: 'Multi-provider (Polar hosted / Paddle overlay / NOWPayments invoice). `jurisdiction` optional, validated, no default. Returns `{ url, … }` (provider URL). Provisioning arrives by webhook — does NOT debit. API-ONLY. Scope: mcp | *.'
requestBody:
required: true
content:
application/json:
schema:
type: object
responses:
'200':
description: '{ url, … }'
content:
application/json:
schema:
type: object
'400':
description: Invalid data.
operationId: postApiV1PaymentsSubscribe
x-operation-id-source: derived
components:
schemas:
ErrorResponse:
type: object
required:
- error
description: Stripe-style error envelope returned by apiError() on ALL v1 routes. `error` is an OBJECT {type, code, message, request_id, details?}; the top-level `error_message`/`code` are backward-compat (deprecated v1.7). A generated client must deserialize `error` as an object, not as a string.
properties:
error:
type: object
required:
- type
- code
- message
properties:
type:
type: string
example: invalid_request_error
code:
type: string
example: VALIDATION_ERROR
message:
type: string
request_id:
type: string
details:
type: object
description: Optional. An engine failure carries what you need in order to decide what to do next, and a `429` says whose ceiling you reached. Each field is present only when it was measured, and `details` is omitted entirely rather than sent empty.
properties:
retryable:
type: boolean
description: Whether retrying this exact request can succeed. Absent means not measured — do not read absence as `true`.
refunded:
type: boolean
description: Whether the credit for this call was returned. Absent means not measured.
reason:
type: string
description: Short machine-readable cause.
example: provider_timeout
provider:
type: string
description: Which engine failed. On a BYO tenant this is the difference between checking your own key and opening a ticket with us.
example: Anthropic (BYO)
error_class:
type: string
scope:
type: string
enum:
- ip
- user
- organization
description: 'On a `429`: whose ceiling you reached.'
retry_after_seconds:
type: integer
description: 'On a `429`: seconds to wait, the same value as the `Retry-After` header.'
limit_per_minute:
type: integer
description: 'On a `429`: the per-minute ceiling you reached.'
error_message:
type: string
description: Backward-compat (deprecated v1.7).
code:
type: string
description: Backward-compat (deprecated v1.7).
securitySchemes:
ApiKeyAuth:
type: http
scheme: bearer
bearerFormat: nlk_...