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)

Sources (2)

@integraledger/lcp README⁠ (opens in a new tab) · @integraledger/lcp: what it guarantees⁠ (opens in a new tab)

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 x402, MPP, AP2, ACP, UCP, ACK and card payments across chains and rails, and in A2A task metadata.
npm⁠ (opens in a new tab)Source⁠ (opens in a new tab)
@integraledger/termsApache-2.0
Buyer gate: compare the ATR hash with the served bytes, and build the payment with that hash, before signing.
npm⁠ (opens in a new tab)Source⁠ (opens in a new tab)
@integraledger/terms-mcpApache-2.0
The buyer gate's operations as MCP tools, with a skill for the agent that uses them.
npm⁠ (opens in a new tab)Source⁠ (opens in a new tab)
@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.
npm⁠ (opens in a new tab)Source⁠ (opens in a new tab)
@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.
npm⁠ (opens in a new tab)Source⁠ (opens in a new tab)
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)
PyPI⁠ (opens in a new tab)

Sources (1)

integraledger-terms (Python) README⁠ (opens in a new tab)

The standard

Each version below is the one the site was built against, read from the package’s own package.json.

@integraledger/lcp: 0.3.0
@integraledger/terms: 0.2.0
@integraledger/terms-mcp: 0.2.0
@integraledger/agentic-connectors: 0.2.0
@integraledger/profile-facilitator: 0.2.0

The code

Compiled against the published packages when the site is built.

Install

npm install @integraledger/lcp
npm install @integraledger/terms
npm install @integraledger/terms-mcp
npm install @integraledger/agentic-connectors
npm install @integraledger/profile-facilitator
pip install integraledger-terms

What `@integraledger/lcp` covers

pairings: 67
protocol surfaces: 7
rails and processors: 21
recoverable from the chain alone: 23

A pairing is one payment protocol, scheme and rail. Each declares where the ATR hash rides — the unique 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)

Sources (1)

lcp docs: pairings reference⁠ (opens in a new tab)

The standard

The package’s registry, BINDINGS, holds every pairing with its pattern record. This lists the pairings whose ATR hash anyone can read back from the settled transaction alone. Source: lcp docs: recovering H from the chain alone⁠ (opens in a new tab)

The code

Compiled against the published packages when the site is built.

Every pairing, from the registry

src/snippets/registry.ts

// The package's registry holds every pairing with its pattern record: here, the pairings whose fingerprint anyone can
// read back from the settled transaction alone.
import { BINDINGS } from '@integraledger/lcp';

export const recoverable = BINDINGS.filter((b) => b.pattern.zeroPartyRecoverable).map((b) => b.id);

Read the documentation

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 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)

Go to legalcontextprotocol.org⁠

Sources (2)

LCP Abstract⁠ (opens in a new tab) · LCP governance⁠ (opens in a new tab)

The standard

The public text and its example documents are versioned on GitHub; every LCP § on this site links to the section it cites. Source: LCP Abstract⁠ (opens in a new tab) · Source: LCP examples⁠ (opens in a new tab)

The code

Compiled against the published packages when the site is built.

Read a discovery document as the standard defines it

src/snippets/discovery.ts

// An agent, before it transacts: read a service's legal front door and the terms it points to.
import { isRefusal } from '@integraledger/lcp';
import { parse, WELL_KNOWN_PATH } from '@integraledger/lcp/discovery';

export async function legalContext(origin: string) {
  const response = await fetch(new URL(WELL_KNOWN_PATH, origin));
  const read = parse(new Uint8Array(await response.arrayBuffer()));
  if (isRefusal(read)) return read;
  return read.document; // terms, and at higher levels atrHash, acceptanceRequired, disputeResolution…
}

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.

The hosted appliance is free on test networks, with test-network USDC.

Talk to us

The packages

What @integraledger/lcp covers

Read the documentation

Read the site at technical depth

The standard

Ready to see your own agreements proved?

What `@integraledger/lcp` covers