Already 3 months old when the scout caught it.
Legal Context Protocol
What it is
The Legal Context Protocol (LCP) is an open standard that makes the legal terms of an agent-to-agent or agent-to-merchant transaction discoverable, verifiable, and provable after the fact. A service publishes its terms as a JSON document at a fixed well-known URI (/.well-known/legal-context.json); a SHA-256 hash pins the exact text a buying agent saw at the moment of the deal; and a cryptographic signature over that hash gives non-repudiable proof of who agreed to what, when. The spec is layered — one required field, the rest optional — so an implementer can adopt more of it as transaction stakes rise.
Why it's emerging now
Agentic commerce removes the human click-through that used to constitute "acceptance" of terms: an agent now discovers a product, negotiates, and pays on a person's behalf in milliseconds, with no standard way afterward to prove what was agreed, which law governs, or how to dispute it. LCP was launched June 24, 2026 by the American Arbitration Association and Integra Ledger specifically to close that gap, with Google, IBM, Circle, Wayfair, and a wide coalition of payments and identity infrastructure firms as founding contributors — signaling that "who governs the contract when an AI agent signs it" has become a live infrastructure question as agent-mediated purchasing scales.
How it relates to what you know
It sits alongside protocols like A2A, ACP, and MCP as another instance of the same shape: a small, well-known-URI-based discovery convention plus a signed-exchange pattern, but aimed at the legal/consent layer of a transaction rather than tool or model context. It's a narrower cousin of the still-unadopted terms.txt research proposal on the watchlist — both use a /.well-known/ file to make machine-access terms legible to agents — but LCP is shipping, multi-vendor-backed infrastructure focused on binding consent and dispute resolution for payments, not per-path crawl/access pricing.