October 15, 2026: Agent Name Service scopes are now available for Personal Access Tokens

View as Markdown
October 15, 2026PAT
ANS
Changed

You can now generate a Personal Access Token (PAT) with Agent Name Service (ANS) scopes and use it to call the ANS API. Use it to register and manage agents with a scoped, revocable credential instead of a classic developer key.

What changed

The Permissions field on the Generate Personal Access Token page has a new Agent Name Service category with two scopes:

  • ans.agent-registration:read (Read Agents): read agents, certificates, certificate signing request (CSR) and renewal status, and agent events; resolve ANS names; search registered agents.
  • ans.agent-registration:write (Manage Agents): register, verify, revoke, and renew agents and certificates. It implies ans.agent-registration:read, so a write-only token can call every ANS operation.

Every ANS API reference page now lists the scope each operation accepts. Write operations like POST /v1/agents/register and POST /v1/agents/{agentId}/revoke require ans.agent-registration:write. Read operations, including POST /v1/agents/resolution and GET /v1/agents/events, accept either scope.

Send the token on every request as Authorization: Bearer $GODADDY_PAT.

Who is affected

Developers calling the ANS API who want to use a PAT. Tokens generated before this change don't include ANS access; generate a new token with the ANS scopes.

Existing integrations are unaffected. The classic developer key (sso-key {KEY}:{SECRET}) continues to work on every ANS operation, and scopes don't apply to it. The three registered-agent search operations (search, list, and retrieve) also accept anonymous requests when you omit the Authorization header. Anonymous requests are limited to 60 per minute per client IP, and a PAT raises that to 3000. Scopes for other APIs are unchanged, so you don't need to take any action.

Last updated on

How is this guide?

On this page