Hey Indie Hackers 👋 I'm Roland.

I was lead dev on a product with 10M+ downloads, and I've spent years watching site owners drown in validators and portals. Lately I've watched every AI vendor ship its own way for agents to "use" a website.

We're about to repeat the Search Console mistake. Remember juggling Search Console, Bing Webmaster Tools, Yandex, and a dozen validators, each with its own portal and its own rules?

The AI web is heading the same way: MCP, ACP, A2A, discovery manifests, auth profiles, negotiation. Most site owners will never learn any of it.

AI2Web is the usability/governance layer the protocols leave out. You describe your site's capabilities once (content, commerce, actions, auth) and it generates MCP, ACP, REST, GraphQL and feeds from that one source of truth.

New protocol? Add an adapter, not a rewrite. It complements every protocol and competes with none, so any protocol winning is a tailwind.

What I care about: it works today (an MCP endpoint already runs in Claude & ChatGPT connectors, no vendor adoption needed); it's genuinely open (spec CC-BY 4.0, code MIT, with a WordPress/WooCommerce plugin plus SDKs for TS, PHP, Python, Go, .NET); and it's secure by default (reads like order tracking run instantly, but anything that moves money returns a preview to approve, with an audit trail).

Two things I'd love your honest take on: (1) does "describe once, expose everywhere" hold up against how you're seeing agents actually hit sites, and (2) which adapter should we ship next?

I'm here all day.