What happened
On November 10, 2026, at KubeCon + CloudNativeCon North America in Salt Lake City, the Linux Foundation announced ANS as a project under its governance. The Foundation describes ANS as an open standard built on existing Domain Name System (DNS) infrastructure. It defines how agents are named and registered, how their identities are published through DNS, and how those identities can be verified. The specification also covers monitoring identity records for unauthorized changes and enabling agents to verify one another.
The Foundation says the formalized specification consists of seven documents. They address domain-anchored naming, registration and versioning, DNS publication, public log auditing, integrity monitoring, and agent-to-agent authentication. A technical steering committee will govern the specification and develop it in the open. The announcement presents this as a common framework for systems intended to work across platforms and services, rather than an identity scheme controlled by one vendor.
The announcement names two examples of early interoperability. The AGNTCY Agent Directory Service supports verification of ANS identities. Separately, ANS Finder implements the Agentic Resource Discovery (ARD) specification and, according to the Foundation, passes its registry conformance tests. The Foundation characterizes these as evidence of early adoption and progress toward combining discovery with verifiable identity; it does not describe them as universal deployment.
Since the project’s intent to launch was announced in June, 11 organizations have contributed to or adopted the standard, the Foundation says: Cisco, Cloudflare, DigiCert, DistributedApps.ai, GoDaddy, HOL, Infoblox, Radix, Salesforce, OWASP and Trustmodel.ai. The announcement links to the specification, open-source code and contribution process at the Agent Name Service GitHub project, and directs readers to ANS information. It does not state a price, access restriction or commercial launch date.
What the archive adds
New Runtime's earlier coverage noted that major identity providers could treat agents as distinct principals, with identifiers separate from human and service accounts (the delegated-agent identity shift). ANS is a new development on that known question: it proposes a DNS-based, cross-platform standard and enters Linux Foundation governance. The earlier note described an expectation about identity providers; this announcement does not establish that those providers have adopted ANS.
Trend signal
This supports, but does not prove, the expectation that agents will receive identities distinct from human and service accounts. The announcement’s named integrations and contributors are an early signal; they are not evidence of broad production use. See the delegated-agent identity shift. This does not yet fit a pattern New Runtime tracks.
Why now
The Linux Foundation says the project has moved from an intent to launch announced in June to a formalized specification governed by a technical steering committee. It also points to recent high-profile security incidents involving AI agents as a reason organizations need to establish which agent they are trusting. The announcement does not detail those incidents or link them to a particular ANS deployment.
Connections to other events
The Foundation’s announcement places ANS alongside AGNTCY’s Agent Directory Service, which supports verification of ANS identities, and ANS Finder’s implementation of the ARD discovery specification. These are complementary pieces in the account the Foundation gives: identity verification and agent discovery. New Runtime's earlier coverage also described the expectation that identity providers will give agents their own identifiers (delegated-agent identity); ANS offers a standard-focused route toward that broader outcome, rather than evidence that identity providers have already made the shift.
Why it matters
For a team building agents that cross organizational or vendor boundaries, knowing which agent is making a request is a prerequisite for deciding whether to trust it. A shared naming and verification scheme could make it easier to distinguish an agent’s identity from its human operator, locate the identity through familiar internet infrastructure, and check whether its published record has changed. That would give teams a potential foundation for access policies, auditing and revocation decisions.
The practical benefit depends on implementation, not the existence of a specification. Teams would need compatible identity publication and verification in their own systems and in the services they interact with. ANS does not, by itself, define what an identified agent is allowed to do or guarantee that its operator is trustworthy. For builders, the announcement is a reason to track interoperability work and test the published specification against concrete identity and discovery needs—not a reason to assume a cross-vendor trust layer is already ready for production.
What happens next
- At least one additional agent directory or discovery implementation will publicly document ANS verification support (6 months, 60%). Watch for: a release note, conformance result or integration announcement naming ANS.
Limits and uncertainty
The announcement does not quantify deployment, the number of agents registered, or how many of the 11 organizations operate ANS in production. It does not report independent security testing, operational performance, or the process and time required to detect and correct an unauthorized DNS record change. Nor does identity verification establish an agent’s permissions, behavior or trustworthiness. The specification and code are public, but the announcement does not demonstrate that independently operated systems can interoperate beyond the examples it names.
Skill to build now
If your team is designing an agent directory or cross-organization workflow, inspect the ANS specification and map its identity, publication and verification steps against one real agent-to-agent interaction. Record which party controls the domain, how your service would verify the record, and how you would respond to a changed or revoked identity. That exercise can expose integration requirements without treating the new standard as a production-ready trust decision.
Reader takeaway
ANS gives agent identity a DNS-based, open-standard home under Linux Foundation governance, with named early integrations and 11 supporting organizations. The important next test is implementation across independently operated systems. A verified name may help establish who an agent represents, but teams still need separate controls for what that agent may access or do.