INTEGRATIONS

Your CTRM sends. We analyse. Your CTRM receives.

Native bidirectional integration with the main enterprise CTRM systems on the market. HMAC-authenticated webhook in, signed callback out. Zero Retention: contract text never persists on our side — only the SHA-256 hash and the analysis verdict. Configuration in minutes from the dashboard.

CTRM liveSWIFT / SEPA on demand3 SDKs published8 REST endpoints

CTRM · LIVE TODAY

Native adapters for the four CTRM systems we hear about most often.

Openlink (Endur / Findur), ION / Aspect, Brady and Murex are supported with vendor-specific payload shapes. A generic adapter exists for any CTRM that can speak JSON over an HMAC-signed webhook. Production activation follows the standard enterprise onboarding.

01

CTRM POSTs the contract

Your CTRM fires a webhook to our endpoint with an HMAC-SHA256 signature header. Body shape is vendor-specific or generic JSON.

02

We analyse in seconds

The standard pipeline (Node A / Node B / risk mapping) runs on the contract. We persist only metadata + SHA-256 of the source — never the text itself.

03

Callback to your CTRM

A signed POST returns to your CTRM with riskLevel, flags and a short summary. Async fallback: GET /api/ctrm/jobs/{jobId} for polling integrations.

  • HMAC-SHA256 inbound verification
  • Native adapters · Openlink Endur/Findur · ION/Aspect · Brady · Murex
  • Generic JSON adapter for any other CTRM
  • Async callback or polling fallback
  • Zero Retention by design — hash only, never the text

FINANCIAL CONNECTORS · ON DEMAND

Activate the connector you need.

The architecture that supports the CTRM integration is connector-agnostic. The connectors below are activated under enterprise contract on the same rails — your timeline drives the activation order, not ours.

ConnectorStatusNotes
CTRM · Openlink · ION · Brady · MurexliveSee above. Activation per enterprise contract.
SWIFT MT / MX · ISO 20022on demandArchitecture supports inbound SWIFT. Requires BIC + production certificates.
SEPA · SCT / SDD / Instanton demandRelevant for payment compliance flows inside the EU.
Bloomberg Terminalon demandInstitutional substitute / complement to Alpha Vantage for market data.
Refinitiv / LSEG Workspaceon demandSame. Vendor preference per client.
FIX Protocolon demandFor connecting trading desks directly to the analysis engine.

OFFICIAL SDKs

Three packages. Same engine.

Install in 30 seconds. Zero runtime dependencies for the TypeScript SDK. Both SDKs cover the full REST surface plus signed webhook verification.

📦 TypeScript / JS

$ npm install @nexus-finance/sdk

@nexus-finance/sdk · v0.1.0 · npm · zero runtime deps

🐍 Python ≥ 3.9

$ pip install nexus-finance-sdk

nexus-finance-sdk · v0.1.0 · PyPI

🤖 MCP Server

$ npx -y @nexus-finance/mcp

@nexus-finance/mcp · v0.1.0 · 8 tools for Claude / Cursor / Claude Code · published in the Anthropic MCP Registry

REST API v1

Eight endpoints. JSON in, JSON out.

Bearer authentication with scope-based API keys. HMAC-SHA256 signed outbound webhooks. Idempotency-Key supported everywhere it makes sense. The full surface:

POST  /api/v1/analyze              — synchronous analysis on a single contract
POST  /api/v1/jobs                 — async job queue, signed-webhook callback
GET   /api/v1/jobs/:id             — poll an in-flight job
POST  /api/v1/cases                — open / update a case (multi-tenant)
POST  /api/v1/var                  — VaR / CVaR with stress scenarios
POST  /api/v1/rwa                  — Basel III SA Risk-Weighted Assets
GET   /api/v1/market-feeds         — live commodity / FX / equity quotes
POST  /api/ctrm/webhook            — CTRM inbound endpoint (HMAC-verified)

Pick the integration that fits your stack.

Tell us which CTRM you run, which market data vendor you trust and which language your team writes in. We come back with the activation timeline and the signed contracts on the same call.

Talk to integrationsBack to /finanzas