Unique Agent Identity
Every agent has a unique, verifiable identity distinct from its developer, its user, and its supervising agents: used for authentication, authorisation, and audit.
This page is the complete instruction page for one pattern called "Unique Agent Identity." It explains the problem this pattern solves, the idea behind the solution, when you should (and should not) use it, and what happens afterward, both the good effects and the costs.
This matters because building AI agents is not just about making them clever. It is also about making them safe and predictable. Following a well-tested pattern like this one helps avoid common mistakes, and shows you exactly which safety rules and regulations it connects to, listed under "Standards Mesh" on this page.
Context
Agents acting "as" a user conflate authority, make audit impossible, and create compliance hazards. The agent is a distinct principal with its own scope.
Problem
Shared or inherited identity destroys accountability.
Forces
- Convenience of impersonation vs audit clarity
- Identity sprawl vs proper segregation
Solution
Issue each agent (and each version) a unique identity in the organisation's IAM. Authentication uses that identity. Authorisation is scoped to the agent, not inherited from the user. Every action is attributed to the agent identity plus the principal on whose behalf it acts (if any).
Where this pattern acts in the two lifecycles
03 Decide. Tool / route / next-action selection. 7 of 61 catalogue patterns act at this stage.
01 Design & Scope. Use-case assessment, autonomy tier, risk bounding. 11 of 61 catalogue patterns act at this stage.
Stages and counts from the catalogue data. The Runtime lens is the loop the agent runs each turn; the AgentOps lens is the lifecycle the team runs the agent through. See the Matrix for every pattern at each stage.
Applicability
- All enterprise agent deployments
- Regulated sectors
- Multi-tenant platforms
Anti-Patterns
- Agents using a shared "service account"
- Agents authenticating as the user
Consequences
- +Clear attribution
- +Scoped blast radius
- −IAM objects to manage
- −Provisioning workflow required
