The web was built for human eyes. Now the "customer" is increasingly an AI agent that can't read your layout, guesses at your forms, and renders a whole page just to find one price.
Google AP2 (Agent Payments Protocol) - mandate-based, 60+ partners (Mastercard, PayPal, Amex), now handed to the FIDO Alliance.
If you run a store, this should feel familiar. It's the "build a separate app for every assistant" trap. IE vs Netscape. A native app per platform. Do you now integrate ACP and AP2 and MCP and whatever Amazon ships next quarter - and re-do it every time a new agent shows up?
Hi everyone! I'm Roland. For a while now I've been stuck on a problem that won't leave me alone: the web was built for human eyes, but the fastest-growing "visitor" to most sites is now an AI agent that can't actually read them.
Agents scrape HTML, guess at forms, and render a whole page just to find one price or one button. And every assistant wants a different integration. It started to feel like the early mobile web all over again: rebuild everything, once per platform.
So I started AI2Web - an open interoperability layer. You describe your site once, in a single manifest at /ai2w, and it projects to whatever an assistant actually speaks: MCP, ACP, AP2, REST, feeds. No scraping, no per-vendor rebuild.
It's fully open (CC-BY spec, MIT SDKs). So far I've shipped reference SDKs in 6 languages, a WordPress/WooCommerce plugin that makes a store buyable by AI agents (ChatGPT checkout, Google AP2), a Chrome "AI readiness" checker, and a discovery network so agents can find AI-ready sites.
The open interoperability layer for AI-enabled websites. Describe your site's capabilities once, then expose them across MCP, ACP, REST & GraphQL, validated and managed from one place. MIT-licensed. Works with Claude & ChatGPT connectors today.
