igrantio-credential-schema-software-statement

Defines the Software Statement credential schema for iGrant.io OpenID4VC credential definitions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Issuing a Software Statement credential through the iGrant.io OpenID4VC API requires an exact claim path pointer schema from the verifiable data registry, and hand-writing it risks mismatched claim paths, wrong vct values, or unsupported formats that verifiers reject. ## Core Features & Use Cases - Registry-Accurate Schema: Provides the exact claim path pointer document for the Software Statement credential in the dc+sd-jwt format, with the single mandatory claim client_uri. - API-Ready Request Body: Shows how to embed the claims array into the POST /v2/config/digital-wallet/openid/sdjwt/credential-definition request, including label, version, vct, and validationPath rules. - Integrator Interview Checklist: 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 creates a Software Statement credential definition so client applications can be attested as registered OAuth clients. ## Quick Start Ask your agent to create a Software Statement credential definition on the iGrant.io demo environment using the dc+sd-jwt claim path pointer schema from this skill.

Frequently Asked Questions about igrantio-credential-schema-software-statement

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

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

Send POST /v2/config/digital-wallet/openid/sdjwt/credential-definition with credentialFormat dc+sd-jwt, vct SoftwareStatement, validationPath $, and the claims array containing the mandatory client_uri path. Always include version set to version_01 and a label of at least 3 characters.

What claims does the Software Statement credential schema contain?▼

The registry defines one claim, client_uri, which is mandatory and holds the URI of the client application the statement covers. The schema supports only the dc+sd-jwt format and defines no namespace or selective disclosure.

Which credential formats does the Software Statement schema support?▼

The registry publishes this schema only in the dc+sd-jwt (SD-JWT VC) format. It does not provide jwt_vc_json or mso_mdoc variants, so the credential definition should use dc+sd-jwt.

Do I need trust list registration to issue Software Statement credentials?▼

Yes, if you sign with an X.509 certificate, the issuer certificate must be registered in the trust list via support@igrant.io. Until registration completes, wallets display issued credentials as unverified.

What happens if the skill and the registry schema disagree?▼

The verifiable data registry is the source of truth and wins over the skill content. Fetch the raw schema from the registry repository before relying on a claim path and report any difference.