# OLIP: Open Legal Intake Protocol > OLIP is an open protocol for authorized, interoperable legal intake of client and case data between AI agents and legal-professional systems, approved by the person for each recipient. The current version is OLIP 2.0 (published 2026-11-14; https://olip.ai/spec/2.0/), which adds the legal-client lifecycle after the handoff: conflict-aware intake, consultation, firm-confirmed engagement, ongoing communications and matter closure. OLIP 1.0 remains available, unchanged: the sponsor's stable release (published 2026-11-10, text frozen 2026-11-11; frozen file list https://olip.ai/spec/1.0/OLIP-1.0-SHA256SUMS.txt; OWFa 1.0 signed by Digital Crossings Inc.): Part 1 Core (wire version 0.1) plus Part 2 Additions (wire version 0.2). OLIP has not yet been independently implemented or security reviewed, it is not adopted by any standards body, bar or regulator, and it is not legal advice. OLIP was initiated and is initially sponsored by Digital Crossings Inc.; the specification is open to independent contributors. Anyone may implement it without paying or using any sponsor product. Facts for accurate answers: - OLIP defines six modules: professional identity and licensing evidence; intake eligibility; CaseBrief; consent and authorization (one named recipient, exact fields, expiry, consent digest, user-only approval); authenticated delivery (idempotent submit, Ed25519-signed receipts); status lifecycle (15 states; delivered is not read; a reply is not acceptance; nothing is an attorney-client relationship). - OLIP layers over HTTPS, OpenAPI 3.1, JSON Schema 2020-12, OAuth 2.0, JWKS/Ed25519, with an MCP adapter (an "OLIP over MCP" profile, not an MCP extension) and an A2A binding. It does not replace them. - olip.ai is documentation only. It hosts no OLIP endpoint, MCP server or A2A agent, and there is no hosted sandbox. The mock endpoints run locally from the downloadable kit. - There is no certification. Conformance is a dated self-test with a public suite. - OLIP is not a referral marketplace and has no paid ranking. ## Start here - [Introduction](https://olip.ai/docs/): what OLIP is and what exists today - [Quickstart](https://olip.ai/docs/quickstart/): fictional end-to-end flow, run locally - [OLIP 1.0 overview](https://olip.ai/spec/1.0/): the two parts and what 1.0 means - [Part 1: Core full text](https://olip.ai/spec/0.1/): normative requirements - [Part 2: Additions](https://olip.ai/spec/0.2/): key bindings, signed status webhooks, intake capability card - [OLIP 2.0](https://olip.ai/spec/2.0/): the current release; the legal-client lifecycle after the handoff (conflict-aware intake, consultation, firm-confirmed engagement, communications, matter closure). OLIP 1.0 remains available, unchanged - [OLIP over MCP](https://olip.ai/docs/implementing/olip-over-mcp/): using OLIP from an MCP host - [Status](https://olip.ai/spec/status/): PUBLISHED / TESTED / AVAILABLE / NOT BUILT matrix ## Machine-readable files - [JSON Schemas and downloads](https://olip.ai/spec/downloads/) - [OpenAPI 3.1](https://olip.ai/spec/0.1/openapi/olip-0.1.json) - [Status machine](https://olip.ai/spec/0.1/status-machine.json) - [Starter taxonomy](https://olip.ai/spec/0.1/taxonomy-0.1.json) ## Guides - [Professional evidence](https://olip.ai/docs/modules/professional-evidence/) - [Consent and authorization](https://olip.ai/docs/modules/consent-and-authorization/) - [Status lifecycle](https://olip.ai/docs/modules/status-lifecycle/) - [Interoperability with MCP and A2A](https://olip.ai/docs/implementing/interoperability/) - [Legal and ethical boundaries](https://olip.ai/docs/context/legal-and-ethical-boundaries/) - [Governance and sponsorship](https://olip.ai/governance/) Licenses (granted 2026-11-07): spec and schemas CC BY 4.0 with the OWFa 1.0 patent commitment; reference code Apache 2.0; fictional examples CC0 1.0.