API overview
The service topology and the main REST endpoints for integrators.
LexCore is three cooperating services. Integrators talk to case-management (the system of record and API gateway). It proxies AI work to the ai-orchestrator and document mechanics to the doc-engine, both of which are internal and guarded by a shared secret.
case-management exposes a REST API under /api/v1/cases, authenticated with a bearer JWT from your sign-in. For tools that run without a person signed in (n8n, Zapier, your own scripts), use a workspace API token instead, which reaches a small, fixed set of routes; see Connect LexCore to your other tools. Representative areas:
| Area | Representative endpoints |
|---|---|
| Documents | upload (multipart) · get · download · delete · versions/export |
| AI review | review-contract · redline (+ .docx) · compare · grid (+ XLSX) · reverify |
| Research | research · verify-authority · authority/coverage |
| AI tasks | draft · extract-clauses · chronology · absence-check · opposition · contract-graph |
| Workflows | list/create · run |
| Templates / Playbooks | CRUD · publish (PII-scrub gate) · versioned playbooks |
| Health | health (liveness) · ready (dependencies) · metrics |
Note
Client contracts are pinned in the web-app's API client. Several fields are JSON strings (for example questions, steps, rules, placeholders, citation), so parse them defensively. The full endpoint list and internal service ports are in the technical documentation (docs/TECHNICAL_DOCUMENTATION.md).
Related documentation
Connect LexCore to your other tools: API tokens and webhooks
Let tools like n8n, Zapier, Make or Power Automate work with LexCore, so routine steps happen by themselves. What each part does, how to switch it on, and what stays protected.
The MCP gateway
LexCore's verified tools as Model Context Protocol tools for AI apps such as Claude. Built and tested, but not yet open to customers.
Bring your own key (BYOK) and self-hosting
Use your own model provider account, or run the whole stack on your own infrastructure.
Integrations: channels and connectors
Work where your legal team already works: chat channels, intake links, storage and DMS connectors, and a Word add-in.