BRIEFING · 2026 SO FAR

Agent readiness in 2026: what changed for business leaders

Nine months of announcements, reduced to what a marketing, ecommerce or digital leader needs to know.

Am I Ready for Agents? editors · 29 September 2026 · Reviewed September 2026

The short of it

Three things changed in 2026. Infrastructure companies began making agent choices for sites by default, the main agent standards moved under shared foundations and settled their core designs, and agent payments got working proposals but no single winner. Each change is dated and linked below.

What happened, in order?

The list below covers announcements we read and could date. It is not complete, and it leaves out developer-only releases.

12 February: Cloudflare launched Markdown for Agents in beta, converting pages to markdown when an agent asks for it.
20 March: ora.ai announced AgentReady, an MIT-licensed open specification for agent readiness, which reached version 1.0.0 on 24 April.
8 April: ora.ai introduced Deep Scan, which it describes as a benchmark rather than a checklist.
11 May: the x402 project added batch settlement for very small, frequent agent payments.
28 July: the Model Context Protocol published its 2026-07-28 specification, which removes the session handshake and makes the protocol stateless.
6 August: Cloudflare opened a developer preview that adds WebMCP tools to sites at the edge, and set out its view of an agent web that is readable, discoverable, callable and payable.
10 August: the llms.txt proposal was revised to version 2.
20 August: ora.ai and Vercel launched is-agentic.com, and Cloudflare introduced optional OAuth scopes so users can grant agents narrower access.
27 August: the A2A protocol joined the Agentic AI Foundation, alongside MCP.
28 August: Cloudflare began validating Web Bot Auth signatures automatically for bot submissions.
15 September: Cloudflare added a setting to refuse AI training while staying in search.
24 September: Cloudflare made MCP server portals generally available.

The news page has a summary and source link for each.

Change 1: your infrastructure is making choices for you

CDNs and hosts now ship settings for AI crawlers, agent verification, markdown and content signals. That is useful, because it puts decisions within reach of a dashboard. It also means defaults matter: a feature switched on for one reason can say yes or no to AI use on your behalf. Ask your web team which agent-related settings are on today, and who switched them on.

Change 2: the standards are settling

A2A joined the Agentic AI Foundation, which it describes as directed by the Linux Foundation and home to MCP as well. MCP's July specification simplified how agents connect. llms.txt reached a second version. For a business, this lowers the risk of backing the wrong standard: the main building blocks now have stable homes, even if details still change.

Change 3: agent payments are real but early

x402 uses the web's 402 Payment Required code so software can pay per request, and added batch settlement in May. Cloudflare's scanner checks for x402 and three other commerce approaches, ACP, UCP and MPP. None is yet universal. For most stores the near-term question is not which approach to adopt, but whether a purchase an agent starts can be finished with the payment methods and fraud rules you already have.

What should you do with this?

Very little that is urgent, and a few things that are cheap. Take the self-check. Write down your position on AI bots. Ask which agent settings are already on at your CDN or host. Then review the position each quarter, because the pace of change in 2026 suggests it will not stand still.

Sources

Related on this site