Browse the WordPress plugin directory for AI writing tools, and you’ll notice a pattern — a WordPress AI plugin API key request on almost every one of them. Install it, and the first screen will prompt you to sign up with an AI provider, copy a long string of characters, and paste it in before anything works.
For a while, that was the only way AI got into WordPress. It isn’t anymore — and it’s worth knowing what that key actually costs you before you paste one in.
Table of Contents
What “bring your own API key” really costs
An API key looks like a one-time setup step. It’s usually more than that.
- A second account. You sign up with an AI provider, separate from WordPress, with its own login and its own dashboard.
- A separate bill. The plugin might be free. The AI behind it isn’t — you’re billed by the provider, and it’s on you to watch the usage.
- Upkeep. Rate limits, expiring keys, a pricing tier that changes. None of it has anything to do with writing posts, but all of it lands on you.
- Lock-in. The plugin picked its provider. Want to switch? You often rebuild your setup from scratch.
Run two or three AI plugins and you’re managing two or three of these, none of which touch your actual content.
What changed in WordPress 7.0
WordPress 7.0 added AI to the platform itself. Instead of each plugin creating its own connection, WordPress maintains one, and plugins use it. You set up the provider once at the WordPress level, and a plugin built on it doesn’t need its own key. (More on what built-in AI means for your blog, or WordPress’s own core development blog for how the connection itself keeps evolving.)
Versoo Content Ops works this way. It has no API-key field, because it doesn’t need one — it uses whatever AI provider your WordPress site already has configured. You manage your content, not a stack of vendor logins.
When a bring-your-own-key plugin still makes sense
Honesty first: built-in AI isn’t always the answer today.
- You’re on WordPress 6.x or earlier. The built-in AI arrived in 7.0. Before that, a plugin’s own key is the only option.
- Your host doesn’t support it yet. Not every host has WordPress 7.0’s AI available. Check Settings → Connectors — if it’s not there, a third-party plugin fills the gap for now.
- You need one specific provider that your WordPress setup doesn’t offer.
If none of those apply, a plugin asking for its own key is asking you to take on cost and upkeep the platform already handles.
How to Tell If You Need a WordPress AI Plugin API Key
You can spot the difference before you commit. During setup, watch for a plugin that sends you off to create an account and paste its own key — that’s a bring-your-own-key tool. One that reads from your existing WordPress AI provider, with no key field of its own, is built on the native connection.
Neither is wrong. But you should know which one you’re signing up for, and what it’ll ask of you every month after. A quick way to check on any plugin you’re evaluating: open its settings screen before you activate it on a live site, and see whether the very first thing it asks for is a key from some other company. If it is, you’re looking at a bring-your-own-key plugin, whatever the marketing copy calls it.
The short version
An API key isn’t only a setup step — it’s a second account, a separate bill, and ongoing upkeep. WordPress 7.0 made that optional by putting AI in the platform. If you’re on 7.0 with a provider configured, you don’t need a plugin that brings its own key. You need one that uses the connection you already have — and hands you drafts that already sound like your site.