igrantio-credential-schema-qesac

Defines the QESAC credential schema with claim path pointers for iGrant.io OpenID4VC issuance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Issuing a QESAC credential through the iGrant.io OpenID4VC API requires the exact claim path pointer structure from the verifiable data registry, and guessing the schema fields leads to credential definitions that verifiers reject. ## Core Features & Use Cases - Registry-Backed Schema: Provides the exact QESAC claim path pointer document for the dc+sd-jwt format, including the mandatory credentialId claim, vct value, and validationPath. - API Request Template: Supplies a ready-to-adapt JSON body for the POST /v2/config/digital-wallet/openid/sdjwt/credential-definition endpoint, with notes on labels, versioning, and multi-format entries. - Integrator Interview: Walks through environment, API key, format, issuance mode, revocation, signing, and trust-list decisions before any code is written. - Use Case: An integrator building an EUDI Wallet issuer backend uses this skill to create a QESAC credential definition on the iGrant.io demo environment with the correct claims array copied verbatim from the registry. ## Quick Start Ask your agent to create a QESAC credential definition on the iGrant.io demo environment using the dc+sd-jwt format with the registry claim path pointer.

Frequently Asked Questions about igrantio-credential-schema-qesac

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

FAQPage Schema
How do I create a QESAC credential definition with the iGrant.io API?▼

Send a POST request to /v2/config/digital-wallet/openid/sdjwt/credential-definition with credentialFormat dc+sd-jwt, vct set to QESAC, validationPath $, and the claims array containing the mandatory credentialId path. Always include version_01 and keep the returned id for the issue operation.

What claims does the QESAC credential schema contain?▼

The registry defines one claim, credentialId, which is mandatory and identifies the credential. The schema supports only the dc+sd-jwt format, and you should not add claim paths that the registry does not hold.

Does the QESAC schema support mso_mdoc or jwt_vc_json formats?▼

No, the registry publishes the QESAC schema only in the dc+sd-jwt format. If your use case needs mdoc or W3C VC, you must use a different credential schema from the registry.

What do I need before issuing QESAC credentials with iGrant.io?▼

You need an Organisation Wallet Suite API key from support@igrant.io for the demo or staging environment. For wallet-trusted credentials, your issuer certificate must also be registered in the trust list.

Why does my credential definition request fail or behave unexpectedly?▼

Common causes are a label under 3 characters or matching a reserved label, omitting the version_01 field which falls back to an older specification, or using an API key in the wrong environment since keys work only in their own environment.