Wagtail published a post on 8.0’s new API under a thesis stated in the title — a CMS with AI, not an AI CMS. The distinction is a product decision with a real edge: there will be no AI buttons in your admin unless you choose to install Wagtail AI, and the new surface is opt-in in three lines of configuration. What it opens is substantial. The v3 API, built on Django Ninja and Pydantic, exposes more than fifty admin operations across pages, images and documents, authenticated with bearer tokens, documented with an OpenAPI schema, and reachable over MCP. There is a CLI alongside it and markdown support for rich text, with 8.1 following a few weeks behind. The framing that makes it coherent is the deployment choice they hand you: “You can keep using only the admin UI, or go API only. Or case-by-case.”
That is the opposite of how most CMS vendors have shipped AI this year, and it is worth crediting as a governance stance rather than a feature list. Nothing here is a model. It is a contract over the operations an editor already performs, which means the agent story and the scripting story and the headless story are the same story, and none of them requires trusting a vendor’s prompt. The tradeoff is honest and stated: opt-in means most installs will not have it on, so the ecosystem-wide effect arrives slowly, one upgrade at a time.
The catalog’s Wagtail record is a photograph of the previous era, and it is worth reading precisely because of that. It holds exactly one API page — the Wagtail API v2, the read-oriented JSON surface over pages, images, documents and snippets that has served headless deployments for years. Fifty admin operations is a different kind of surface entirely: v2 answers what the site contains, v3 changes it. For a project running under NASA, Google, the NHS, Mozilla and MIT, moving write access from the admin UI into a documented, token-authenticated contract is the larger of the two announcements.
Wagtail scores 19.9, emerging on the Kin Score, with discoverability at 68.5 and access clarity at 50.0 against contract quality and governance at 0.0. Agent Readiness is 2.5, human-only, and the lit column contains exactly one entry: rate_limit_signal. Everything v3 ships is currently dark — spec_presence for the OpenAPI schema, auth_clarity for the bearer tokens, mcp_server for the MCP endpoint, agentic_access for the operations themselves. Four dimensions, all addressed by one release that is already written. The catalog measures what a provider publishes, not what it has built, and 8.0 is the version where those stop being the same number for Wagtail. Worth re-reading this record after 8.1 lands.