Building AI-Native Websites

Pre-empts the reader's most likely objection before they can raise it. One idea. Genuine "wait, really?" for anyone who assumed headless CMS already solved this.

Headless CMS already solved this, you might think. It didn't. It solved it for developers, not for agents.

Backend For Frontend exists because one generic API can't serve structurally different consumers well. Mobile and web wanted different shapes of the same data, so each got its own tailored backend instead of sharing one endpoint stretched to fit both.

Headless CMS did something similar for humans: instead of shipping rendered HTML, it ships JSON a developer can build any UI from. But that JSON is still shaped around "what does a frontend developer need to render a page," not "what does an agent need to reason over this content and act on it."

An agent doesn't want a list of fields. It wants to know what a section means, what operations are valid on it, and what's allowed under what scope. That's a different contract entirely: typed, schema-constrained, built around capability, not display.

Headless CMS was the BFF for human developers. Agents are the next frontend, and they need their own.