igrantio-credential-schema-lpid

Provides LPID claim path pointer schemas for creating credential definitions on 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-lpid-l3-igrant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: igrantio-credential-schema-lpid
Source: https://github.com/L3-iGrant/skills/tree/main/credential-schemas/igrantio-credential-schema-lpid
Command: npx skills add https://github.com/L3-iGrant/skills --skill igrantio-credential-schema-lpid-l3-igrant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Issuing Legal Person Identification Data (LPID) credentials requires exact claim path pointers that differ across the dc+sd-jwt, jwt_vc_json, and mso_mdoc formats, and getting a path or namespace wrong breaks issuance or wallet presentation. ## Core Features & Use Cases - Format-specific claim paths: Ships the exact claim path pointer documents for LPID (identifier and legalName) in all three registry-published formats, including the mso_mdoc doctype org.iso.18013.5.1.lpid. - Credential definition guidance: Shows how to build the POST /v2/config/digital-wallet/openid/sdjwt/credential-definition request with vct, type, doctype, validationPath, revocation, and signing options. - Use Case: When building a European Business Wallet (EUBW) integration, use this Skill to create an LPID credential definition on the iGrant.io OWS API and issue organisation identity credentials that wallets accept. ## Quick Start Use the igrantio LPID credential schema skill to create an LPID credential definition in dc+sd-jwt format on the iGrant.io demo environment.

Frequently Asked Questions about igrantio-credential-schema-lpid

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

FAQPage Schema
How do I create an LPID credential definition on the iGrant.io API?▼

Send a POST request to /v2/config/digital-wallet/openid/sdjwt/credential-definition with version version_01 and one credentialDefinitions entry per format. Copy the claims array from the matching schema document and set vct, type, or doctype plus validationPath for the chosen format.

What claims does the LPID credential schema contain?▼

The LPID schema holds two mandatory claims: identifier, the registered organisation identifier such as a company registration number, and legalName, the registered legal name. Both claims must be filled in every issue request across all three formats.

Which credential formats does the LPID schema support?▼

The registry publishes LPID in dc+sd-jwt, jwt_vc_json, and mso_mdoc. The recommended default is dc+sd-jwt unless the rule book requires mdoc, in which case the doctype is org.iso.18013.5.1.lpid.

Why do mso_mdoc claim paths use a different namespace than the metadata?▼

The mdoc metadata namespace is org.iso.18013.5.1.lpid, but claim paths must start with org.iso.18013.5.1. The issuer builds the mdoc from the paths, so send them exactly as the schema document specifies.

Does jwt_vc_json support selective disclosure for LPID claims?▼

No, jwt_vc_json has no selective disclosure, so its schema document omits limitDisclosure. The dc+sd-jwt and mso_mdoc documents set limitDisclosure to true, letting holders disclose each claim independently.