igrantio-credential-schema-boarding-pass

Defines claim paths for issuing Boarding Pass 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-boarding-pass-l3-igrant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: igrantio-credential-schema-boarding-pass
Source: https://github.com/L3-iGrant/skills/tree/main/credential-schemas/igrantio-credential-schema-boarding-pass
Command: npx skills add https://github.com/L3-iGrant/skills --skill igrantio-credential-schema-boarding-pass-l3-igrant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Issuing a Boarding Pass verifiable credential requires the exact claim paths, credential type, and namespace expected by EUDI wallets and verifiers. This Skill provides the authoritative claim path pointer schema (registry version 2025.7.1) so you can create a correct credential definition on the iGrant.io OpenID4VC API without guessing field names. ## Core Features & Use Cases - Complete claim schema: Provides all 14 flat travel claims (departure/arrival date, time and port, passenger name, seat number and type, ticket number, ticket QR, vessel description) with mandatory and limitDisclosure flags. - API-ready payload: Shows the exact POST /v2/config/digital-wallet/openid/sdjwt/credential-definition request body with vct, credentialFormat, validationPath, and claims array. - Use Case: A ferry operator wants to issue SD-JWT VC boarding passes to passengers' EUDI wallets. Use this Skill to build the credential definition with the correct VerifiableFerryBoardingPassCredentialSDJWT type and claim paths, then issue credentials that verifiers can match. ## Quick Start Ask your agent to create a Boarding Pass credential definition on the iGrant.io demo environment using the dc+sd-jwt claim path schema from this skill.

Frequently Asked Questions about igrantio-credential-schema-boarding-pass

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

FAQPage Schema
How do I create a Boarding Pass credential definition on iGrant.io?▼

Send a POST request to /v2/config/digital-wallet/openid/sdjwt/credential-definition with credentialFormat set to dc+sd-jwt, vct set to VerifiableFerryBoardingPassCredentialSDJWT, validationPath set to $, and the claims array copied from the schema document.

What claims does the Boarding Pass credential schema contain?▼

The schema holds 14 flat top-level claims: arrivalDate, arrivalPort, arrivalTime, departureDate, departureTime, firstName, identifier, lastName, seatNumber, seatType, ticketLet, ticketNumber, ticketQR, and vesselDescription. All are mandatory and support selective disclosure.

Does the Boarding Pass schema support mdoc or JWT formats?▼

No. The registry publishes this schema only in the dc+sd-jwt (SD-JWT VC) format. The metadata sets isSdJwt to true and both isJwt and isMsoMdoc to false, so there is no JWT or mdoc form of this schema.

Can passengers selectively disclose boarding pass claims?▼

Yes. Every claim in the schema sets limitDisclosure to true, so the holder can reveal individual claims independently. For example, a passenger can show only the ticket number at the gate while keeping their name hidden.

What vct value should I use for the boarding pass credential?▼

Use VerifiableFerryBoardingPassCredentialSDJWT as the vct, since verifiers match on this value. Some ecosystem profiles use the namespace eu.europa.ec.eudi.boardingpass instead, so send whichever value your verifier expects.