Models change. Proofs remain.
Raw data never leaves. Only the proof is sent.
The Lemma API issues five proofs — provenance, authentication, authority, inference, and attribute. Prove without handing over raw data, and verification is always free.
Five kinds of proof, one API.
- 01 来歴 · Provenance Prove origin without handing over the original. Prove where data came from and that it's untampered — without exposing the contents.
- 02 認証 · Authentication Prove identity without sending a key. Prove who you are without ever sending a key.
- 03 権限 · Authority Delegate authority without handing over a key. Build delegation that runs at full speed in scope and stops outside it.
- 04 推論 · Inference Prove inference without disclosing the model. Independently verify the consistency of an AI's inputs and behavior.
- 05 属性 · Attribute Prove you meet a requirement without revealing the attribute. Prove regulated attributes selectively — without handing over the original.
Issuance is billed; verification is always free. Each proof's detail is on its own page (authentication → Seal).
Trust across every phase.
Keep your AI workflow as-is. Add the Lemma API as one layer, and proof rides every phase — from input to delegated action.
Authentication (identity) applies across every phase.
One middleware layer in your existing flow.
One SDK. It rides the standards you already use; issuance is metered over x402, verification is public and free.
- 01 Mint a key Issue an API key in the Dashboard. Dashboard
- 02 Issue a proof Issue from the SDK — settled per issuance via x402, or on a monthly allowance. SDK · x402
- 03 Verification is free Anyone, anywhere confirms it — with no raw data. public · free
It rides your existing flow as one middleware layer. Endpoints and code samples are in the specs. This page never calls the API.
Data stays in place.
Only proofs travel.
The source mints a proof, only the necessary parts are selectively disclosed, and a verifier checks them with a public key. Through all three phases, raw data never moves.
Mint the proof at the source
Embed the Lemma SDK at the source. Issue attribute proofs for data, models, and authority. Raw data never leaves.
Reveal just enough
Selectively disclose only the facts a verifier needs — authority, attribute, integrity. Raw data is never touched.
Anyone can confirm
Anyone, anytime, verifies authenticity with a public key. Optionally anchor as tamper-evident audit attestations.
Proprietary cryptography,
three cores.
Three core technologies make the trust infrastructure work — establishing “it’s the same thing,” “disclose only this,” and “no one can rewrite it,” all without touching the original data.
Proof
Turn business rules like “18 or older” or “revenue over threshold” into machine-verifiable cryptographic facts. Prove a statement’s truth without touching the original.
Disclosure
Keeping the binding to the original issuer signature, the holder reveals only the attributes a model needs. Minimize what AI receives as input.
Provenance
Anchor the document commitment, schema, issuer, and ZK verification result on-chain. Fix it as provenance that can be neither rewritten nor erased.
Issuance is billed; verification is free.
You pay to issue; verification is always free. Beyond usage-based billing with no monthly fee, flat-rate quota / grade plans are coming soon. On-chain permanence is optional.
See pricing on /pricing →Authentication is this API's authentication suite (Seal is its landing page). Trust402 is the wrapper for using this API self-serve (Pay / Sell).
Built for decisions that matter.