WordPress 7.0 Lets Any Plugin Use AI Through Your API Key. There Is No Spend Limit in Core.

WordCamp Asia 2026 wrapped on Friday in Mumbai with 2,281 attendees and one theme running through every session: AI. WordPress 7.0 was supposed to launch live at the event. It didn't (we covered the delay). But while the tech press fixates on the release date, the bigger story is what ships when 7.0 finally lands. WordPress is becoming an AI platform. A new Connectors API, a built-in AI Client, and an Abilities API will let any plugin talk to OpenAI, Anthropic, or Google through your site's shared API credentials. And right now, core ships no mechanism to cap what a plugin can spend.

How WordPress 7.0's AI Infrastructure Works

WordPress 7.0 introduces three new systems that work together. The Connectors API adds a Settings > Connectors screen to the WordPress admin where you configure your AI provider API keys once. Official provider plugins for Anthropic (Claude), Google, and OpenAI ship alongside core. Community-built connectors for Ollama, OpenRouter, and Mistral already exist. Configure a key, and every plugin on your site can use it.

The AI Client is the developer-facing layer. Plugin authors call wp_ai_client_prompt() and get text generation, image generation, structured JSON responses, or speech synthesis through a clean, provider-agnostic interface. They don't handle your credentials. They don't even need to know which provider you've chosen. The function takes a prompt and returns a result. It supports model preference fallback chains, so a plugin can request Claude first, fall back to GPT if unavailable, and keep working regardless.

The Abilities API (client-side JavaScript landing in 7.0, PHP side already in 6.9) lets plugins register capabilities with schemas and permissions. This is the foundation for browser agents and WebMCP integration: AI services will be able to discover what your WordPress site can do and interact with it programmatically.

For WordPress developers, this is a genuine step change. Before 7.0, every AI plugin reinvented the same settings page, the same key management, the same provider wrappers. That fragmentation is over.

As Felix Arntz, who authored the AI Client proposal on Make WordPress Core, put it: the system "allows arbitrary prompt execution" but "requires a high-privilege capability check, which by default is only granted to administrators." That's a sensible baseline for who can trigger AI calls from the browser. It does not, however, address what happens when server-side plugin code fires prompts without a human in the loop.

The Budget Problem Nobody Is Raising

Once you enter your API key in Settings > Connectors, every active plugin can call wp_ai_client_prompt(). There is no per-plugin budget. No request-rate cap. No monthly spending ceiling anywhere in core.

The wp_ai_client_prevent_prompt filter lets you block prompts by user capability (admin only, for example). It does not limit volume or cost. A plugin that fires an AI prompt on every page load, one that runs batch processing via wp_cron, or one with a loop that doesn't terminate cleanly could generate hundreds of pounds in API charges before you check your provider dashboard.

Greg Ziółkowski, who built the Connectors API, confirmed this directly in the Make WordPress Core proposal: API keys function as a "site setting, so every plugin can access it." That's the correct architecture for reducing fragmentation. It's also the reason you need external safeguards.

This isn't a design flaw. It's an early-stage architecture decision, and the community will build rate-limiting plugins quickly. Providers already have their own spend controls: OpenAI, Anthropic, and Google all let you set dashboard-level budget caps today. But WordPress core ships the accelerator without the brake pedal. For a small business owner who installs a plugin promising "AI-powered" features and doesn't monitor their Anthropic or OpenAI dashboard, the first invoice could be a genuine shock.

API keys stored in the WordPress database through the Connectors screen are also not encrypted in the current implementation (ticket #64789 is tracking this). If WordPress security is already on your radar, that's worth knowing. Store keys in environment variables or PHP constants instead, both of which the Connectors API supports as higher-priority sources.

Five Things to Do Before You Update

1. Set spend limits on your provider dashboards. OpenAI, Anthropic, and Google all let you cap monthly spend. Do this before you enter any API key into WordPress.
2. Audit every plugin that advertises AI features before activating it on a live site. Check whether it uses the new wp_ai_client_prompt() function and how often it fires.
3. Only configure the providers you actually need. Don't connect all three just because the screen lets you.
4. Keep your API keys in environment variables or PHP constants, not the database. The Connectors API supports this priority order, and it's more secure. Your hosting provider or WordPress host can help with this.
5. If you're on a managed support plan, your agency should be handling this. That's what you pay them for. We monitor plugin behaviour, review updates before they go live, and catch exactly this kind of risk before it costs you money.

What WordCamp Asia Told Us

AI dominated all three days in Mumbai. James LePage's opening session set the tone, and later sessions covered AI-driven development, autonomous testing, and plugin automation. Mary Hubbard's fireside chat addressed trust, security, and what responsible AI integration looks like in an open-source project. Matt Mullenweg joined the closing Q&A remotely with written responses touching on contributor growth, product direction, and the health of the open web.

The release squad published the revised schedule on 24 April. WordPress 7.0 is now confirmed for 20 May 2026, with RC3 on 8 May and RC4 on 14 May. The delay was about real-time collaboration's database architecture, not the AI features. The Connectors API, AI Client, and Abilities API are stable and shipping.

WordCamp India was also announced as the fourth flagship WordPress event for 2027, joining Asia, Europe, and US on the calendar.

The message from the conference floor was clear: AI isn't a sideshow for WordPress any more. It's infrastructure. And the security implications are real: the same week, Anthropic revealed that its Claude Mythos model had found thousands of zero-day vulnerabilities across every major operating system and browser. 365i tested the AI Connectors hands-on during beta and wrote up what they actually do in practice. If you want the technical detail before the release lands, that's worth reading.

Frequently Asked Questions