Why I built Open for Agents
After more than 20 years as a web publisher, I can see agents changing how people use websites. Owners need a practical way to stay in control.
Read Why I built Open for AgentsStories
Practical guidance for agent-ready websites
Understand where agent browsing is heading, how website owners can stay in control, and what we have learned by building and testing Open for Agents on real websites.
Start here
Latest stories and practical guides
Rendering is not understanding
We tested Kitesurf and Chromium across nine agent-ready pages. Both rendered every page. Chromium also found every WebMCP tool the pages were designed to expose.
Read Rendering is not understandingCan one website tool keep the same rules across agent clients?
I tested whether a read-only Open for Agents tool kept the same inputs, limits, and permissions when packaged for Agent Plugins 1.0 and used in Codex.
Read Can one website tool keep the same rules across agent clients?Cloudflare made WebMCP easier. Website owners still choose the tools.
Cloudflare's WebMCP preview can deliver tools in the browser. Website owners still decide which tools to publish and what agents may do with them.
Read Cloudflare made WebMCP easier. Website owners still choose the tools.Use Open for Agents with Microsoft Agent Framework
Connect Microsoft Agent Framework to a WordPress site's owner-reviewed Open for Agents MCP tools, with practical Python and .NET examples.
Read Use Open for Agents with Microsoft Agent FrameworkWhy now: search agents, browser agents, commerce protocols, and site Assistants
How website owners can decide what emerging search, browser, commerce, and site-provided agents may know and do.
Read Why now: search agents, browser agents, commerce protocols, and site AssistantsPrefer a feed? Subscribe to Open for Agents Stories by RSS.