OID4VP: how an agent shows its mandate
OpenID for Verifiable Presentations (OID4VP) covers the opposite direction: a verifier makes a request, the holder answers with a presentation that discloses only the requested claims. It is the presentation path of the EUDI wallet.
The flow
The verifier creates a request object with the required claims and a response address; the holder signs a presentation with key binding and sends it there. The verifier's nonce protects against replay.
At Mandact
The flow runs server-side at /api/v1/oid4vp/request and /response; the SDK builds the agent's response (presentMandateOid4vp) with selective disclosure. In the end the same engine decides as for /v1/verify.
For verifiers
Whoever already introduces OID4VP for IDs checks agent mandates with the same mechanics — a second integration is not needed.
Status
Endpoints implemented (request, response); SDK function presentMandateOid4vp.