Skip to content
Agent Identity

OIDF · Final approved 10 July 2025

OpenID for Verifiable Presentations 1.0

openid-4-verifiable-presentations-1_0-final

OIDF FinalStableIdentityAdjacent

An agent acting as a verifier (checking a supplier's credential) or presenting an organizational VC as its identity will hit OpenID4VP. Cross-org agent identity CGs often assume this stack.

At a glance

Problem
A verifier needs to request a presentation of credentials from a wallet (W3C VC, SD-JWT VC, mdoc) using OAuth rails, including over the W3C Digital Credentials API.
Identity / authn / authz
Identity presentation. Can be combined with issuance of an access token based on the presentation.

Actors

  • Verifier
  • Wallet / holder
  • User

When this matters for agents

When this matters for agents: an agent acting as a verifier (checking a supplier's credential) or presenting an organizational VC as its identity. Cross-org agent-identity CGs often assume this stack. It is not how MCP HTTP authorizes tool calls.

Flow in plain language

Verifier sends an authorization request with a DCQL query. Wallet returns a vp_token with presentations. Alternative transport: Digital Credentials API instead of HTTPS redirects.

Key tokens and claims

vp_token
Container for one or more presentations.
dcql_query
Digital Credentials Query Language request.

Implementer notes

Product of the OpenID DCP working group. v1.1 was planned without breaking changes (estimated late 2026). Do not implement the older 'OpenID Connect for Verifiable Presentations' drafts; they are superseded.

Relationship to others

Primary sources