GoDaddy just published the Agent Name Service (ANS) API) and an accompanying standards site for defining identity and lifecycle management for autonomous agents.

ANS pairs a human-readable name with cryptographically verifiable identity, using PKI/X.509 and DNS-style discovery. It’s designed to work alongside frameworks like A2A, MCP, and other emerging agent protocols.

What’s new:

Public ANS API is now live (registration, discovery, certificates, revocation, etc.) ANS Standards site with the current spec + architecture Open adapter layer for interoperability without framework lock-in

GitHub repo available for builders

Links:

Standards → hhttps://www.agentnameregistry.org/ Repo → https://github.com/godaddy/ans-registry API keys → https://developer.godaddy.com/keys

Given the rise of autonomous agents, this aims to solve identity, trust, and lifecycle governance at internet scale.

Curious what HN thinks: Do we need shared, neutral identity infrastructure for agents — or should each framework solve this independently?

The PR mentions registration, renewal, and revocation. Are these operations fully automated (e.g., ACME-style), and do they include audit hooks or webhooks for external trust monitors?