AI Agent Identity

Summary: The emerging concept of giving AI agents their own verifiable digital identity — separate from, but bound to, the human, company, or institution they act for — so their actions can be scoped, authorized, and audited.

Sources: 2026-09-04-ai-agent-identity-news.md, 2026-09-07-ai-agent-identity-news.md, 2026-09-08-ai-agent-identity-news.md, 2026-10-26-ai-agent-identity-news.md, 2026-10-27-ai-agent-identity-news.md, 2026-10-28-ai-agent-identity-news.md, 2026-10-29-ai-agent-identity-news.md, 2026-10-30-ai-agent-identity-news.md, 2026-11-02-ai-agent-identity-news.md, 2026-11-04-ai-agent-identity-news.md, 2026-11-05-ai-agent-identity-news.md, 2026-11-06-ai-agent-identity-news.md, 2026-11-09-ai-agent-identity-news.md, 2026-11-11-ai-agent-identity-news.md

Last updated: 2026-11-11

As AI agents increasingly act on behalf of people and organizations (browsing, filling forms, preparing documents, initiating payments), several governments and standards bodies are converging on the idea that agents need a first-class identity distinct from shared credentials or a human’s own login.

Core elements described across sources

A unique identifier or credential for the agent itself, rather than the agent silently reusing a human’s password or API key (source: 2026-09-04-ai-agent-identity-news.md).
Binding to a responsible party — the identity is tied back to the person, company, or institution that authorized the agent, so actions remain traceable (source: 2026-09-04-ai-agent-identity-news.md).
Scoped, limited permissions rather than full delegation of a user’s rights — see agent-authorization-and-delegation (source: 2026-09-04-ai-agent-identity-news.md).
Auditability — actions taken by the agent should be logged and attributable (source: 2026-09-04-ai-agent-identity-news.md).

Estonia’s public correction sharpened this concept materially. Giving an agent a first-class identity does not have to mean giving it a human-style legal identity: Estonia will not issue personal identification codes to agents, and instead links an agent to the person it represents, with liability staying human (source: 2026-09-08-ai-agent-identity-news.md, citing ERR News). See estonia-ai-agent-id.

A related distinction from the standards side: discovery, authentication, authorization, and accountability are separate layers, and proposals that appear to disagree sometimes address different ones (source: 2026-09-07-ai-agent-identity-news.md, citing Cloud Security Alliance). See agent-standards-and-interoperability.

Where this is happening

estonia-ai-agent-id — the most concrete national programme; note the 2026-09-08 correction withdrawing the “AI personal identification code” framing.
agent-standards-and-interoperability — the technical layer: OWASP ACS, IETF DAWN, WIMSE, SPIFFE, OAuth delegation.
united-states-ai-agent-policy — NIST guidance pointing to OAuth 2.0 and SPIFFE as existing building blocks.
china-ai-agent-policy — a national standard covering identity management for interconnected agents.
singapore-ai-agent-policy — a sandbox finding that identity/authentication infrastructure isn’t yet ready for agents.
malaysia-ai-agent-policy — framing agents as “non-human identities” in need of legal accountability structures.

Open questions

Partly answered (2026-09-08): on whether proposals have moved beyond the advisory stage — Estonia’s Aruait now has a published scope and named deliverables (Identity 2.0, a trust registry, interoperability standards, a service-to-service pilot), though no deployed system is yet described (source: 2026-09-08-ai-agent-identity-news.md, citing RIA). The status of the other jurisdictions still needs verification.
Still open: how agent identities interoperate across jurisdictions. Estonia lists interoperability standards as a goal, but no source describes cross-border recognition — needs verification.
New (2026-09-08): how a national trust registry relates to workload-identity standards such as SPIFFE is unaddressed in all sources so far.

2026-10-26: corporate agent identifiers

SK Telecom’s first AI Governance Report reportedly gives agents employee ID numbers and named human supervisors, with a developing lifecycle from identification to retirement — an operator-level model of identity tied to human responsibility, not a government code (source: 2026-10-26-ai-agent-identity-news.md, citing Seoul Economic Daily). See south-korea-ai-agent-policy. The IETF draft draft-burls-mtac-01 likewise separates verifiable agent identity from permission to act (see agent-standards-and-interoperability).

2026-10-27: identity vs authentication and authority

Cybernetica’s Arne Ansper distinguishes legal personhood from technical identity and says an agent number alone is not enough without authentication and authority limits (interviewee assessment) (source: 2026-10-27-ai-agent-identity-news.md, citing ERR); see estonia-ai-agent-id. IBM’s Agent Identity going generally available is a vendor-level model pairing an agent inventory (ownership, lifecycle) with delegated, task-scoped tokens (vendor claims) (source: 2026-10-27-ai-agent-identity-news.md, citing IBM); see agent-standards-and-interoperability.

2026-10-28: NIST tenets

NIST proposes that each agent have a distinct, cryptographically verifiable identity linked to the person or organization initiating tasks (source: 2026-10-28-ai-agent-identity-news.md, citing NIST). Consistent with the linked-identity model above. See united-states-ai-agent-policy.

2026-10-29: “Know-your-agent” floated by CFTC

CFTC Chairman Selig floated “know-your-agent” checks and asked whether agent developers should register, in remarks on 28 October. Discussion only, not a requirement (source: 2026-10-29-ai-agent-identity-news.md, citing CFTC). See united-states-ai-agent-policy.

Update 2026-10-30

A disputed WIRED report ties agent permissions and credential handling to contractor accountability in a US defense setting; see united-states-ai-agent-policy (source: 2026-10-30-ai-agent-identity-news.md, citing WIRED). Estonia: no change.

Update 2026-11-04

HKMA’s Project SAGE names agent identity, delegated-authority verification and Know Your Agent as a regulatory work area (china-ai-agent-policy; source: 2026-11-04-ai-agent-identity-news.md, citing HKMA). UK regulators’ DRCF statement stresses deployer accountability (united-kingdom-ai-agent-policy; source: 2026-11-02-ai-agent-identity-news.md). Estonia: no change.

Update 2026-11-09

Between 4 and 9 Nov: nine countries signed the Tallinn “Agentic State” declaration, centred on a named natural person behind public-sector agents (non-binding; 2026-11-06-ai-agent-identity-news.md); the OCC and CAC published consequence-scaled oversight and trust-framework material without agent-ID mandates (2026-11-05-ai-agent-identity-news.md); Singapore and the Zetrix/CAICT pilot explored cross-border agent verification (2026-11-06-ai-agent-identity-news.md); the UK named a National Agentic Security Unit (2026-11-09-ai-agent-identity-news.md). Still no jurisdiction shown to have enacted agent identity codes beyond what is recorded on estonia-ai-agent-id and china-ai-agent-policy.

Update 2026-11-11

Estonia’s cabinet discussed (10 Nov) a draft Public Information Act § 43(10) amendment creating a legal basis for registering person-linked AI agent codes — discussion only, no approved or submitted bill (source: 2026-11-11-ai-agent-identity-news.md, citing Government of Estonia — Cabinet meeting agenda, 10 November 2026, item 4); see estonia-ai-agent-id. The Linux Foundation launched Agent Name Service, an open DNS/certificate-based agent identity and discovery project — issuer claims, not a standard or mandate (source: 2026-11-11-ai-agent-identity-news.md, citing Linux Foundation — Agent Name Service launch, via PR Newswire); see agent-standards-and-interoperability. Still no jurisdiction shown to have enacted agent identity codes.