Payment protocols answer what was paid. Identity frameworks answer who acted. Nothing answered under what terms, governed by what law, and with what recourse — until the Legal Context Protocol.
On June 24, 2026, the American Arbitration Association (AAA) and Integra Ledger launched LCP: an open standard that puts a merchant's legal terms, consent record, and dispute path at one predictable URL — https://{domain}/.well-known/legal-context.json — so an AI agent can verify what it's agreeing to before any payment fires.
Why it blew up this week
On September 23, 2026, PYMNTS ran the story that turned LCP from a June spec into a news cycle: "A budget for a purchase is not permission for every choice an agent makes inside it."
- A shopper who tells an agent "book a vacation under $3,000" approved a budget — but the agent can pick the airline, accept a nonrefundable fare, add insurance, and split charges across cards without asking again.
- Until LCP, no record existed of which decisions the shopper approved and which the agent made alone.
- Only 23% of U.S. consumers trust AI to handle payments (PYMNTS, Sept 23, 2026) — while retailers like Target already treat an agent's choices as the customer's own.
That's not a protocol problem. It's a consent ledger problem.
The wire format: one JSON file
Before transacting, an AI agent fetches /.well-known/legal-context.json from the counterparty's domain over HTTPS. The only required field is terms — an absolute URL to a standalone, downloadable terms document. No blockchain. No API keys. No third-party service.
{
"terms": "https://your-domain.com/terms.html",
"atr": "sha256:9f2c…ab41",
"dispute_resolution": "https://www.adr.org/"
}
Optional fields add provability (SHA-256 ATR hash proving exactly what the terms were at transaction time), explicit acceptance, and dispute-resolution hooks. Any web server can implement LCP in minutes by serving one JSON file.
Four levels of trust
| Level | What the agent gets | When to use it |
|---|---|---|
| 1 — Informational | Terms discoverable; proceeding = implicit consent | Low-value reads, micropayments |
| 2 — Provable | ATR hash proves the exact terms, unchanged | Anything you'd want an evidence trail for |
| 3 — Signed | Digital signature binds a party to terms | High-value transactions |
| 4 — Integrated | Hooks to dispute resolution, escrow, compliance | Regulated / enterprise commerce |
Each level is independently valuable; none is required. A $0.001 x402 API call doesn't need arbitration hooks, but it should still be findable.
How it connects to decision-gated payments
LCP is the consent ledger a decision gate needs. The gate decides whether money moves — ≥0.80 auto-pay, 0.50–0.79 hold, <0.50 escalate — and LCP proves what everyone agreed to, while x402 moves it. When a payment holds, the human reviews which terms and which choices they're signing off on. The gate decides whether money moves, LCP proves what everyone agreed to, x402 moves it.
We adopted it — Level 2, live
ScriptMasterLabs published /.well-known/legal-context.json on its own x402-selling domain, pointing at machine-readable x402 terms with a SHA-256 ATR hash: Level 2 (Provable). Verify it:
curl https://scriptmasterlabs.com/.well-known/legal-context.json
Honest caveats
- No blockchain required. The spec needs nothing beyond HTTPS. It's a web standard that happens to have blockchain contributors.
- It's draft, not law. v1.0 is out for community review under Apache 2.0. No court has tested an LCP record yet.
- The x402 wiring is real but thin. The official site lists x402 among complemented protocols "through existing extension mechanisms" — no dedicated x402+LCP spec yet.
- Adoption numbers: couldn't verify. We found no published count of live legal-context.json files. So we published ours — now there's at least one you can curl.
Founding contributors: Google, IBM, Circle, Wayfair, Stellar Development Foundation, Ava Labs, UiPath, Cardano, Hedera, Crossmint, Pinata, Aptos Foundation, Sei Labs, Mysten Labs, Trinsic, Baselayer, First Person Cooperative. Gartner projects that by 2028, 90% of B2B purchases will be intermediated by AI agents, channeling more than $15 trillion through automated exchanges.
Full piece with receipts: https://scriptmasterlabs.com/legal-context-protocol
Top comments (0)