Regulatory Gate
Qualify an action before execution and return an operational state with the requirements supporting it.
NELSE API
Keep your software.Add the regulatory layer.
NELSE API is for organisations and software vendors that already own the interface, the users and the workflow. Your system sends context and confirmed facts; NELSE returns scoped requirements, actions, review states and evidence references.
RESTSDKMCPEVENTS
Capabilities
One API. Multiple regulatory control points.
Exact availability depends on the connected pack, assurance profile, integration and contracted perimeter. A described capability is not presented as universal regulatory coverage.
AI Gate
Apply usage rules to an AI request, flow or action, with human review where required.
Communication Gate
Control customer-facing messages or content before release within a defined regulatory perimeter.
Regulatory Change
Relate a rule change to the controls, documents or open cases that require reassessment.
Proof & Replay
Preserve context, versions and approvals needed to inspect or replay a result.
Regulatory Clock
Turn a qualified event into deadlines, owners, actions and expected evidence.
Application or API?
The same engine. Two operating models.
Use a NELSE application
NELSON, NELSPACE or NELSIA when your teams want a ready operating surface.
Use NELSE API
When your users already work in your own product and the regulatory capability must be embedded.
Combine both
Use a NELSE application for some teams and API integration for the workflows that must remain in your systems.
Integration contract
An API response should tell you more than yes or no.
Context + facts
Jurisdiction, product, event, actors, dates, identity and confirmed information.
Corpus + engine
Pinned normative scope, deterministic execution and human-review requirement where applicable.
Requirements + actions + evidence
State, missing information, deadlines, actions, review route and evidence/replay reference.
Public decision trace
Keep the path from source to evidence addressable.
SOURCE
Authoritative text, standard or internal policy and its version.
RULE
Formalised requirement used in the selected normative scope.
FACT
Confirmed, missing or conflicting contextual information.
RESULT
Requirement, action, deadline, state or control outcome.
HUMAN
Review, modification, refusal or approval when required.
PROOF / REPLAY
Reference used to examine the result in its historical context.
Where it fits
Healthcare software
A patient journey, act or information duty is prepared inside the software already used by the professional.
Requirements, missing facts, actions, human-review points and evidence references return to the same workflow.
Clinical research & MedTech
A protocol, intended purpose, feature, dataset or market changes.
The integration identifies dossiers, evidence and reviews to revisit for the selected regulatory scope.
Banking & insurance
An onboarding, product, client or transaction triggers several regulatory controls.
Obligations, required evidence, deadlines and review states can be returned directly into KYC, underwriting or advice workflows.
AI & agent workflows
A user or agent wants to send data, invoke a model or execute an action.
NELSE can return allow, transform, block, limited-scope, evidence-required or human-review states according to the connected control.
Incidents & deadlines
An event starts several regulatory clocks.
Typed deadlines, actions, notification paths and evidence requirements return to the existing ITSM/SOC process.
Integration modes
REST
Synchronous qualification and control calls from your backend.
SDK
Embed typed NELSE states and control patterns directly in your product experience.
MCP
Let agents consult NELSE without turning the language model into the normative decision engine.
EVENTS
Consume state changes, review requirements and regulatory events in existing workflows.