A law firm got a WordPress site out of an AI builder in ten minutes, then came back two weeks later with a broken contact form and no search traffic. How I treat AI output as scaffolding instead of a finished build.
A client’s admin was three AI plugins deep, each with its own API key and settings page. The AI Experiments plugin v0.1.0 offers a registry and a base class instead, so features get built once against a standard API.
I wired a client’s store straight into one AI provider and regretted it two weeks later. The Abilities API and the WP AI Client give you a way to register tools and send prompts in WordPress without hardcoding a model.
A 60-site multisite network taught me that bring-your-own-API-key doesn’t scale. Managed hosts should register AI providers through the WP AI Client, the same way they already hand you MySQL and an object cache.
A client’s WooCommerce store was slow because five plugins were each calling their own LLM API on every save. That is the problem the Ai_Client in WordPress 7.0 and the new Abilities layer are meant to solve.
A client wanted a sparkle button by Friday. What WordPress 6.9 actually shipped matters more: the Abilities API and the MCP adapter, which give AI agents a defined way to talk to a site.
A wrapper around a few REST endpoints wasn’t enough to keep an AI agent alive through a timeout. Version 0.3.0 of the WordPress MCP Adapter covers what I had to hand-roll: HttpTransport, WP_Error responses, prefixed hooks and one event stream.
A client’s plugin kept bouncing back out of the queue, so here is what changed: 60,187 plugins in the directory, 7,670 submissions this year, and 85.3% of first reviews started by an automated scanner rather than a person.
A synchronous OpenAI call on image upload hung the admin for five seconds. The AI Experiments plugin v0.1.0 points at a different route: registered Abilities, the WP AI Client, and MCP.
Pointing an LLM at an undocumented WooCommerce extension produced hooks that never existed. Extracting the real hook list with PHP first, then prompting, is what separates a usable draft from a liability.