Skip to content
Agent Identity

W3C · date: see source

Verifiable Credentials Data Model

VC Data Model 2.0 Recommendation; 2.1 Working Draft

W3CStableIdentityAdjacent

Natural format for 'Acme attests that agent X may operate in production until date Y', presented by the agent to a relying tool.

At a glance

Problem
An issuer needs to make tamper-evident claims about a subject that a verifier can check without phoning the issuer every time (though status/revocation may still require a check).
Identity / authn / authz
Identity (and other) claims. A VC is not an OAuth access token. OpenID4VCI/VP move VCs over OAuth.

Actors

  • Issuer
  • Holder
  • Subject
  • Verifier

When this matters for agents

When this matters for agents: natural format for 'Acme attests that agent X may operate in production until date Y', presented to a relying tool. A VC is not an OAuth access token. OpenID4VCI/VP move VCs over OAuth rails.

Flow in plain language

Issuer signs a credential. Holder stores it, presents a Verifiable Presentation to a verifier, who checks proofs and validity.

Key tokens and claims

credential / presentation
Data model objects; proofs may be embedded or enveloping.

Implementer notes

Prefer VC DM 2.0 for new work. 2.1 is a working draft. Combine with SD-JWT VC when the credential must be a JWT with selective disclosure.

Relationship to others

Primary sources