Developers
Open packages, and their documentation.
Everything this site explains is in public packages you can install and read. The seller side is deterministic and small at its core: it holds no key, signs nothing and calls no network on its own. Source: @integraledger/lcp README (opens in a new tab) · Source: @integraledger/lcp: what it guarantees (opens in a new tab)
npm install @integraledger/lcp@0.5.0npm install @integraledger/terms@0.4.0npm install @integraledger/terms-mcp@0.4.0npm install @integraledger/agentic-connectors@0.4.0npm install @integraledger/profile-facilitator@0.4.0pip install integraledger-terms
The packages
Each package’s name, version and description below is read from the package itself when the site is built.
@integraledger/lcpApache-2.0
Assemble and hash an Agentic Transaction Record (ATR), and carry the hash in the payment, or beside it in an agreement payment, on the x402, MPP, AP2, ACP, UCP, ACK and card pairings this package implements, and in A2A task metadata.
@integraledger/termsApache-2.0
Buyer gate: compare the ATR hash with the served bytes, and build the payment with that hash, before signing.
@integraledger/terms-mcpApache-2.0
The buyer gate's operations as MCP tools, with a skill for the agent that uses them.
@integraledger/agentic-connectorsApache-2.0
The seller door's contract: the OpenAPI 3.1 document, TypeScript types, refusal table and vectors a connector speaks to issue an ATR, claim a payment and report a settlement.
@integraledger/profile-facilitatorApache-2.0
An x402 facilitator for the LCP profiles x402/exact/tron/lcp-trc20-memo and x402/exact/polkadot/lcp-assets-remark: verifies and settles payments whose signed transaction carries the ATR hash.
integraledger-terms
The buyer’s gate for Python, passing the same vectors as the TypeScript gate. Source: integraledger-terms (Python) README (opens in a new tab)
What @integraledger/lcp covers
67 pairings·7 protocol surfaces·21 rails and processors·27 recoverable from the chain alone
A pairing is one payment protocol, scheme and rail. Each declares where the ATR hash rides — the fingerprint of the agreement’s Agentic Transaction Record (ATR) — and what a payment through it proves. Source: lcp docs: pairings reference (opens in a new tab)
Read the documentation
- Concepts, guides and reference for
@integraledger/lcp (opens in a new tab) - The seller guide: assemble, advertise, check the payment, read the settlement (opens in a new tab)
- The buyer guide: compare, then build and sign, then finish (opens in a new tab)
- Rails: where the ATR hash rides on each chain and payment network (opens in a new tab)
- Agentic checkouts: ACP, UCP, AP2, ACK, card networks and A2A (opens in a new tab)
- The pairings reference, with each pairing’s proof sentence (opens in a new tab)
- The buyer’s gate:
@integraledger/terms (opens in a new tab) - The seller door’s contract:
@integraledger/agentic-connectors (opens in a new tab)
Read the site at technical depth
These links open each page at the technical depth: the standard, the data and the code behind each section, and how to check it yourself.
- The home page, with the ATR’s bytes and the standard’s full example
- Every protocol, with each pairing’s record
- Every rail, with its reader and entry points
- The Levels of Trust, with what the packages do at each
- Payment types: every payment type in the package, where the ATR hash rides and what each proves
The standard
The packages implement the Legal Context Protocol. Its public text, examples and governance are at legalcontextprotocol.org; any implementation, in any language, is welcome. Source: LCP Abstract (opens in a new tab) · Source: LCP governance (opens in a new tab)
Ready to see your own agreements proved?
Tell us what you sell, buy or carry, and we will show you where the agreement rides in it.
Integra Binder, hosted by Integra, does the seller’s side of each agreement and is free on test networks, with test-network USDC.