Your website was built for one kind of visitor. On August 25, OpenAI told developers to build for a second kind: the announcement, titled "Build Agent Ready Websites with ChatGPT," introduces site tools, a way for any webpage to hand working controls to an AI agent. Agent ready websites stopped being a thought experiment that day. ChatGPT now ships an implementation, Chrome is running an origin trial of the same standard, and a hackathon backed by Cloudflare, Shopify, Vercel, Render, and Netlify already collected submissions.
For B2B SaaS teams watching their AI search visibility, this is the second half of a shift that started with citations. Here's what shipped and what to do about it.
What OpenAI Shipped: Site Tools for Agent Ready Websites
Site tools are ChatGPT's implementation of WebMCP, a proposed web standard. The idea fits in a sentence: a website registers JavaScript functions with names, descriptions, input schemas, and handlers, and a visiting agent can call them instead of guessing its way through your UI.
The part that matters is where those tools run. The agent works on the same live page you're looking at, inside your signed-in session, in the built-in browser of the ChatGPT desktop app. ChatGPT Work and Codex discover whatever the current page offers. You watch the changes happen.
OpenAI's own properties show the shape of it. ChatGPT Learn and the OpenAI Developers site expose tools like search_openai_docs and lookup_page, so an agent searches documentation through a defined interface instead of scraping nav menus. A demo document editor called Margin registers ten tools, three read and seven write, covering actions like finding a section or leaving a comment for the user to review.
For the record, there are real constraints. Site tools need GPT-5.6 Sol or Terra, and the desktop app. Enterprise and Edu workspaces don't get them yet. Tools defined through HTML form attributes aren't picked up, and neither are tools registered inside iframes. Every invocation gets a safety review, and consequential actions such as purchases or deletions still require user confirmation.
The same announcement bundle points at Sites, ChatGPT's hosted website builder now in public beta. Prompt in, deployed site out, agent-readable by default. OpenAI is simultaneously teaching agents to use websites and mass-producing websites agents can use.
The WebMCP Standard Is Bigger Than OpenAI
Look at who edits the WebMCP specification: one Microsoft engineer and two Google engineers, publishing through the W3C Web Machine Learning Community Group. The latest draft landed September 10. Chrome published a developer guide in May and has an origin trial running. That lineup makes WebMCP the closest thing the agent era has to a cross-vendor bet, with OpenAI as one implementer among several.
Chrome's framing explains why browsers care. Today an agent operates your site through what the Chrome team calls actuation: simulated clicks and typed text, every step open to misinterpretation. A declared tool with a JSON schema removes the guesswork. One developer on r/mcp reached for the comparison we'd have picked ourselves: this is JSON-LD all over again. Structured data told crawlers what a page means. WebMCP tells agents what a page can do.
That parallel should feel familiar if you've been publishing content for AI search. The sites that adopted structured data early spent years collecting rich results while competitors caught up. The same window just opened for actions.
AI search traffic grew 835% this year. Is your content ready?
RankControl generates 15+ content types optimized for ChatGPT, Claude, and Perplexity. Published on your domain, matched to your brand.
The Partner List Tells You Where This Is Going
OpenAI ran the announcement alongside a 10-day hackathon, the WebMCP Challenge, with $35,000 in cash prizes plus Codex Micros and ChatGPT Pro subscriptions. Submissions closed September 4. Ten winners get announced September 23.
The prize money is ordinary. The partner list is not: Google Chrome, Cloudflare, Shopify, Vercel, Render, and Netlify. That's the browser most people use, the CDN in front of roughly a fifth of the web, the platform running millions of storefronts, and the three hosts where modern SaaS marketing sites actually deploy. When those six companies co-sponsor a spec-adoption contest, they are recruiting the supply side of an agent economy.
Early movers are already treating tools as a default, and the pattern is spreading fast. Documentation platforms have started serving WebMCP out of the box, with dashboards showing which queries agents run against your docs. Builders on X keep landing on the same framing: start headless, and open the interface only when the human wants to see something, like a seat map before picking a seat. The tool call handles the transaction. The page handles the trust.
The Skeptics Have a Point, For Now
Not everyone is convinced, and the pushback deserves attention because it's specific. The most useful thread on r/mcp is literally titled "WebMCP: I don't get it." The author's complaint: it only works in the desktop app, in Work mode, with the in-app browser already open on the right page. Compared with a classic MCP server, that reads like a list of disadvantages.
WebMCP: I don't get it
What is the point of WebMCP? It only works when: - Using the Desktop App- Work mode- With in-app browser already open at the website in question It seems all disadvantages compared with the classic MCP (besides the fact that you don't need...
Two counterarguments from that same thread hold up. First, auth. A standalone MCP server for a logged-in product needs its own credential path, its own token storage, its own deployment, and its own upkeep. A WebMCP tool inherits the session the user already has, which is exactly why it only works with the page open. The inconvenience and the security model are the same fact.
Second, scale. One commenter put it plainly: there are a few tens of thousands of MCP servers and hundreds of millions of web apps. Most software will never ship a dedicated agent server. A few registered tools on a page it already has? That can ship this quarter.
To be fair, the current reach is narrow, and building tools nobody's agent can call yet is a real cost. That calculus changes the moment Chrome's origin trial graduates. Then every Chromium browser becomes a potential client for the same tools ChatGPT uses today.
Built by the team that got cited in 48 hours.
Content generation, backlink building, AI visibility tracking, and Google rankings. One platform, zero guesswork.
What B2B SaaS Sites Should Do to Get Agent Ready
You don't need to ship WebMCP tools this month. You need a sequence.
- Fix the reading layer first. An agent picks which products to engage with by reading and citing content, long before it calls anyone's tools. If your pages aren't structured for machine parsing, tools won't save you. The agent discoverability guide covers the groundwork: semantic HTML, server rendering, a clean heading hierarchy, and an accessibility tree agents can parse.
- Publish your commercial facts in parseable form. Pricing, plan limits, supported integrations, and support terms. Formats like Google's OKF bundle and plain structured pages both work. An agent that can't read your pricing recommends the competitor whose pricing it can read.
- Pick one workflow worth exposing as tools. When you do build, start where OpenAI's docs point: an operation your app already supports, wired to existing logic and permissions. Docs search is the obvious first candidate for SaaS. Registration is a small JavaScript surface:
document.modelContext.registerToolplus a schema and a handler. Keep inputs narrow, reuse your auth, and keep the human interface intact. - Measure whether agents choose you. Quick sidebar, because this is the step teams skip: none of the above matters if ChatGPT and Perplexity resolve your category through a competitor. Tracking your citations across AI engines tells you whether agents are arriving at all, and whether that changes after you ship.
The reading-layer audit and the parseable-facts pass take a focused workday. Tool design is a sprint once you pick the workflow. The measurement piece is the one that never ends, because the real problem isn't becoming agent ready once. It's knowing when an engine quietly stops sending agents your way. You can run that whole loop by hand every month, or RankControl's agents can run the content and tracking side continuously while your engineers build the tools.
Watch September 23
The hackathon winners will be the first public catalog of what WebMCP is actually good for, and worth ten minutes of your time when they land. Watch the spec cadence too: a draft that updated on September 10 is a draft moving fast. And watch whether Anthropic and Google wire their agents to the same standard, because Claude went the browser-agent route the same week OpenAI shipped site tools, and a standard both sides adopt becomes infrastructure overnight.
The web spent fifteen years learning that readable gets you ranked. The last two years taught it that citable gets you recommended. The next lesson is already scheduled: callable gets you used. Sites that treat all of that as one project will be the ones agents keep coming back to.
See your first AI citation report in under 5 minutes.
No setup calls. No onboarding meetings. Connect your domain and see where AI mentions your brand right now.
