Integrations
The policy engine gives the same answer wherever the question comes from. These are the places it can come from today, and where its answers can go.
Work tools
Slack
Analyse, draft and get notifications in Slack.
Scrive
Send approved contracts for e-signature without leaving Lexnus.
AI
Claude
Drafts from the approved library. Returns the verdict before anything moves.
An Admin can also switch the account’s AI provider to Claude by Anthropic.
OpenAI
Same library, same verdict. The agent calls the engine before it drafts.
An Admin can also switch the account’s AI provider to OpenAI.
Mistral
EU-hosted model, EU-hosted policy. Verdict returned to the agent.
Mistral is the default AI provider, hosted by Lexnus with EU data residency.
OpenAI on Azure
An Admin can switch the account’s AI provider to OpenAI on Azure.
Cursor, VS Code and other MCP clients
Connect to Lexnus and use your playbooks directly.
Identity
Microsoft Entra ID
Single sign-on and directory sync.
Okta
Single sign-on and directory sync.
Google Workspace
Single sign-on.
Any OIDC provider
Single sign-on.
Any SCIM 2.0 provider
Directory sync.
Developers
Direct API
Facts in, verdict out, from any system you already run.
Coming soon
Word
Verdict in the side panel. Approved fix inserted with tracked changes.
Outlook
Banner on the inbound contract, fix offered in place.
HubSpot
Facts submitted from the deal record. Verdict returned to the deal.
Google Drive
New contract in a watched folder, evaluated on arrival.
These are planned, not available today.
Need something sooner? Webhooks and the API let you build it yourself.
Where your team works
Slack
An Admin connects your Slack workspace once, for the whole account. People are matched to their Slack accounts by email. Each person then chooses which notifications reach them as direct messages.
Approval requests arrive with Approve and Reject buttons, so a contract can be unblocked without leaving Slack. Signed-contract notices can go to a channel. And Lex, the Lexnus assistant, answers in a direct message: ask about a contract, or share a file to add it to Lexnus. Lex acts as you, with your role, and asks you to confirm before anything is sent for signature.
AI assistants over MCP
Claude, ChatGPT, Cursor, VS Code and other MCP clients connect to Lexnus and use your playbooks directly: analyse a document, draft from a playbook, file a contract, send it for signature. Every call runs as an identified person and is recorded. Setup, tools and limits are in the MCP reference.
E-signature through Scrive
Send contracts for signature from Lexnus, with BankID, MitID and qualified electronic signatures among the options. Your team uses the Lexnus Scrive account by default, or an Admin connects your own. See Signing and Obligations.
For your own systems
Webhooks
An Admin points Lexnus at an HTTPS endpoint and chooses the events to send.
REST API
The API is the one the Lexnus application uses.
Webhook events
| Event | When it fires |
|---|---|
| Approval requested | A rule needs sign-off on a contract version. |
| Approval decided | An approver approved or rejected. |
| Contract created | A new contract exists in Lexnus. |
| New version published | A contract has a new version. |
| Contract signed | Every party has signed. |
| Contract finalised | A contract was marked executed. |
| Renewal due | A renewal reminder date has arrived. |
| Contract expired | A contract reached its end date without renewing. |
For IT
Single sign-on
Sign in through Microsoft Entra ID, Okta, Google Workspace or any OIDC provider.
Directory sync
Connect Okta, Microsoft Entra or any SCIM 2.0 provider and users and groups are provisioned automatically.
Your choice of AI provider
By default, Lexnus uses Mistral, hosted by Lexnus with EU data residency. An Admin can switch the account to Claude by Anthropic, OpenAI, or OpenAI on Azure with your own key.
FAQs
Does Lexnus work in Slack?
Yes. An Admin connects your Slack workspace once. People then get notifications as direct messages, approve or reject requests with buttons, and can ask Lex questions in a direct message.
Which AI assistants can connect to Lexnus?
Any client that speaks the Model Context Protocol, including Claude, ChatGPT, Cursor and VS Code. See the MCP reference for setup.
How do I know a webhook came from Lexnus?
Every delivery carries an HMAC-SHA256 signature over its timestamp and body, made with a secret shown to you once when you create the webhook. Your endpoint checks the signature before trusting the request.
Does Lexnus support SAML?
Single sign-on uses OIDC, which Microsoft Entra ID, Okta and Google Workspace all support. SAML is not available.
Can we use our own AI provider?
Yes. An Admin can switch from the default, Mistral hosted by Lexnus in the EU, to Claude, OpenAI or Azure OpenAI with your own key. Whichever provider you use, it extracts facts. Rules decide compliance.
Is there a Word add-in?
Not yet. A Word add-in is coming soon: the verdict in the side panel and the approved fix inserted with tracked changes. It is planned, not available today. An Outlook add-in is coming soon too.
What happens when a webhook delivery fails?
Failed deliveries are retried for about an hour and a quarter. After ten failures in a row, the webhook is switched off and its owner is told. The delivery log shows each attempt and the response it got.
Is a new webhook active straight away?
A new webhook receives nothing until it is verified with a signed test request.
How do I authenticate with the REST API?
Authenticate with a developer token from Account settings → Developers, or with an OAuth token. A call can do what the person behind the token can do, and no more. Requests are rate-limited per account. A refused request says when to try again.
Can single sign-on be required?
An Admin can require single sign-on for your email domains, which turns off password sign-in for them.
How does IT set up directory sync?
An Admin sends IT a setup link that works for 24 hours, without IT needing a Lexnus account.
Does the AI provider decide whether a contract complies?
The provider extracts facts from contracts. It never decides whether they comply. The rules do.
Apply your standard where your team already works
Connect Slack, Scrive and your AI assistants over MCP, so the same playbook applies wherever contracts are written.
EU-hosted. GDPR compliant. No US CLOUD Act exposure.