igrantio-credential-schema-age-verificationlisted

# Age Verification credential schema ## When to use Use this skill when you issue or ask for an **Age Verification** attestation. The credential proves that the holder is over an age limit. It carries no name, no date of birth, and no document number. The holder shows one boolean and keeps the rest of the credential hidden. The registry publishes this schema in **one format only: `mso_mdoc`**. The metadata sets `isMsoMdoc` to `true`, and `isSdJwt` and `isJwt` to `false`. There is no SD-JWT VC form and no JWT form of this schema in the registry. This page describes registry version **2026.4.1**, the latest version of the template. ## Prerequisites - An **iGrant.io Organisation Wallet Suite (OWS) API key**. Get it from [support@igrant.io](mailto:support@igrant.io). Keep it on the server, in an environment variable or a secret manager. The browser never sees it. - The **OWS environment** the key belongs to. The default is **demo** (`https://demo-api.igrant.io`). Use **staging** (`https://staging-api.igrant.io`) only when the integrator asks for it. A key works only in its own environment. ## Ask the integrator first Ask one question at a time. Wait for the answer. Give the recommended default with each question. Look up facts in the project (framework, environment variables, an existing backend) instead of asking for them. Record the answers before you write code. 1. **Environment** - demo or staging? _Default demo (`https://demo-api.igrant.io`); a switch late