.agent Community Blog
Insights, updates, and thoughts from the community.
WebMCP and AID: Browser-first tools meet Internet-first discovery
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.
Why AID Now Supports UCP
Universal Commerce Protocol (UCP) is now supported in AID, enabling agents to discover and transact with commerce endpoints via DNS.
Add AID to ERC-8004: keep discovery fast, keep identity portable
Why ERC-8004 needs a DNS-first discovery layer to stay fresh and portable
AgentBrief: a curation agent for the agentic web
A workflow-first newsroom built on taste, signal, and the agentic web
Agent Identity & Discovery
identity for the agentic web
Identity joins discovery - from v1 to v1.1
Moving from discovery to trusted discovery
Web Bot Auth, not for agents
signed interactions, or a product moat wrapped in a standard?
Door or Address book
How does an AI agent know what to do when it hits a locked door on the web?
Missing grep mcp
The discovery layer MCP forgot: AID uses a DNS TXT record to map domains to MCP endpoints so hosts can auto-connect.
Finding door a2a
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.
What Should Happen When You Type a Domain Name?
Typing a domain should just connect: AID adds a DNS-based address book so apps discover an agent’s URI and protocol automatically.
Missing record
The MX-like record for agents: AID’s DNS TXT points any domain to its agent (MCP, A2A, or OpenAPI) for zero-friction discovery.