The attributable identity a workload such as an agent carries across every hop, under which its actions are logged and its access is revoked, typically a short-lived, attested credential such as an SVID 1. It differs from channel authentication, which secures a single hop, such as a client talking to an MCP server.
- Developed in
- ch. 23, Channel authentication is not agent identity
ch. 04, Layer 04: Runtime Controls & Observability - Chapters
- ch. 03, Values & Principles · ch. 04, The Stack · ch. 05, Patterns · ch. 23, AI Agents
- Contrast with
- NHI · SVID
- In the open reference
- Runtime safeguards for frontier AI · Agent runtime control profile
- Source
- 1 numbered reference, listed below
Where it is used
6 chapters of the Body of Knowledge use the term. Each link opens the first section that does.
- 03 · Values & Principles The eight values 2 mentions
- 04 · The Stack Layer 04: Runtime Controls & Observability 3 mentions
- 05 · Patterns Pattern: Agent Identity & Scoped Credentials 1 mention
- 07 · Maturity Model The five levels 1 mention
- 08 · Regulatory Map Other jurisdictions 1 mention
- 23 · AI Agents What makes an agent a governance object 10 mentions
Patterns that use this term
2 pattern pages use the term, most mentions first.
- Agent Identity & Scoped Credentials 4 mentions
- Agent Registry 1 mention
Related terms
Sources
- [1] SPIFFE overview (short-lived cryptographic identity documents called SVIDs, as X.509 certificates or JWTs; the Workload API issues and rotates them; SPIRE implementation). SPIFFE project. 2026. https://spiffe.io/docs/latest/spiffe-about/overview/ (verified: primary)
Definitions of legal terms paraphrase the cited text, which governs. Dated statements are as of .