Provenance verification

Verify that an AI output came from a specific model, with a specific input, under a specific policy.

Finds bugs ≠ proves decisions.

3 STEPS

What this demo shows

01

Pick a sample

3 industries × Valid (legitimate) / Invalid (tampered, model-swap, duplicate) — 6 cases in all.
02

Press Verify

A 5-step cryptographic verification runs: schema → envelope → input commitment → output commitment → policy.
03
Read the result
- Valid What was cryptographically proven, and what it changes in production.
- Invalid What Lemma rejected, and why.

Pick a sample

Six bundled samples cover three industries with one valid and one invalid pair each. Or upload your own proof bundle — verification runs entirely in your browser.

Banking & Finance

Loan approval (valid)

A regional bank approves a ¥5,000,000 small-business loan. The applicant's exact income is never disclosed to the bank's AI; Lemma proves only that income exceeds the policy threshold and that the applicant is not on any AML watchlist.

Stakes:

Borrower privacy preserved
Regulatory audit trail produced

Regulatory: PPSIKYC/AMLGDPR

Primitives: BBS+Groth16

Loan approval (tampered output)

The same loan approval, but the approval document was edited after the AI signed it. Lemma detects the tampering before the document is presented to compliance.

Stakes:

Audit integrity
Bank liability

Regulatory: PPSIKYC/AML

Primitives: Poseidon

Manufacturing

Process compliance (valid)

A parts manufacturer ships a batch to an EU buyer. Lemma proves the production process conformed to the registered ESG/CBAM-compliant specification.

Stakes:

Supply-chain trust
EU import compliance

Regulatory: EUDRCBAM

Primitives: Groth16

Process compliance (model swap)

The same shipment, but a different AI inspection model was substituted between certification and shipment. Lemma detects the substitution via envelope signature mismatch.

Stakes:

Process trust
Recall liability

Regulatory: EUDRCBAM

Primitives: BBS+Poseidon

Agent Economy

Agent chain + x402 payment (valid)

An autonomous agent purchases an API service via x402 payment. Lemma proves the agent had delegation authority and that the payment receipt is genuine.

Stakes:

Delegation integrity
Payment receipt non-repudiation

Primitives: BBS+Groth16

Agent chain (duplicate)

The same proof is submitted twice across two settlement steps — for example, a stuck retry loop in an agent pipeline. Lemma detects the duplicate proof_id and rejects the second submission.

Stakes:

Settlement integrity
Double-spend prevention

Primitives: Poseidon

Upload a custom proof JSON Stays in your browser. We never receive the file.

Pick a sample to begin.

Provenance verification

What this demo shows

Pick a sample

What was cryptographically proven

What this means in production

What went wrong