API overview
The service topology and the main REST surface 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. 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. Note that several fields are JSON strings (for example questions, steps, rules, placeholders, citation) — parse them defensively. The full endpoint list and internal service ports are in the technical documentation (docs/TECHNICAL_DOCUMENTATION.md).
Related technical documentation
The MCP gateway
Expose LexCore's verified capabilities as Model Context Protocol tools any AI host can call — without bypassing CitationGate.
Bring Your Own Key & self-hosting
Use your own model provider account, or run the whole stack behind your own infrastructure.
Integrations: channels & connectors
Meet legal teams where they already work — chat channels, intake links, storage/DMS connectors, and a Word add-in.