The WordPress AI Client is the built-in layer in WordPress 7.0 that lets plugins talk to AI providers through one shared connection instead of each plugin handling its own keys. For store owners, that means one place to manage AI access, rather than a different settings screen in every plugin.
Before this change, every AI plugin asked for its own API key. Four plugins meant four keys, four usage dashboards and four places to rotate a key if it leaked. That is easy to forget and hard to audit.
This guide explains what the WordPress AI Client does, how Connectors work, how to set them up safely on a WooCommerce store and which risks remain.
Quick answer
The WordPress AI Client lets compatible plugins share AI provider connections managed on the Connectors screen. To use it, update to WordPress 7.0, add one provider connection, set spending limits at the provider and enable it in each plugin. A shared key does not mean shared privacy rules, so check every plugin’s data settings.
What is the WordPress AI Client?
The WordPress AI Client is a core component, added in WordPress 7.0 on 20 May 2026, that gives plugins a standard way to send requests to AI providers. Think of it as a shared telephone line. Plugins pick up the same line, and you control who is connected.
Developers gain a common tool. Site owners gain one place to manage connections. No data leaves your site until you set up a connection.
What are WordPress AI connectors?
WordPress AI connectors are the saved connections to AI providers, managed on a Connectors screen that only administrators can reach. You add a provider once. Compatible plugins can then use it.
| Topic | Before the AI Client | With the AI Client |
|---|---|---|
| API keys | One per plugin | One shared connection |
| Key rotation | Edit every plugin | Update one connector |
| Provider changes | Reconfigure each plugin | Switch the connection |
| Oversight | Scattered across screens | One administrator view |
| Plugin support | Built into each plugin | Plugin must support connectors |
The last row matters. A plugin must be written to use connectors. Not every AI plugin will, so check each one.
Should a WooCommerce store use shared connectors?
Use shared connectors when convenience and central control matter. Keep separate keys when you want separate budgets and blast radius.
Shared connector works well when:
- You run a small team and want one place to manage access.
- You may change providers later.
- Your plugins all support connectors.
Separate keys work better when:
- You want to cap the chatbot and bulk content jobs separately.
- You want to see which feature caused a cost spike.
- A leaked key should only affect one feature.
A good compromise: create separate projects or keys at the provider, and connect each one deliberately. See how to choose an AI provider for WordPress.
How do you set up the WordPress AI Client safely?
Set it up in six steps, and test before you trust it.
- Back up and update. Take a backup, then update to WordPress 7.0 on a staging copy first.
- Create a provider account. Use a dedicated project or key for your store.
- Set limits at the provider. Add a monthly budget and alerts before you connect anything.
- Add the connection. Use the Connectors screen, with an administrator account.
- Enable it per plugin. Choose which plugins may use the connection.
- Test with harmless prompts. Check results, errors and usage before going live.
Our guide to AI costs in WordPress shows which limits to set in each place.
Which Siteryn plugins work with the WordPress AI Client?
Siteryn AI Support Agent can use WordPress AI connectors, so one key can serve several compatible plugins. It also works without any AI provider. In that mode it answers from your FAQ entries, policy pages and product search, and sends nothing to an AI service.
Siteryn AI Product Content and AI Product Recommendations let you connect your own provider. For the latest connector support, check the documentation for each plugin.
Learn more about the plugins:
Which risks remain with shared AI connections?
A shared connection simplifies management, but it does not remove risk. Watch for these:
- Over-broad access. Every connected plugin can use the same budget. Limit who can use it.
- Data still leaves your site. Each plugin decides what it sends. Review each one, as our WooCommerce AI privacy guide explains.
- One point of failure. If the shared key is revoked, every connected feature stops.
- Surprise costs. Shared budgets hide which feature spent the money. Track usage by feature where you can.
- Plugin quality varies. Test each plugin before you rely on it.
AI connector setup checklist
- Staging site updated to WordPress 7.0
- Provider project created for the store
- Monthly budget and alerts set
- Connection added by an administrator
- Each plugin enabled deliberately
- Privacy settings reviewed per plugin
- Usage checked weekly for the first month
Answer shopper questions with your own AI connection
Siteryn AI Support Agent answers from your FAQ, policies and products, hands visitors to your team for live chat and can use WordPress AI connectors, or run without any AI provider.
Frequently Asked Questions
What is the WordPress AI Client?
It is a core feature in WordPress 7.0 that provides a standard way for plugins to connect to AI providers. Administrators manage the connections in one place instead of in every plugin.
What are WordPress AI connectors?
Connectors are saved connections to AI providers, managed on a dedicated screen in WordPress. Compatible plugins use them to send requests, so you do not paste the same key into several plugins.
Do I have to use the WordPress AI Client?
No. Plugins can still use their own provider settings. The AI Client is an option that reduces duplication. Use it when your plugins support it and you want central management.
Does the AI Client send my data to an AI provider automatically?
No. No data leaves your site until you set up a connection. After that, each plugin controls what it sends, so review each plugin’s privacy settings carefully.
Is a shared connection cheaper?
Not by itself. Costs depend on how many requests your plugins make and which model you use. Set budgets at the provider and monitor usage by feature.
Can my store run AI features without any provider?
Some features can. Siteryn AI Support Agent replies from your own FAQ, policies and product search until you connect a provider. A provider makes replies more natural but is optional there.
Final Thoughts
The WordPress AI Client brings order to a messy part of the plugin world. One shared connection is easier to manage, as long as you set limits and review what each plugin sends.
Set a provider budget first, then connect.
