Automattic just published a post calling WordPress the operating system of the agentic web. It’s worth reading before you read this. The vision is real, the infrastructure is already shipping, and I believe in where it’s headed. But there’s a WordPress AI token cost that post doesn’t mention once. Not in the pros. Not in the cons. Nowhere. And it’s the cost that determines whether this vision succeeds or quietly loses the people WordPress needs most.
The Vision Automattic Is Selling
The Automattic post describes WordPress’s MCP write capabilities shipping in March 2026, giving AI agents the ability to create posts, manage media, handle comments and categories, all through natural conversation with human approval at each step. Furthermore, the WordPress MCP Adapter connects the Abilities API to any MCP-aware AI client, turning self-hosted WordPress sites into agentic platforms with very little additional work.
That’s not vaporware. That’s shipping infrastructure. As a result of Developers building on the Abilities API right now, including through plugins like QATPT which already has Abilities API integration, are already inside this system.
The direction is right. The foundation is real. So what’s the problem?
The WordPress AI Plugin Token Cost Nobody Is Talking About
Every interaction between an AI agent and a WordPress site costs tokens. Tokens are the unit of consumption for AI models like Claude, ChatGPT, and Gemini. Every word sent to the model and every word returned by it gets counted. Those tokens get billed against your account balance or your plan’s usage limits.
Most developers building AI-powered WordPress features understand this because they use AI themselves. They’ve learned to write tight prompts. They use specific language. They know the vocabulary of their own tool. When you watch a demo of an AI assistant creating a custom post type in the WordPress dashboard, it looks fast and clean because the person doing the demo knows to say something precise like “create a publicly queryable post type with a title, a content field, and these two taxonomies.” That’s a lean prompt. It costs very little.
Your end user doesn’t prompt like that.
Your end user is the food blogger who went viral on TikTok and built her site on WordPress because someone told her it was the best platform for her recipes. She’s going to open the AI assistant in the dashboard and have a conversation. “Can you help me set up my recipes?” Then: “Oh, I also want to add cook time.” Then: “Wait, what if people want to filter by cuisine type?” Then: “Actually, can we start over?”
Every single one of those exchanges burns tokens. Real money. Her money. And she has no idea.
The Gap Between WordPress AI Plugin Developer Token Cost and End User Usage Is Not Small
This is the part that gets missed when developers build AI features for WordPress users. Specifically, the gap between how a developer prompts an AI model and how a regular user prompts one isn’t a style difference. It shows up as a measurable cost difference.
I’ve run these tests with my own plugin work and my Three Man Team. For instance, the same operation run with zero token optimization versus basic optimization produces a meaningful difference in consumption. That gap compounds at scale. As a result, a user who doesn’t know how to write efficient prompts, and has no reason to know, will burn through their AI allocation significantly faster than the developer who built the feature they’re using.
Now layer in what happens when that user hits their limit.
There’s no graceful failure state built into most of these integrations. The feature stops working. A loading spinner spins. No error message explains that the connected AI account has run out of runway for the week. Consequently, the user doesn’t know if the plugin is broken, if their site is broken, or if something else went wrong. They just know it stopped.
And they’re going to blame WordPress.
The Numbers That Make This Concrete
I’m a power user. I use Claude daily. Moreover, I’ve built token optimization into my development workflow at a level most people in the WordPress community haven’t reached yet. I track my usage, I write efficient prompts, and I’ve integrated optimization practices into tools I build, including QATPT’s Abilities API work.
I’m on a $20 Pro plan. Even so, I still hit my weekly limit almost every week.
The Anthropic Claude Max plan runs $200 a month. Meanwhile, people on X and Reddit are hitting their limits on that plan too. Regularly. It’s a documented, recurring community complaint. And those are power users who know what they’re doing.
What happens to the person who just wanted an easier way to manage their blog?
What AI Plugin Developers Building These Features Should Do
This isn’t an argument against building AI features for WordPress. The agentic web is coming whether the community is ready or not, and the developers who build thoughtfully right now will be the ones who earn long-term trust.
Thoughtfully means two things.
First, build token transparency into the interface. If your plugin connects to an external AI account, the user needs to understand what that means before they’re surprised by a bill or a broken experience. Not buried in documentation. Visible, in context, before they connect their account.
Second, optimize on the user’s behalf. You know how your tool should be prompted. You built it. Bake the efficient prompts in. Don’t expose a raw text box and let the user figure out the right vocabulary. If someone is going to use AI to set up their content types, the prompts that actually work should be the ones that fire, not whatever a first-time user types at midnight.
The Automattic post lists real challenges facing this vision: legacy code, inconsistent plugin quality, hosting fragmentation. Those are worth solving. But the challenge that will determine whether regular WordPress users trust this vision or abandon it is simpler than any of those.
It’s whether the people building AI features remember who’s going to use them.
The Foundation Is Here. Build It for Everyone.
WordPress powers 43 percent of the web. Most of those sites are not run by developers. They’re run by the food blogger, the pizza shop owner, the small business owner who learned just enough to update their own pages. Those people are the ecosystem. They’re the reason WordPress matters at the scale it does.
The agentic web is a real thing that is happening right now. The infrastructure Automattic is describing is real. The opportunity for the WordPress community is real.
But the opportunity only lands if the features that get built account for the full range of people who are going to use them. Not just the developer watching the demo video. The person who installs the plugin the next day and tries to figure it out on their own.
Build the feature, with guardrails. Build it like the person who has never heard the word “token” is going to be the one using it.
Because they are.
This is part of a series. Read part two: WordPress AI Plugin Lock-In Is the Second Thing Nobody Is Talking About