Skip to main content

OPEN LEGAL INTAKE PROTOCOL · 2.0

A common language for AI-to-lawyer connections.

The 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.

An AI agent finds a lawyer with dated, sourced evidence. The person picks one recipient and approves exactly which facts go. The firm's system signs a receipt, and every status says only what actually happened.

How data moves in OLIPAn AI agent prepares a CaseBrief. The person approves exactly which facts go. Only those facts reach the one law firm system the person chose, which sends back a signed receipt.CaseBriefapproved facts onlysigned receiptAI agentfinds lawyers, with sourcesThe personapproves which facts goLaw firm systemsigns a receipt

OLIP 2.0 is the current release of the Open Legal Intake Protocol, published by its sponsor. It 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. It is not legal advice. The demo is a fictional simulation: no real lawyer is contacted. See exactly what exists today.

How it works

The OLIP lifecycle in eight steps. OLIP 1.0, the handoff: steps 1 to 3. OLIP 2.0, after the handoff: steps 4 to 8. The person approves every disclosure and the law firm signs every confirmation; an AI agent can prepare but never approve or confirm.
  1. OLIP 1.0

    Step 1: Discover

    • Professional evidence, dated and sourced
    • Intake eligibility
    Agent prepares
  2. OLIP 1.0

    Step 2: Authorize

    • One named recipient
    • Exact fields, with expiry
    • Bound to a content digest
    Person approves
  3. OLIP 1.0

    Step 3: Connect

    • Authenticated handoff
    • Signed delivery receipt
    • Status says only what happened
    Firm signs
  4. OLIP 2.0

    Step 4: Conflict check

    • Minimal screening first
    • Full CaseBrief only, after the firm says yes
    Person approvesFirm signs
  5. OLIP 2.0

    Step 5: Consultation

    • Firm offers zoned times
    • Person picks one
    • Only the firm confirms
    Person approvesFirm signs
  6. OLIP 2.0

    Step 6: Engagement

    • One exact offer version
    • Person accepts it
    • Attorney confirms
    Person approvesFirm signs
  7. OLIP 2.0

    Step 7: Messages

    • Each message approved
    • Documents checked
    • Delivered is not read
    Person approvesFirm signs
  8. OLIP 2.0

    Step 8: Closure

    • Closed or terminated, with notice
    • Portable matter record
    Firm signs

Person approves each disclosure, bound to its exact content

Firm signs every confirmation and receipt (Ed25519)

An AI agent can prepare every step. It can never approve for the person or confirm for the firm.

1. Discover

Who is this professional, and how do we know? OLIP keeps an indexed record, an official-source check and a lawyer's own statement apart, each with a source, a date and its uncertainty. Firms publish the matters, places and languages they accept.

Professional evidence · Intake eligibility

2. Authorize

The person reviews a short CaseBrief, picks one named recipient, sees every field that will be shared, and approves on a page the agent cannot complete alone. The approval expires and is bound to a digest of exactly that content.

CaseBrief · Consent and authorization

3. Connect

An authenticated, idempotent handoff sends only the approved fields. Status moves step by step: recorded, queued, sent, delivered (with a signed receipt), acknowledged, responded. Delivery is never presented as a reply, and a reply is never presented as representation.

Delivery · Status lifecycle

4 to 8. After the handoff (OLIP 2.0)

The same rules continue once a firm has the handoff. A conflict check starts with the minimum the firm needs, and the full CaseBrief follows only after the firm says intake may continue. Consultation times are offered by the firm and confirmed only by the firm. Engagement binds one exact offer version, accepted by the person and confirmed by the firm's attorney. Every message is approved, every delivery has a signed receipt, and closure leaves the person with a portable record that authorizes nobody.

OLIP 2.0 specification

Why an open legal intake protocol?

People increasingly ask AI assistants for help with a legal problem. Today each assistant, directory and firm intake form invents its own way to describe a lawyer, collect facts, ask for consent and report what happened. The result is repeated forms, vague permission, and status messages that say "sent" when nothing reached anyone.

OLIP gives every party the same small vocabulary:

  • fewer repeated intake forms, because a person's CaseBrief is portable between systems they authorize;
  • permission that names one recipient, lists the exact fields, and expires;
  • professional evidence that cites its source and date instead of a "verified" badge;
  • delivery states that mean exactly one thing each.

OLIP does not certify lawyer competence, make legal decisions, create an attorney-client relationship, guarantee representation, or replace professional-responsibility rules. Non-goals and limits.

A complement to MCP and A2A

Where OLIP sitsOLIP is a legal-intake meaning layer on top of agent protocols (MCP, A2A), which run over HTTPS and OpenAPI, secured with OAuth 2.0 and signed receipts.OLIP: legal-intake meaningevidence · eligibility · CaseBrief · consent · handoff · statusMCP tools (agent side)A2A messages (optional)HTTPS + JSON · OpenAPI 3.1 · JSON Schema 2020-12OAuth 2.0 · JWKS · Ed25519 signed receipts

OLIP adds legal-intake meaning. It does not replace agent or transport protocols: MCP and A2A bindings and an OpenAPI 3.1 HTTPS binding are part of the specification. Interoperability.

Start where you are

For AI developers

Help a person reach one legal professional they chose, with an approval only that person can give, and status that never overstates what happened. Works from any agent, through MCP, A2A or plain HTTPS.

Path for AI agent developers

For law firms

Publish who you are, how your license can be checked, and which matters you accept, in your own words and with dates. Receive only what the person approved, with a receipt you sign.

Path for law firms

For legal software vendors

Add an OLIP endpoint to an intake or practice-management product. Map your existing states to OLIP states conservatively and test with the public conformance suite.

Path for legal software vendors

Open by design

  • Anyone may implement OLIP without paying Digital Crossings Inc., using its software, hosting with it, or holding an account.
  • Discovery order must be disclosed, and payment never changes it (paid_influence: false).
  • Conformance is decided only by a public test suite anyone can run. There is no fee and no certification badge.
  • Self-hosted firm endpoints are a first-class topology, not an exception.
  • OLIP is not a referral marketplace and has no paid ranking.

Governance and sponsorship · Licensing (granted 2026-11-07)

Current status

  • Specification: OLIP 2.0 (2026-11-14): the legal-client lifecycle, built on OLIP 1.0 (2026-11-10, Part 1 Core plus Part 2 Additions). Not adopted by any standards body.
  • 21 JSON Schemas, OpenAPI 3.1 and fictional examples, available to download.
  • Conformance: 35 of 35 checks pass on the Node reference endpoint (sponsor self-test, all results).
  • Independent implementations: 0. Hosted sandbox: not built. Outside security review: not done.

Updated 2026-11-14. Full status table.

How to contribute

OLIP needs outside review most of all: implementers, intake vendors, legal-aid groups, security practitioners and lawyers. Read the specification, try the fictional quickstart, and send comments. Every normative change ships with a schema change, a conformance test and an example.

Contribute and give feedback