What problem does it solve? Building a passport verification request against an EUDI Wallet requires exact credential types, doctypes, namespaces, and claim paths for each credential format, and getting any of them wrong causes the wallet to reject the query. ## Core Features & Use Cases - Ready-made DCQL claim sets: Eleven passport claims (serial number, personal number, names, birth date, gender, nationality, expiry date, issuing authority, portrait, signature) mapped for dc+sd-jwt, jwt_vc_json, and mso_mdoc formats. - Format-specific meta configuration: Correct vct_values, type_values, and doctype_value settings for the iGrant.io presentation definition API, including the org.iso.18013.5.1.passport doctype. - Use Case: A hotel chain adds passport checks to online check-in by creating a presentation definition with the minimal claim set (name, nationality, serial number, expiry date) and sending it via the iGrant.io verification endpoint. ## Quick Start Ask your agent to build a passport verification request using the igrantio DCQL passport template with the dc+sd-jwt format and only the claims your check-in flow needs.