Here's the failure mode nobody puts in the demo. You ask an AI agent to add a section to your homepage. It calls the API, writes the content, and reports back: "Done — I've added the pricing section." You take its word for it. Two days later a visitor emails to say half the page is blank, because a template reference was misspelled and the whole block silently rendered to nothing.
The agent didn't lie. It genuinely wrote the content. It just never looked at the result — because in most AI-and-CMS setups, it can't. It writes into a black box and gets back an "OK." Whether the page actually renders, whether the layout holds, whether the thing a human would see is right — none of that comes back through the API.
That gap is the whole reason we built verification into Neleto instead of leaving it to hope. An agent working on your site gets three ways to check its own work before it tells you it's done.
The problem with "fire and forget"
When a headless CMS hands an agent an API, the contract ends at "content accepted." The rendering happens somewhere else — a separate frontend, a separate build — so the system the agent talks to has no idea what the visitor eventually sees. The agent can be perfectly obedient and still ship a broken page, because the thing that renders and the thing the agent controls are two different systems.
