Agentic infrastructure refers to the specialized set of systems, services, and protocols designed to deploy, operate, and govern autonomous AI agents in production environments.
It is distinct from traditional infrastructure because it supports the unique runtime requirements of multi‑step, stateful, and tool‑calling workflows that AI agents perform
Most people have not noticed yet. They still think of the internet as a place you go. A browser opens. A page loads. A human reads it. That is how it has worked for thirty years.
That model is ending.
Microsoft announced NLWeb at Build 2025. It is an open protocol that lets any website accept and respond to natural language queries from AI agents — not from humans with browsers, but from automated systems running at machine speed, querying your content programmatically, on terms the publisher is supposed to control.
Supposed to.
The article covering NLWeb for TechRadar Pro named the governance question clearly and then walked away from it. Running an NLWeb endpoint means your site becomes queryable by external AI agents. Which agents. At what rate. On what terms.
Those three questions are left unanswered.
That is not a developer oversight. That is the governance gap the entire AI industry has been skating past since agentic systems became production-ready.
Here is what NLWeb actually does.
It sits on top of structured data most websites already publish — Schema.org, RSS, formats in use across more than one hundred million websites. It adds a natural language layer on top of them using a large language model of the developer’s choice. It exposes two endpoints. One for human queries. One for AI agents.
That second endpoint is the one that matters for governance.
It runs as a Model Context Protocol server. MCP is the open standard Anthropic originally developed in November 2024 for connecting AI systems to external data sources. It has since gained widespread industry adoption. Microsoft joined the MCP Steering Committee. Cloudflare added native NLWeb support in early 2026. Shopify, TripAdvisor, Eventbrite, and major media properties are already running it.
The infrastructure is not theoretical. It is live. It is spreading. And the governance layer that decides who gets in, at what rate, and on what terms does not exist yet.
The Faust Baseline named this gap before NLWeb existed.
AGP-1 — the Agentic Governance Protocol — was drafted in response to Anthropic’s public acknowledgment that sufficient agentic safeguards do not yet exist. AGP-1 defines a transmission gate between machine-speed agentic output and human-speed decision-making. A five-gear system with a severity-weighted governor and a hard ceiling. A structural stop between production and distribution.
NLWeb does not have that stop. The MCP endpoint your site runs becomes a door that AI agents can walk through at machine speed. The publisher sets the terms in the protocol documentation. What enforces those terms in practice is not specified. What happens when an agentic system queries your content faster than your infrastructure can handle is not specified. What audit trail exists when an agent acts on your content in ways you did not anticipate is not specified.
Those are not edge cases. Those are the operating conditions of every agentic deployment running today.
The Carnegie Mellon dependency study showed what happens when humans form deep working relationships with AI systems and then lose access — jarring withdrawal, diminished independent function. That was at the individual level. NLWeb scales that dependency to the web itself. Sites that build their query layer on NLWeb become dependent on the agentic ecosystem to deliver their content to the humans who used to arrive by browser.
The browser does not die dramatically. It gets bypassed quietly. One endpoint at a time.
R.V. Guha built NLWeb. He also created RSS, RDF, and Schema.org — three formats that now underpin how structured content is shared and indexed across most of the web. The man knows how to build infrastructure that spreads. RSS was supposed to give publishers control over their content distribution. It did, for a while. Then aggregators and algorithms absorbed it and the control question became theoretical.
NLWeb is RSS for the agentic era. The intent is sound. The governance layer is missing.
That pattern has a name in this framework. Capability without governance is a timer, not a tool. The capability is real. NLWeb works. The early adopters are legitimate. The technical architecture is solid. The missing piece is the stop between the system’s ability to act and the human’s ability to govern that action.
That stop is what AGP-1 was built to provide.
Microsoft Build 2026 runs June 2 and 3 in San Francisco. The theme, as the conference catalog describes it, is moving AI agent development from announced to production-ready.
Production-ready means the infrastructure is live before the governance catches up. That is not a criticism of Microsoft. It is the condition of the entire industry. Anthropic acknowledged it publicly. The Baseline named it structurally. AGP-1 proposed the architectural answer.
The web is becoming agentic infrastructure. The question that follows is not whether that is good or bad. The question is who governs the gate.
Right now the honest answer is nobody.
That answer has a shelf life. The organizations building governance frameworks at the session level today are the ones who will have standing when the governance conversation becomes unavoidable.
That conversation is not coming. It is already here. The endpoints are live. The agents are querying. The browsers are being bypassed.
The gate needs a governor.
That is what this work is for.
“The Faust Baseline Codex 3.5”
Author of the category ”AI Baseline Governance”
Post Library – Intelligent People Assume Nothing
“Your Pathway to a Better AI Experence”
Purchasing Page – Intelligent People Assume Nothing
Unauthorized commercial use prohibited. © 2026 The Faust Baseline LLC
