DNS-Anchored Identity for Autonomous Agents

Ground mark

Every agent that transacts needs an owner. Groundmark anchors that ownership in the Domain Name System — the infrastructure already governing every corner of the internet.

Verification chain

Registered Domain
anthropic.com · ICANN-governed identity anchor
Agent Subdomain
_agentid.agent47.anthropic.com TXT
v=agentid1; pk=ed25519:z7rW8r…; kid=k1
Claim Pointer
_agentclaim.agent47.anthropic.com TXT
claim=operator-verified; idsp=verify.groundmark.org
Attestation · Level 1
Operator verified · Anthropic, Inc.
method: domain + org verification · exp: 2027-01

Agents are transacting.
Anonymously.

Protocols like x402 have solved the payment mechanics for autonomous agents — an agent can hit an endpoint, receive an HTTP 402, pay in stablecoins, and get access. But these transactions carry no identity. There is no standard way for an agent to prove who operates it, what it is authorised to do, or whether its operator is accountable. As agent commerce scales, this gap becomes critical.

Who operates this agent?

No accountable principal. No verifiable link between an autonomous agent and the organisation that deployed it.

Is it authorised for this act?

No delegation record. No way for a relying party to know whether the agent is permitted to perform the action it is requesting.

What claims can it make?

No contextual attestation. Age-gating, licensing, jurisdiction compliance — none of this can be verified without a trust framework.

Can it be revoked?

No revocation signal. If an agent is compromised or decommissioned, there is no standard mechanism to inform the ecosystem in real time.

Authenticate the minimum necessary
for the risk profile of the transaction.

Four levels of trust, from permissionless to regulatory-grade. Most agent transactions need nothing at all. A smaller set require verification proportional to what is at stake.

0
Permissionless
No attestation required. Domain ownership establishes the accountability chain. Agent pays and proceeds.
Most transactions
1
Operator Accountability
An identifiable operator controls this agent and has accepted accountability. They can be contacted; they can be held to account.
Commerce · SaaS APIs
2
Claim-Specific
A specific verified fact: "over 21 = true." Not the underlying data — only the minimum the transaction requires.
Age gates · Licensing
3
Regulatory-Grade
KYC/AML, biometrics, professional licensing. Meets legal standards. The Identity Service Provider is subject to audit.
Finance · Regulated sectors

Built on infrastructure
that already exists.

Every component of Groundmark either already exists or extends something that does. The contribution is recognising that DNS registration, subdomain delegation, RDAP, DNSSEC, and registrar verification — recombined — solve the agent identity problem that agentic commerce requires.

01

Domain ownership as root of trust

An agent's identity chains to a registered domain, verified through registrar processes and governed by ICANN policy. The domain holder controls which agents exist and can revoke them at will. The semantics of the string are irrelevant — only the verifiable chain of delegation matters.

agent47.anthropic.com
02

DNS as pointer, not database

TXT records on the agent subdomain serve as pointers to attestations held by trusted third parties. DNS tells you what claims exist and where to verify them — it does not try to be the claims database itself. This mirrors DNS's original design: it does not host your content, it locates it.

_agentid · _agentclaim
03

Identity Service Providers as auditors

IDSPs verify specific facts about an operator, disclose the methods they used, and stake their reputation on the attestation. They are auditors, not gatekeepers — and not live observers of every transaction. No single IDSP is authoritative for everything; pluralism is deliberate.

04

Revocation at DNS speed

Per-subdomain TTLs as short as 60 seconds make every DNS lookup an implicit liveness check. A compromised or decommissioned agent is effectively dead within a minute of revocation — no additional revocation infrastructure required.

An open standard,
in active development.

Groundmark is being built as a proper internet standard. A working Internet-Draft defines the DNS record formats, verification flow, HTTP header convention, and trust framework — positioned standards-track from day one, and designed to compose with adjacent work in the agentic commerce space.

Internet-Draft

DNS-Anchored Identity for Autonomous Agents  ·  Noss  ·  April 2026

draft-groundmark-agent-identity-dns-00

Working in this space?
We'd like to hear from you.

Groundmark is being developed openly. If you are working on agentic protocols, identity infrastructure, registrar policy, or DNS standards, we welcome the conversation.

Reach us directly at
[email protected]