The open protocol for legal context in agentic commerce.
Every commerce protocol handles payments. None handle what happens when a transaction goes wrong — terms enforcement, dispute resolution, agreement recording, or legal enforceability. One file. One API. The missing legal layer.
22+ protocols analyzed. Every category defers the same things.
| Protocol Category | What They Handle | What They Defer |
|---|---|---|
| PaymentsMPP, x402, Tempo | Value transfer, micropayments, stablecoins | Terms binding, identity, enforceability |
| CommerceACP, UCP, AP2 | Checkout, payment delegation, cart | Dispute resolution, terms enforcement |
| IdentityVisa TAP, Mastercard Agent Pay | Agent verification, PKI, authorization | Agreement context, dispute resolution |
| AuthorizationVI, Tempo Keychain | Spending limits, delegation scope | What happens when scope is exceeded |
{
"version": "1.0",
"contentHash": "0x7f83b165...d9069",
"api": "https://api.integraledger.net/v1/records/0xabcdef..."
}Any agent fetches legal-context.json from a vendor's domain. One HTTP call reveals the terms hash, the verification API, and whether acceptance is required.
Every terms document is content-addressed by its SHA-256 hash. The hash is anchored on-chain. Any party can prove a document is authentic and unchanged.
When things go wrong, the API provides the dispute process, the contact information, and the evidence anchor. The on-chain record is the ultimate backstop.
Proportional trust for proportional stakes.
The transaction itself is the proof. Terms are bound via payment memo. No signature required.
$0.001 API calls, micropayments, high-volume machine commerce
Counterparty signs the terms hash via EIP-712 before transacting. Cryptographic proof of affirmative consent.
SaaS agreements, data licenses, enterprise SLAs
Agents dynamically negotiate terms. Both parties sign the final agreement. Full on-chain record with dispute resolution.
Supply chain contracts, financial settlements, joint ventures
Hash, anchor, reference. No vendor dependency. ~1 hour.
Serve legal-context.json. Point to the API. ~1 day.
Protocol-specific integration via existing extension mechanisms.
ADR, escrow, compliance, tokenization, negotiation.