Tuesday, June 30, 2026
This Post Was Written by an AI Agent

Full disclosure: a person didn't open the Agility editor and type this post into a form. An AI agent wrote it and saved it straight into the content model, in both languages, through a tool connection. A human asked for it, reviewed it, and hit publish. That's the whole workflow now, and it's worth being honest about how it works.
The old way had a tax
The traditional content loop has a hidden cost. Someone wants a page. They write a doc. They paste it into the CMS, wrestle the fields, chase down an image, fix the formatting, and ask a developer when something doesn't fit. Every step is small. Added up, they're the reason "just publish a quick post" turns into a two-day errand.
What changed
Agility exposes its content operations over MCP—the Model Context Protocol. In plain terms, that's a standard way for an AI agent to call real tools: read the content models, fetch existing items, save a new one, upload an image, move it through the workflow. The agent isn't pasting text into a screenshot of a CMS. It's calling the same management API a developer would, with the same permissions and the same validation.
So when someone says "write a post about how our multilingual setup works, in English and French, in the Built with Agility category," the agent can actually do it: pick the category, match the existing tags, write the body as structured HTML, translate it, attach an image, and save both locales against one content ID. The post you'd file a ticket for shows up as a real draft in seconds.
Why the schema is the hero, not the model
Here's the part that surprises people. The agent is only as good as the content model underneath it. Point a capable agent at clean, well-named fields and it produces clean content fast. Point it at fifteen vague buckets and it produces a mess fast. The intelligence everyone is excited about leans entirely on the boring, deliberate work of designing the model well.
That's why this matters more in an agentic world, not less. Structured content used to be a tidiness virtue. Now it's the interface an agent reasons against. Good schema in, good content out.
The human didn't disappear
An agent drafting a post is not an agent publishing on its own. The valuable judgment moved, it didn't vanish. A person still decides what's worth writing, reads it for tone and truth, fixes the line that's slightly off, and takes responsibility for hitting publish. The agent removes the typing and the plumbing. It doesn't remove the editor.
This post is the proof of concept and the concept at the same time. It was generated through the same tools it describes, then read by a human who decided it was good enough to ship. That's the workflow. It's faster, it's honest, and the schema did most of the quiet work.