The American Arbitration Association, working with Integra Ledger and a coalition of over a dozen firms including Google, IBM, and Circle, has launched the Legal Context Protocol (LCP) — a new open standard aimed at a gap nobody else in the agent-protocol stack has addressed: what happens when an AI agent's transaction goes wrong. Payment protocols like AP2 and x402 answer what was paid. Identity and coordination frameworks answer who acted. LCP is built to answer a third question entirely: under what terms, governed by what law, and with what recourse. The protocol makes legal terms, consent, and dispute-resolution paths discoverable and verifiable at the point an agent transacts on behalf of a person or organization. Integra Ledger CEO David Fisher framed the motivation plainly: payment rails for agents are being built rapidly, but the legal layer — what was agreed, under what terms, how disputes get resolved — has been missing. AAA president Bridget McCormack described it as bringing a century of commercial dispute resolution to machine speed, with defined jurisdictional authority baked in. What makes LCP notable as infrastructure rather than just a policy statement is its lack of new dependencies: any organization running a standard web server can adopt it, with no blockchain and no intermediary required, and it's published under Apache 2.0 with governance meant to move to a neutral foundation over time. The launch landed alongside a cluster of related efforts pointing at the same blind spot. Trinsic, an identity gateway provider joining the LCP coalition, put it bluntly: the agentic commerce industry has solved payments, identity, and interoperability, but has stayed silent on transaction failure — and building a deliberate layer of verifiable records of who acted, under what authority, is what will let the space scale. Separately, Proof launched x401, a protocol for verifying the authority behind an agent's actions, intended to be submitted to the FIDO Alliance's agentic authentication workgroup and designed to complement AP2 and x402 rather than replace them. Together these announcements mark a shift in the agent-protocol conversation: after roughly a year of building discovery, payment, and identity rails, the industry is now explicitly building the accountability layer — the piece that produces evidence and recourse when something breaks, rather than just recording that a transaction happened.