igrantio-credential-schema-age-verification

Defines claim path pointers for issuing EUDI Age Verification mdoc credentials via the iGrant.io OpenID4VC API.

1|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/L3-iGrant/skills --skill igrantio-credential-schema-age-verification-l3-igrant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: igrantio-credential-schema-age-verification
Source: https://github.com/L3-iGrant/skills/tree/main/credential-schemas/igrantio-credential-schema-age-verification
Command: npx skills add https://github.com/L3-iGrant/skills --skill igrantio-credential-schema-age-verification-l3-igrant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Issuing a proof-of-age credential requires the exact claim paths, namespace, and doctype of the EUDI Age Verification attestation; getting any of these wrong makes wallets reject or misread the credential. This Skill provides the authoritative claim path pointer schema (doctype eu.europa.ec.av.1) so integrators create correct credential definitions on the iGrant.io OpenID4VC API. ## Core Features & Use Cases - Exact claim path pointers: Provides the five selectively disclosable age_over booleans (14, 16, 18, 21, 65) with mandatory and limitDisclosure flags for the mso_mdoc format. - API-ready payload: Shows how to build the POST /v2/config/digital-wallet/openid/sdjwt/credential-definition request with version, doctype, validationPath, and credentialBindingMethods. - Registry-mirrored schema: Mirrors the iGrant.io verifiable data registry template (version 2026.4.1) with links to the raw schema and metadata so the registry remains the source of truth. - Use Case: An integrator building an age-gated service creates an mdoc credential definition that lets holders prove age_over_18 while keeping every other attribute hidden. ## Quick Start Use the igrantio age verification credential schema to create an mso_mdoc credential definition for doctype eu.europa.ec.av.1 on the iGrant.io OpenID4VC API.

Frequently Asked Questions about igrantio-credential-schema-age-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an age verification credential definition on iGrant.io?▼

Call POST /v2/config/digital-wallet/openid/sdjwt/credential-definition with credentialFormat mso_mdoc, doctype eu.europa.ec.av.1, version version_01, validationPath $, and the claims array of age_over booleans. An iGrant.io OWS API key for the demo or staging environment is required.

What claims does the EUDI Age Verification attestation contain?▼

It contains five boolean claims: age_over_14, age_over_16, age_over_18, age_over_21, and age_over_65, all under the namespace eu.europa.ec.av.1. Only age_over_18 is mandatory; every claim supports selective disclosure.

Does the age verification schema support SD-JWT VC or JWT formats?▼

No. The registry publishes this schema only in mso_mdoc format, with isMsoMdoc set to true and isSdJwt and isJwt set to false. There is no SD-JWT VC or JWT variant of this template.

Can holders disclose only one age limit from the credential?▼

Yes. Every claim in the schema sets limitDisclosure to true, so a holder can present age_over_18 alone while keeping age_over_65 and the other booleans hidden from the verifier.

Why does the credential definition creation fail with HTTP 400?▼

A common cause is a reserved label value, since the platform reserves some labels and label is free text that does not affect the schema. Choose a different label and retry the create call.

Where is the authoritative source for this age verification schema?▼

The iGrant.io verifiable data registry on GitHub is the source of truth and wins over this Skill if they disagree. Check the registry directory for versions newer than 2026.4.1 before relying on any claim path.