Skip to content
Agent Identity

OIDF · date: see source

OpenID Connect for Identity Assurance 1.0

openid-connect-4-identity-assurance-1_0

OIDF FinalStableIdentityAdjacent

If policy is 'the agent may file a tax return only for a KYC'd user', OIDC IDA or a VC is how you know the user is KYC'd — not a display name on a GitHub account.

At a glance

Problem
Ordinary OIDC claims are self-asserted or weakly verified. Regulated use cases need claims bundled with evidence about how they were verified.
Identity / authn / authz
Higher-assurance identity attributes. Not authorization of APIs.

Actors

  • OP with IDA
  • Relying party
  • End-user

When this matters for agents

When this matters for agents: only when policy is 'this agent may file a tax return only for a KYC'd user'. Most coding agents do not need Identity Assurance on day one. A display name on a GitHub account is not IDA.

Flow in plain language

RP requests verified_claims. OP returns verified claims plus verification metadata and evidence, distinct from unverified claims.

Key tokens and claims

verified_claims
Container binding claims to verification evidence.

Implementer notes

Relevant when an agent must act only for an identity-proofed user (finance, health). Most coding agents do not need IDA on day one.

Relationship to others

Primary sources

  • OIDC IDA 1.0https://openid.net/specs/openid-connect-4-identity-assurance-1_0.html