Here’s the thing: Non-technical users might be surprised by this: ChatGPT can’t actually see your website the way you do. It hits your page like a tourist who doesn’t speak the language. Sounds dumb but it takes a screenshot. Guesses which button means “checkout.” Clicks, waits, screenshots again. Rename a button and the whole thing breaks, because it was never reading your site, it was reverse-engineering it. That’s a real problem now, not a hypothetical one. Why? Because ChatGPT passed 1 billion weekly active users (WAU) in August 2026, up from 400 million in early 2025. A third of consumers already start searches with an AI tool instead of Google. WebMCP fixes this underlying broken mechanism. A WebMCP-enabled site is designed to explicitly tell the browser what it can do (searchProducts, bookFlight) and what inputs each tool needs. No screenshots, no guessing. Same difference as scraping a bank’s site versus calling its API. This is why we’re excited at @Netlify to team up with @OpenAIDevs on the WebMCP Challenge. Our take on AX is simple: Agents should be first-class citizens on the web, not something sites barely tolerate. We’d love to see more products built or transformed to be agent-native. If you’re curious to explore WebMCP, this challenge is a great head start.