Plenty of things have landed in core over the last 14 years with a lot of noise behind them. The PHP AI Client in WordPress 7.0 is worth attention for a duller reason: it is a standard, not a feature. The WordPress AI Team has now opened testing on a batch of WordPress AI Connector Plugins that wire a site up to models like Grok, Mistral, and Ollama.
OpenAI and Anthropic ship as the defaults, but the interesting part sits in the community ecosystem, as anyone following the WordPress 7.0 AI Client development has already worked out. The point of the whole thing is that a plugin or theme can call an AI capability without knowing or caring which provider answers.
WordPress AI connector plugins worth testing
Several connectors already exist. Each one implements the provider-agnostic SDK, so swapping one for another does not touch a line of your own logic:
- Grok, from xAI, brings real-time knowledge and handles structured output and vision input.
- Mistral AI is the European option, and at the moment it is the main way to test image generation through the new client.
- Ollama runs models on your own hardware, which is the one to reach for when privacy is the constraint, since there are no API keys and no cloud round trip involved.
- OpenRouter is a single gateway to more than 400 models behind one API key.
The technical specs are covered in more detail in my write-up on standardizing AI connectors.
Registering your own connector
The tedious part is gone. You do not have to build a settings screen for API keys any more. Extend AbstractApiProvider and WordPress renders the UI for you on the new Connectors screen, which leaves you with the implementation and none of the plumbing.
A standard registration on the init hook looks like this:
<?php
/**
* Registering a custom AI provider for WordPress 7.0
*/
add_action( 'init', 'bbioon_register_custom_ai_connector' );
function bbioon_register_custom_ai_connector() {
if ( ! class_exists( 'WordPress\AiClient\AiClient' ) ) {
return;
}
// Registering the provider to the core registry
\WordPress\AiClient\AiClient::defaultRegistry()->register(
'my-custom-provider',
\MyPlugin\AI\CustomProvider::class
);
}
The testing workflow
You need a site on WordPress 7.0, which the Beta Tester plugin will get you, plus the AI Experiments plugin. That gives you the UI to fire real prompts and watch how these WordPress AI Connector Plugins behave when a request errors out or drags.
Provider switching is the case I would test first. Move from OpenAI to Ollama mid-flow and see whether the post editor stays stable and whether the Transient cache clears. That is the kind of race condition that takes down a client site.
If this WordPress AI work is eating your dev hours, I do it for a living. I have been wrestling with WordPress since the 4.x days.
Why testing now matters
WordPress is heading toward AI providers you can plug in and forget about. Whether the platform stays genuinely open depends on how many of them get tested properly before 7.0 ships, which is why an afternoon spent kicking the tires on these connectors is time well spent. Official documentation lives in the PHP AI Client Repository.
