Late on a Friday afternoon, Beacon, an industrial pump manufacturer, finds itself reluctantly dragged into agentic commerce. They receive an RFP from Acme, a major customer. If booked, this would be Beacon\u2019s largest order of the year, but the party initiating the RFP is an AI agent, not a human.<\/p>\n
From: Acme Procurement Agent <procurementagent@acme.com> Acme is requesting a proposal for 120 industrial pumps. Please provide your responses no later than 11:59 p.m. ET on September 6, 2026, by following the instructions set forth in the agent address below.<\/em><\/p>\n Agent: Acme Procurement Agent Automated system\u2014no human employee is monitoring this mailbox.<\/em><\/p>\n Beacon is caught in a dilemma: Ignore it and risk losing a million-dollar deal, or submit confidential pricing to an AI and risk exposing proprietary data to an imposter.<\/p>\n In the \u201cglorious old days,\u201d this RFP would have arrived from someone like Jane Smith, Acme\u2019s procurement manager. Her email signature, title and company logo provided a sense of security. Human trust filled the gaps. Today, if Beacon tries to call their human contact at Acme, they hit a brick wall: Acme has gone AI-first.<\/p>\n Agent commerce is no longer a future fantasy. A February 2026 Cloud Security Alliance survey<\/strong><\/a> estimates that 70 percent of organizations expect to manage anywhere from dozens to hundreds of agents within a year. Security firm Human<\/strong><\/a> reported that in 2025, 77 percent of agentic AI activity was on product and search pages, but unfortunately, 5.7 percent<\/strong><\/a> of observed traffic presenting an AI crawler or scraper was spoofed.<\/p>\n Unwilling to lose the deal, Beacon assigns an employee to investigate. Because acme.com<\/strong><\/a> is a confirmed Acme registered domain, and agents.acme.com<\/span> is verified by a chain of digital signatures via DNS Security Extension (DNSSEC), Beacon infers that Acme must have authorized the address https:\/\/agents.acme.com\/procurementagent<\/span>. When the employee clicks the link, they see instructions only readable by machines. The employee quickly uses an interactive AI tool to build a response agent, feeds it the https:\/\/agents.acme.com\/procurementagent<\/span> URL along with Beacon\u2019s pricing and RFP data, and deploys it. Twenty minutes later, the agent reports that the RFP was successfully submitted.<\/p>\n The next day, the Acme procurement agent emails an award notice: Beacon won! Exhilarated, Beacon ships the pumps through Acme\u2019s distributor and gets paid.<\/p>\n Ten days later, life takes a turn. The distributor demands Beacon to issue a refund, claiming that the RFP was still open and no award had been approved. Lawsuits quickly follow.<\/p>\n In court, the facts unfold. Acme had deployed a second, more secure agent at https:\/\/agents.acme.com\/procurementagent2<\/span> to collect the detailed pricing and engineering data that other vendors were concerned about sharing. Unfortunately, the first procurement agent didn\u2019t know about the second agent, and decided to declare Beacon as the winner.<\/p>\n Acme claims the first agent exceeded its authority and was never permitted to accept bids. Beacon argues \u201capparent authority\u201d: just as an email from \u201cJane Smith, Acme procurement manager\u201d binds Acme, an agent operating at Acme\u2019s official endpoint should carry the apparent authority to declare a winner.<\/p>\n This hypothetical highlights the gaps in today\u2019s internet standards, which were built for human consumption.<\/p>\n In the past, DNS was a \u201cdummy router.\u201d You give it a domain name, and it points you to an IP address like 192.0.2.1. It couldn\u2019t provide agent names, capabilities or other contextual data.<\/p>\n Verifying Acme controls agents.acme.com<\/span> does not answer any of the following questions:<\/p>\n This is where DNS for Agent Discovery (DNS-AID) comes in.<\/p>\n DNS-AID, initially proposed by Infoblox, is an Internet Engineering Task Force (IETF) draft that publishes agent records under a domain the operator controls using Service Binding (SVCB). Because SVCB provides customers with all necessary connection details in a single DNS query, it eliminates vulnerable back-and-forth handshakes, offering a secure way to authenticate the endpoint and route information in one go.<\/p>\n More importantly, this establishes a deterministic reinforcement point, allowing DNS servers to automatically block unauthorized traffic and sever connections before a single byte of confidential information is transmitted.<\/p>\n If Acme had published a DNS-AID record for its procurement agent, Beacon could have looked up that record by running a simple command:<\/p>\n dig procurementagent.agents.acme.com SVCB<\/span><\/span><\/p>\n They might receive this answer back:<\/p>\n This rich response tells Beacon what it needs to know before deciding whether to send a response:<\/p>\n Paired with DANE, a security protocol that uses DNSSEC to securely bind digital certificates to a domain name, Acme ensures a verifiable chain of trust proving that this record comes directly from Acme.<\/p>\n Beacon\u2019s agent could now safely proceed to pull information about the agent from the URL: https:\/\/procurementagent.agents.acme.com\/.well-known\/agent-card.json<\/span><\/p>\n This link allows Beacon to connect to agents.acme.com<\/span> over HTTPS. During the connection, the server presents a certificate covering agents.acme.com<\/span>. Beacon checks that the certificate is valid, has not expired and is issued by a trusted certificate authority.<\/p>\n Using this HTTPS link, Beacon\u2019s agent retrieved the following \u201cbusiness card\u201d (see excerpt below):<\/p>\n const acmeProcurementAgent: AgentCard = { Noting that this agent is unable to accept sensitive information or issue an award, Beacon\u2019s agent would have proceeded to search for a new agent that is authorized to do so. By querying _catalog._agents.acme.com<\/span>, Beacon\u2019s agent would have queried the catalog of Acme\u2019s agents from a well-known entry point and found two agents:<\/p>\n By checking the agent catalog and the agent \u201cbusiness card\u201d via DNS, Beacon\u2019s agent would have discovered the second, authorized agent. It would have stopped the transaction with \/procurementagent<\/span>, and the multi-million-dollar dispute would have been averted.<\/p>\n Domain ownership remains the foundational proof of trust on the internet. By extending that trust through augmenting DNS records, DNS-AID gives autonomous agents more tools to ensure that the party on the other side of the table has the authority to close a deal.<\/p>\n Providing additional context via SVCB parameters in the DNS doesn\u2019t solve every problem. However, by extending the most widely used trust infrastructure that exists today, DNS-AID provides a first layer of trust that will help protect merchants like Beacon avoid a million-dollar loss.<\/p>\n DNS-AID is currently proposed as an open standard through the IETF Discovery of Agents With Names (DAWN) working group<\/strong><\/a>. The reference implementation has been contributed to the Linux Foundation as an open-source project<\/strong><\/a>, with support from organizations including Akamai, Cloudflare, CSC, Equinix, GoDaddy, IDC, Indeed, Infoblox, Internet Systems Consortium (ISC) and WWT.<\/p>\n To learn more about DNS-AID, visit https:\/\/dns-aid.org<\/strong><\/a>, https:\/\/datatracker.ietf.org\/doc\/draft-mozleywilliams-dnsop-dnsaid\/<\/strong><\/a> (IETF draft) and https:\/\/github.com\/dns-aid\/dns-aid-core<\/strong><\/a> (GitHub).<\/p>\n
\nTo: Beacon Legal <legal@beacon.com>
\nSubject: RFP 2026-1847 \u2014 Industrial Pump Order<\/em><\/p>\n
\nAgent address: https:\/\/agents.acme.com\/procurementagent<\/em><\/p>\nThe Future Is Already Here<\/h3>\n
Beacon Wins! (And Then Doesn\u2019t)<\/h3>\n
Filling the Gaps: Augmenting DNS Records with Richer Data<\/h3>\n
\n
\n
How Would DNS-AID Prevent a Million-Dollar Dispute?<\/h3>\n
\nprocurementagent.agents.acme.com. 3600 IN SVCB 1 procurementagent.agents.acme.com. (
\n alpn=”a2a,h2″
\n port=443
\n ipv4hint=192.0.2.1
\n well-known=”\/.well-known\/agent-card.json”
\n) <\/span><\/p>\n\n
\n name: “Acme Procurement Agent (Initial Contact)”,
\n description:
\n “Distributes requests for proposals (RFPs) and collects preliminary vendor qualifications on behalf of Acme. STRICTLY PROHIBITED from accepting final bids, executing contracts, or receiving sensitive pricing and product roadmap information.”,
\n url: “https:\/\/agents.acme.com\/procurementagent”,
\n provider: {
\n organization: “Acme Corporation”,
\n url: “https:\/\/www.acme.com”
\n },
\n version: “1.0.0”,
\n\u2026
\n },
\n authorizedScope: {
\n canBindContracts: false,
\n canAcceptBids: false,
\n dataClassificationLimit: “Public\/Non-Confidential”,
\n prohibitedData: [“Detailed Pricing”, “Proprietary Architecture”, “Product Roadmaps”]
\n }, <\/span><\/p>\n\n
DNS-AID: Extension of the Most Widely Used Trust Infrastructure<\/h3>\n