Verifiable Origin.
Pass the origin of the data AI reads as a tamper-proof proof.
Turn the "where it came from" of business documents, API responses, and IoT measurements into a cryptographic proof that travels with the data into AI inputs and business systems. One of the five proofs that make up the Lemma API.
Pass the origin of data in a form anyone can verify.
Attach the issuer's cryptographic signature and a tamper-proof hash to documents and data, then deliver it. AI and recipients can independently verify the origin without accessing the original.
Original data
Data the issuer can verify, such as business documents, API responses, and IoT measurements.
Hash + issuer signature
Data arrives with provenance
Think of it like a notarized deed.
When you record an important contract or will, a notary creates a notarized deed certifying that "this document was created by this person, on this date" — have you ever gone through this? Lemma's Verifiable Origin works the same way. It cryptographically fixes "who issued the data, and when" so a third party can independently verify it later.
The provenance facts + proof
- ✓
sourceHash(the data's fingerprint) - ✓
issuer(the issuer's cryptographic signature) - ✓
issuedAt(issuance time) - ✓Provenance chain (traceability of the chain)
Chain the trust of data structurally.
How is it different from hashing, digital signatures, and backups?
The individual techniques exist, but Lemma is what brings "origin," "tamper-proof," and "independent verification" together in a single structure.
P1 is one of the five proofs that make up the Lemma API.
Business scenarios that use this proof.
Prove the origin alone, with purpose-built cryptography.
Issuer signature
Cryptographically fixes the data's issuer (a vendor, a government body, an internal team). Who issued it can be independently verified later.
Hash commitment
Keeps the original's contents hidden while publishing only the unique fingerprint. Tampering is mathematically detectable.
Provenance chain
Records multi-tier issuance and handoffs as a chain. Guarantees continuity of origin across multi-tier supply chains and RAG indexes.
{
"$schema": "your.provenance.v1",
"sourceHash": "0x9c4f...e7d2",
"issuer": "kyc-provider.jp",
"issuedAt": "2026-06-05T10:00Z",
"lineageChain": [
{ "node": "supplier-a", "hash": "0x71..." },
{ "node": "manufacturer-b", "hash": "0x9c..." }
],
"attestation": "0xa8...4f3e"
}
Technical documentation related to this proof.
Issue provenance as an API.
This is the “provenance suite” of the Lemma API. Prove where data and content came from — and that they haven’t been tampered with — without handing over the original. Verification is always free.
- Issue proofs (billed only when you issue)
- Selective disclosure (share only the facts you need)
- On-chain permanence (optional)
Rates are on the pricing page; endpoints and code samples are in the specs.