igrantio-api-holderlisted

# iGrant.io OpenID4VC API - Holder ## When to use Use this skill when your organisation holds credentials in its own wallet. It covers the 31 operations of the **Holder** group: the holder global configuration, credential receipt and lifecycle, the credential offer, issuer metadata, wallet unit status, the presentation flow, and the wallet notifications. Use it when you must: - take an `openid-credential-offer://` URI into the wallet, and finish a flow that needs a transaction code, a deferred credential, or an authorization code; - list, read, accept, or delete the credentials of the wallet; - turn automatic presentation on or off for one credential; - answer an `openid4vp://` request: receive it, filter the matching credentials, and send the selection; - watch credential lifecycle events over the notification stream. For the issuing side, read `igrantio-api-issuer`. For the relying-party side, read `igrantio-api-verifier`. ## Protocol scope - The wallet implements **OpenID4VCI 1.0** for issuance and **OpenID4VP 1.0** with **DCQL** for presentation. Send a presentation with the **V3** operations. - Presentation Exchange is not a supported surface of an iGrant.io verifier. The filter and send operations still hold an `inputDescriptors` shape, and it applies only to a request from an outside verifier that still sends a DIF Presentation Exchange definition. Use the DCQL shape for every iGrant.io request. - **Honest exceptions.** Two holder operations still wor