Regulatory Attribute Proof.
Pass only the facts AI needs as proofs — never the personal data.
Send regulatory attributes — KYC, age, location — to AI without ever handing over the original. One of the five proofs that make up the Lemma API.
Keep the original in your hands — pass only the attributes to AI.
Extract the attributes you need and deliver them to AI together with a cryptographic proof. The original stays in-house.
Original data
Holds the full customer record (name, address, date of birth, transaction history, and more).
Extract attributes,
attach a proof
Only attributes + proof arrive
Think of it like a seal-registration certificate (inkan shōmeisho).
When you open a bank account, you submit a seal-registration certificate (inkan shōmeisho) rather than your entire family register — you may have done exactly this. It is a document that officially certifies only the facts that are needed. Lemma's Regulatory Attribute Proof works the same way: instead of handing your whole original data set to AI, you pass only the attributes that are needed, together with a proof.
The attribute facts + proof
- ✓The attributes a regulation asks about, such as
jurisdiction = JP - ✓The cryptographic signature of the issuer (a KYC provider, a public agency, and so on)
- ✓A ZK proof that any third party can independently verify
Bring AI even into work that handles personal information.
How it differs from masking, encryption, and monitoring.
Hiding, protecting, or observing alone can't deliver the attributes AI needs.
P4 is one of the five proofs that make up the Lemma API.
Business scenarios that use this proof.
Prove only the attributes — with cryptography built in-house.
Selective disclosure
Disclose only the attributes that are needed and mathematically conceal the rest. Unlike masking, a third party can verify it independently.
Zero-knowledge proof
Prove "age 18 or over" without handing over the date of birth. Only the truth of the attribute reaches the verifier.
Issuer signature
Cryptographically fix the issuer of an attribute (a KYC provider, a public agency, an internal system). Who attested it can be verified after the fact.
{
"$schema": "your.attribute.v1",
"jurisdiction": { "disclosed": "JP" },
"age_over": { "disclosed": 18 },
"aml_clear": { "disclosed": true },
"name": { "hidden": true },
"address": { "hidden": true },
"birth_date": { "hidden": true },
"issuer": "kyc-provider.jp",
"zk_proof": "0x9c4f...e7d2"
}
Technical documentation related to this proof.
Issue attributes as an API.
This is the “attribute suite” of the Lemma API. Prove that requirements are met — without revealing the attributes themselves. 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.