WordPress 7.0 introduced the AI Client, a shared PHP interface for AI services, together with Connectors for managing provider access centrally. A plugin can request an AI task through WordPress instead of implementing a separate integration for every provider.
Why it matters
The provider can change through configuration rather than a plugin rewrite, and every plugin no longer needs a different API-key screen. This improves maintenance and makes the connection boundary easier to understand when several plugins use AI capabilities.
WordPress does not provide models or quota for free. Every provider has pricing, data policies, and usage limits, and prompts may leave the site. Document what is sent, who may trigger the task, and what happens when the provider is unavailable or the quota is exhausted.
Try it quickly
Start with a non-sensitive task such as suggesting an excerpt for a test draft. Connect one provider, then disconnect it and confirm the plugin fails clearly without publishing an incomplete result. Keep API credentials out of themes and source repositories.
Source: the official WordPress 7.0 release.