Five vendors made the same move in the last six weeks. Cloudflare turned email into an agent-native primitive. Microsoft opened the Windows 11 taskbar to third-party agents that can act on the desktop. Salesforce launched Headless 360 to expose its platform as infrastructure for outside agents. Mastercard wired up agent-driven card payments through Lobster.cash. And Sundar Pichai told an interviewer that Google Search will become an "agent manager."

The categories: email, operating system, enterprise data, payments, search. Five different layers of the computing stack. No coordination between the players. The same direction.

This is not the openness it looks like. It is defence.

The Five Fronts

Cloudflare's Email Service moved to public beta on April 17, with native sending from Workers, automatic SPF, DKIM, and DMARC setup, sub-15-millisecond delivery from its global network, and a Model Context Protocol server so external agents can discover and use email as a primitive. The pitch was three lines of code to send email. The named incumbents being squeezed were SendGrid, Mailgun, and Postmark.

Microsoft is opening the Windows 11 taskbar to third-party AI agents that can act on the desktop. The agent gets a first-class surface inside the operating system, not a sidebar app or a chat panel. That is a real architectural choice: the OS treats agents as something closer to processes with permissions than to applications with windows.

Salesforce launched Headless 360, which turns the platform into infrastructure for third-party agents. Salesforce already has Agentforce for its own internally-built agents. Headless 360 is the move that says: build your agents anywhere you want, just keep using our data.

Mastercard's integration with Lobster.cash lets AI agents make card purchases. The exact authentication mechanics matter less than the fact that the world's second-largest card network is now publicly building rails for delegated, agent-initiated transactions. Agents can spend money.

Sundar Pichai, in a recent interview: "Search would be an agent manager, in which you're doing a lot of things." And: "a lot of what are just information seeking queries will be agentic search. You will be completing tasks, you have many threads running." Search becomes orchestration. Many agents in parallel, working on tasks for the user, with Google as the conductor.

Five layers, five vendors, one quarter. None of them work together.

What They Are Actually Defending Against

The thing being defended is not market share. It is relevance.

An AI agent paired with a model that can write production-quality code is not just a user of SaaS. It is a builder of SaaS. The same agent that calls SendGrid's API can stand up a Postfix instance behind a Cloudflare tunnel, configure SPF and DKIM, and have working transactional email by lunchtime. The same agent that queries Salesforce can build a CRM in a weekend on Postgres and a few thousand lines of code. The same agent that integrates with a payment provider can wire up Stripe directly without the intermediary.

The economics of build-versus-buy assumed a developer team measured in person-months and a SaaS subscription measured in dollars per seat per month. Both numbers are now wrong. Building is measured in LLM tokens, which is to say a couple of hundred dollars for most of these categories. Buying is still measured in seats.

Why pay for a SaaS subscription when you can have an agent build you a working replacement for the cost of a few steak dinners? That is the question every SaaS executive started asking themselves this year. The answer they all converged on, independently, was the same: be the agent's default infrastructure before the agent learns it can build its own.

The New Moat Is Not the Product

If the product is reproducible in a weekend, the product is no longer the moat. What remains defensible is whatever the agent cannot trivially rebuild.

For Mastercard, that is the acceptance network: every merchant on the planet that already takes their cards. An agent can write payment integration code, but it cannot recreate forty years of merchant relationships. For Salesforce, it is the data: the customer record that already lives in a million CRM instances, plus the integrations into every other enterprise system. An agent can build a CRM, but it cannot retroactively populate it with a decade of your sales history. For Google, it is the queries: the distribution at the point where the user actually expresses intent. For Microsoft, it is the OS surface: the agent that lives in the taskbar is one click away from the user, every time. For Cloudflare, it is the operational floor: sub-15-millisecond delivery globally, with no DevOps team to maintain.

What every incumbent is selling to agents now is not a feature set. It is the part of their business an agent cannot replicate at any price.

What This Means For You

If you build infrastructure for a living, the question is no longer how to serve developers better. It is which parts of your offering survive once an agent starts doing the procurement. If the answer is your API surface and a developer relations team, you are exposed. If the answer is a network you have spent twenty years building, data nobody else can reach, or an operational floor you have set, you have something defensible. Identify it, double down on it, and make sure the agent's first call lands at your door.

If you advise clients on AI integration, the conversation has shifted. The question is no longer "which SaaS should we buy." It is "which agents should we buy, and which should we have an agent build for us." Anything that depends on network effects, proprietary data, or regulated infrastructure stays a buy. Anything that is essentially a CRUD application with a polished UI is moving into build territory, and the cost of building has dropped by two orders of magnitude.

If you run a SaaS business, the move every incumbent above made this quarter is the move you also need to make. Open up to agents on terms that route them through you, before they learn to route around you. Treat agents as a new class of user with their own identity, scoped permissions, and audit requirements. The vendors that figure this out first will become the agent's default for their category. The vendors that wait will discover their category was the one the agents decided to build themselves.

What Comes Next

The next six months will sort the incumbents into three groups. The ones with a real moat beyond the product, who become indispensable to agents and capture the new traffic. The ones with no moat beyond the product, who get bypassed quietly while their churn dashboards stay green for another quarter or two. And the ones who tried to wall the agents out entirely, who get bypassed loudly.

Many major vendors made the same move in the last six weeks. Watch which categories follow in the next six. The ones that do not are telling you something important about their products.