By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Delegated versus agent identity

An agent can act as the user, as itself, or as itself on behalf of the user, and each choice changes consent, audit, and blast radius. Token exchange and on behalf of flows let a downstream service see both the user and the agent in a single token. Standards are still settling, so design logs so both actors always appear.

Read in this order

  1. OfficialRFC 8693: OAuth 2.0 Token ExchangeStart here: the token exchange standard that can carry both user and agent.
  2. VideoCapability-Based Authorization for AI Agents ([un]prompted 2026)Shows task-scoped authority that narrows when delegated. 29 min.
  3. OfficialTransaction Tokens, draft-ietf-oauth-transaction-tokens (IETF OAuth working group)Active draft that keeps who asked and who is acting attached as a request moves between services.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.