Legal Context ProtocolAppendix D: Comparison to Existing Protocol Standards
How LCP relates to MPP, ACP, UCP, x402, AP2, TAP, Agent Pay, Verifiable Intent, A2A, MCP, and ACK.
The following table compares LCP's capabilities against the major agentic commerce and agent infrastructure protocols.
Comparison Table
| Feature | LCP | MPP | ACP | UCP | x402 | AP2 | TAP | Agent Pay | Verifiable Intent | A2A | MCP | ACK |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Terms discovery | Yes | No | URLs only | URLs only | No | No | No | No | No | No | No | No |
| Terms format signaling | Yes | No | No | No | No | No | No | No | No | No | No | No |
| Terms identified by hash | Level 2+ | No | No | No | No | No | No | No | No | No | No | No |
| Explicit acceptance | Level 3 | No | No | Partial | No | No | No | No | No | No | No | No |
| Dispute resolution clause (verifiable) | Level 4 | No | No | No | No | No | No | No | No | No | No | No |
| Dispute resolution service catalog | Level 4 | No | No | No | No | No | No | No | No | No | No | No |
| Payment processing | No | Yes | Yes | Yes | Yes | Yes | Via Visa | Via MC | No | No | No | Yes |
| Checkout lifecycle | No | No | Yes | Yes | No | No | No | No | No | No | No | No |
| Agent identity | No | No | Partial | Partial | No | Partial | Yes | Yes | Partial | Partial | No | Yes |
| Consumer authorization | No | No | No | Partial | No | Yes | Yes | Yes | Yes | No | No | Partial |
| Agent-to-agent communication | No | No | No | No | No | No | No | No | No | Yes | No | No |
| Agent-to-tool connectivity | No | No | No | No | No | No | No | No | No | No | Yes | No |
Summary
LCP is complementary to all of these protocols. It provides the legal context layer — terms discovery, verification, signed acceptance, and dispute resolution hooks — that every other protocol defers. The authorization protocols (TAP, Agent Pay, Verifiable Intent, AP2) provide the consumer side; LCP provides the merchant side. Together they form a complete agreement. See Protocol Integration for per-protocol integration patterns and Relationship to Authorization Protocols for the relationship to authorization protocols. Mastercard Agent Pay appears in the matrix for completeness; as a proprietary program without a public integration surface, it has no integration illustration under Protocol Integration.
Appendix B: Pattern Illustrations
Abstract structural illustrations of the settlement binding patterns — Native Field, Overlay Contract, Sidecar Attestation, Opaque Challenge, Id-Reuse, Protocol Extension, HTTP-Layer Advisory.
Appendix E: Legal Significance
Mapping the LCP trust levels to recognized contract doctrines under U.S. and EU law — browsewrap, evidentiary integrity, electronic signature, recourse, and cross-cutting doctrine.