智能提示模板

Build on it

OpenContracts is a platform, not a black box. Everything the UI does runs on surfaces you can call yourself — point it at the documents you already have and build your own tooling on top.

Build and start all services (including frontend)

docker compose -f local.yml build docker compose -f local.yml --profile fullstack up ```

Then open http://localhost:3000 and log in with admin / Openc0ntracts_def@ult.

See the full Quick Start guide for details and troubleshooting.

Quick Start

OpenContracts ([Demo](https://contracts.opensource.legal))

Open-source document intelligence you can build on.

Point OpenContracts at a repository of documents and get a programmable citation graph — human annotation, structured extraction, AI agents, and a built-in MCP server, all behind one API. Self-hosted, MIT-licensed, and built for teams working at scale.

Same graph, three surfaces: a GraphQL + REST API for your apps, a Model Context Protocol server for your agents, and a React UI for your team.

---

Copy sample environment files

mkdir -p .envs/.local cp ./docs/sample_env_files/backend/local/.django ./.envs/.local/.django cp ./docs/sample_env_files/backend/local/.postgres ./.envs/.local/.postgres cp ./docs/sample_env_files/frontend/local/django.auth.env ./.envs/.local/.frontend

A pluggable pipeline

Parsing, embedding, and thumbnailing are swappable components. Register a custom parser, embedder, or thumbnailer for your formats and everything downstream — search, annotation, agents — keeps working unchanged.

See the pipeline overview.

Processing Pipeline

The modular pipeline supports custom parsers, embedders, and thumbnail generators:

Each component inherits from a base class with a defined interface:

• Parsers — Extract text and structure from documents
• Embedders — Generate vector embeddings for search
• Thumbnailers — Create document previews

See the pipeline documentation for details on creating custom components.

</details>

---

Then explore it — and ask it questions

Citations are highlighted inline on the filings themselves. The References panel lists everything a document cites — click any cite to open the statute, with its own cross-references and everything that cites it back. The ask bar runs a corpus-scoped agent whose answers come back grounded and cited.

Everything in both clips is the stock product against a local install — no custom code, and every surface the UI touches is also reachable over the API and MCP server below.

Here's the artifact those clips produce, frozen so you can read it — every filing wired to the exact section of law it cites, with bodies of law the library doesn't hold yet drawn as dashed nodes, tracked until you ingest them:

---