Products Lemma APIProof issuance & verification platformTrust402Delegate to agents, and transactSealSign-in for the agent era — no keys handed over
Use cases Manufacturing & Critical InfraInspection Record AssuranceFinance & FinTechCounterparty Record VerificationPublic SectorCertificate-less ProceduresHealthcareQualified Worker AssuranceProcurement & Supply ChainSupplier Credential MonitoringMedia & ContentContent AuthenticityService & RetailCross-group IdentityAI Adoption (cross-industry)AI Run GovernanceDevelopers & Agent OpsAgent Authority Control ▸ Browse the use-case index
Pricing
Resources Critical BriefThe frontier of AI × trustBlogThinking and implementation notesDocumentationAPI & specsVerification CenterReal verification & issuance countsAbout usFRAME00, Inc.ContactSales & press inquiriesGlossaryDefinitionsFAQFrequently asked questions
Get Started ↗ JA
Home/Use cases/Procurement & supply chain
Procurement & supply chain

Not whether it arrived — whether it's valid, settled on the spot.

Instead of collecting licenses and ISO certificates and checking them by eye, take them on presentation and settle it on the spot. Both the wait in supplier review and the checking workload drop sharply.

Talk to us Verify a proof yourself
Procurement system — checking a presented certificate
Not tampered with
DOC HASH0x68d4…9f01
IssuerCertification body
Issued2026-07-28
SubjectISO 9001 certificate
Proof classProvenance
Signature matches Tamper check Issuer confirmed
The proof layer
is running now
Verification Center live 3 proof-backed data feeds Verification is free
See it for yourself →
01 — Why LemmaWhat slows a supplier review down is collecting, checking and tracking expiry.

Supplier qualification is three jobs — collect the certificate, check it by eye, track when it expires. All three are manual and all three recur. With several hundred suppliers, a dedicated team still cannot keep up. And whether a submitted certificate is genuine never actually gets established: what you confirm is that it arrived, not that it is valid.

What you want isn't the document.
It's the fact that it's valid.

02 — What changesThree things Lemma changes
From collect-and-store to present-and-settle

Stop gathering certificates one by one and filing them. Take them on presentation, when you need them, and settle it on the spot.

Supplier portal
Certificate presentedISO 9001 (to 2027-03)
IssuerCertification body
Query to issuerNot needed
VerdictNot tampered with
A supplier's certificates
Construction licenseValidProof attached
ISO 9001 (to 2027-03)ValidProof attached
Liability insuranceValidProof attached
Waste transport permitValidProof attached
Expiry tracking, simplified

Because a presented certificate carries its issue date, an expired one shows up in the verdict. You stop running a tracking ledger of your own.

The same check, past your first tier

A proof still verifies after it has been forwarded, so tier-2 suppliers and beyond go through the same flow.

POST /v1/proofs/verify
// A forwarded proof verifies exactly the same way { "docHash": "0x68d4…9f01" } // What comes back { "valid": true, "issuer": "cert-body" }
03 — Threat casesWhat happened when the check became a formality.

Three cases from this area, drawn from the Lemma Critical Briefs. In each one the paperwork was complete — and did not match reality.

No. 041Over 60,000 aircraft engine parts circulated on forged airworthiness certificatesAttribute Proof Bypass No. 040Carbon credits issued and sold against forest protection that never happenedAttribute Proof Bypass No. 032Inside a legitimate platform, the payout bank account was silently rewrittenAttribute Proof Bypass

See every Brief in this area →

04 — How it worksThree steps, and that's it.
Issuing the proof
RecordISO 9001 certificate
IssuerCertification body
What is sentHash only
Issued 0x68d4…9f01
01Attach a proof
Why it holdsChange one character in the certificate and it no longer matches the proof.
One API call at issuance, or register it from a form. The body of the certificate is never sent.
What the supplier presents
ISO 9001 certificate
Proof attached — verify here
02Hand it over
Why it holdsThe proof itself is about 200 bytes, and survives being forwarded.
The certificate carries a verification link. Nothing about how it is exchanged has to change.
The buyer's screen
Not tampered with
SignatureTamper checkIssuer
03They check it
Why it holdsThe receiving side settles it alone, without contacting the issuer.
Open the link and the verdict appears. No account, no key.
05 — Use casesHow it is used in this industry
Check a supplier's licenses and ISO certificates on presentationLemma Take ESG claims from suppliers with proof, not with a spreadsheetLemma Keep compliance evidence current across a distributed network of sitesLemma Confirm that the people on site hold the qualifications they claimLemma
06 — Latest newsAdoption, and what is moving in this area
Case study2026.08.05 Proving residents' activity records are genuine — without exposing personal data
Case analysis2026.09.01 AnonyMousKIT: AI voice agents posing as 'Apple Support' extracted unlock passcodes from st…
Blog2026.08.21 Reconcile without opening the books. A smoother month-end for stablecoin payments

See all blog posts →

Supply Chain

How much of your review
is spent collecting paper?

We map your current supplier-qualification flow with you and separate what is collection from what is actually verification. It starts with a 30-minute call.

Talk to us See the Verification Center