Protocol Integration
Protocol-by-protocol integration tables showing exactly how ALC embeds into MPP, ACP, UCP, x402, Visa TAP, A2A/MCP, AP2, and Mastercard Agent Pay.
The Agent Legal Context protocol uses existing extension mechanisms in each commerce protocol. No core specification changes are required for any protocol.
MPP (Machine Payments Protocol)
| Integration Point | Mechanism | Description |
|---|---|---|
| Terms reference in challenge | opaque field | contentHash included in 402 challenge |
| Terms reference in payment | TIP-20 memo (32 bytes) | contentHash in transfer memo on settlement |
| Acceptance in credential | Credential payload extension | EIP-712 TermsAcceptance alongside payment proof |
Tier 1: contentHash in MPP challenge opaque field. TIP-20 transfer memo carries the hash on settlement.
Tier 2: MPP challenge signals "acceptance required." Agent signs EIP-712 TermsAcceptance, includes signed acceptance in MPP credential alongside payment proof.
Tier 3: Negotiation happens outside MPP (agent-to-agent via A2A or direct). Once terms are agreed, payment flows through MPP with contentHash binding.
ACP (Agentic Commerce Protocol)
| Integration Point | Mechanism | Description |
|---|---|---|
| Terms reference in session | Session metadata | {"contentHash": "0x..."} in checkout session |
| Acceptance before checkout | Pre-completion step | Terms acceptance required before complete_checkout_session |
| Discovery alongside ACP | Well-known URI | legal-context.json served alongside acp.json |
Tier 1: contentHash in ACP checkout session metadata.
Tier 2: ACP extension for terms acceptance. Agent must accept before complete_checkout_session.
Tier 3: ACP's 11-state checkout lifecycle could be extended to include negotiation states.
x402
| Integration Point | Mechanism | Description |
|---|---|---|
| Terms reference | Response header | X-Integra-Hash header in payment response |
| Terms binding | Payment metadata | contentHash included in payment scheme data |
x402 is lightweight by design. ALC integration is correspondingly minimal: headers and metadata. Terms acceptance (Tier 2) is a prerequisite step before the x402 flow initiates.
UCP (Universal Commerce Protocol)
| Integration Point | Mechanism | Description |
|---|---|---|
| Terms in mandate | Cryptographic mandate extension | contentHash embedded alongside checkout terms |
| Capability declaration | Extension capability | integra capability in server profile |
UCP's cryptographic mandate model naturally extends to include terms acceptance -- the mandate already embeds transaction terms and requires signing. ALC provides the enforcement and verification layer that UCP explicitly declares out-of-scope.
Visa TAP
| Integration Point | Mechanism | Description |
|---|---|---|
| Terms in agent intent | Signed data field | contentHash in agent intent signature payload |
| Discovery | MCP server | ALC operations exposed as MCP tools at Visa's MCP endpoint |
TAP's three-signature model (agent intent, consumer recognition, payment container) can incorporate terms acceptance in the agent intent signature. TAP's PKI-based agent identity provides the agent verification needed for Tier 2 and Tier 3.
A2A / MCP
| Integration Point | Mechanism | Description |
|---|---|---|
| Agent metadata | Agent Card extensions | contentHash and API URL in agent card |
| Task binding | Task metadata | integra-context-hash in task metadata |
| Legal tools | MCP tool definitions | ALC operations exposed as MCP tools |
A2A Agent Cards carry the contentHash and API URL as metadata extensions. Any counterparty agent can discover terms before initiating a task. MCP tool definitions make ALC operations (verify, accept, dispute) available to any MCP-compatible model.
AP2 (Agent Payments Protocol)
| Integration Point | Mechanism | Description |
|---|---|---|
| Terms in mandate | Cart/Intent/Payment mandate metadata | {"integra-evidence-hash": "0x..."} in mandate |
| Multi-party evidence | VDC extensions | Cart + intent + payment linked to IntegraRecord |
| Dispute evidence | Mandate hash anchoring | All three mandates hashed as single evidence entry |
AP2's three-mandate model (cart, intent, payment) maps directly to ALC's multi-party evidence structure. All three mandates can be content-addressed and linked to a single on-chain record, providing comprehensive evidence for dispute resolution.
Mastercard Agent Pay
| Integration Point | Mechanism | Description |
|---|---|---|
| Terms in Agentic Token | Token metadata | contentHash in Agentic Token metadata |
| KYA registration | Know Your Agent extensions | Agent's IntegraRecord referenced during KYA |
| Verifiable Intent | SD-JWT claim extensions | integra_terms_hash as VI disclosure |
Mastercard's Agentic Token metadata and KYA registration process can reference IntegraRecords. The Verifiable Intent (SD-JWT) disclosure mechanism can include integra_terms_hash as a claim, binding agent intent to specific terms.