igrantio-credential-schema-authenticatorlisted

Claim path pointer schema for the iGrant.io Authenticator credential (credential type io.igrant.authenticator) from the iGrant.io verifiable data registry. It holds one claim, email_address, and the registry publishes it in all three formats: dc+sd-jwt, jwt_vc_json and mso_mdoc. Use this skill when you create an authenticator credential definition on the iGrant.io OpenID4VC API, when you build passwordless sign-in with a wallet, or when you need the exact claim path for each of the three credential formats.
L3-iGrant/skills · ★ 1 · API & Backend · score 75

Install: claude install-skill L3-iGrant/skills

# iGrant.io Authenticator credential schema ## When to use Use this skill when you issue or ask for an **iGrant.io Authenticator** credential. The credential proves control of one email address, and nothing else. It is the smallest schema in the registry: one claim. iGrant.io uses it for passwordless sign-in, where the user presents the credential in place of a password. The registry publishes this schema in **all three formats**: | Format | Metadata flag | Identifier to send | | --- | --- | --- | | `dc+sd-jwt` | `isSdJwt: true` | `vct` | | `jwt_vc_json` | `isJwt: true` | `type` | | `mso_mdoc` | `isMsoMdoc: true` | `doctype` | This page describes registry version **2025.7.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. **Environmen