Notes from the agentic web.

How Agent Identity & Discovery fits under Google's new Agentic Resource Discovery spec, and why identity is the part search leaves open.

An endpoint proof is only as strong as the independence of the channel that publishes the key from the endpoint that holds it. Why AID anchors the key in DNS, what that buys, and what it does not.

Agent Identity & Discovery v2 makes AID the 0-th hop for agent discovery: a DNS-first endpoint and key anchor with sharper PKA, updated SDKs, and a cleaner migration path.

WorkOS auth.md gives agents a way to register with a service after they reach it. AID gives that flow a DNS-first, optionally key-proven first hop.

AI agent discovery has not settled on one protocol; experiments are revealing a layered stack of DNS bootstrap, trust, registries, manifests, overlays, governance, and commerce.

A proposed §10.9.0 for draft-klrc-aiagent-auth: DNS-based first-hop discovery slots beneath OAuth metadata without conflict.

We submitted draft-nemethi-aid-agent-identity-discovery-00 to the IETF Datatracker on March 16, 2026, documenting the original AID draft and _agent label-governance request.

We like SVCB. We plan to use it. But a third of DNS providers can't publish one yet, and agent adoption isn't waiting for them.

How AID DNS records can serve as a lightweight bootstrap layer for ARDP agent resolution and discovery. An optional, illustrative mapping for deployments where the ARDP authority is a DNS name.

How AID PKA addresses the cross-boundary agent authentication problem — and what questions remain open.

Code Mode makes large APIs practical for agents by compressing tool surface area. AID stays focused on DNS-first discovery, so protocol routing remains simple and interoperable.

Google’s WebMCP makes websites agent-ready inside the browser. AID stays DNS-native so agents can discover endpoints from any domain, with or without a website.

Universal Commerce Protocol (UCP) is now supported in AID, enabling agents to discover and transact with commerce endpoints via DNS.

Why ERC-8004 needs a DNS-first discovery layer to stay fresh and portable

identity for the agentic web

Moving from discovery to trusted discovery

How does an AI agent know what to do when it hits a locked door on the web?

The discovery layer MCP forgot: AID uses a DNS TXT record to map domains to MCP endpoints so hosts can auto-connect.

Use DNS to find an agent’s front door: AID’s TXT record points to an A2A AgentCard so clients can discover and connect cleanly.

Typing a domain should just connect: AID adds a DNS-based address book so apps discover an agent’s URI and protocol automatically.

The MX-like record for agents: AID’s DNS TXT points any domain to its agent (MCP, A2A, or OpenAPI) for zero-friction discovery.