Do You Need an API Key to Use AI in WordPress?
It depends on the plugin, and the honest answer has two halves. WordPress's own AI plugin does need one. Its FAQ is direct about it: "yes, currently you need to provide your own API key for the configured AI Connector plugin, such as OpenAI, Google AI, or Anthropic". Plenty of other plugins do not, because they run the AI on their own service and sell you an allowance instead. Neither is the right answer for everybody, and the question worth asking is not which is quicker to set up. It is who holds the provider account, who pays for the tokens, and what happens in the month your usage triples. Bring your own key and you pay fractions of a penny per request with no ceiling on the capability and no ceiling on the bill. Use a plugin with the AI included and you pay a fixed price for a fixed allowance and never see a token. At low volume the second is cheaper and simpler. At high volume the first is cheaper, and it is not close.
The short version
- There are three ways to get AI into WordPress: bring your own provider key, install a plugin that includes the AI, or run a model on your own hardware. Almost every plugin you will look at is one of the first two.
- The platform's default is your own key. WordPress ships an experimental AI plugin plus separate connector plugins for OpenAI, Anthropic and Google, and you paste your key into a Connectors screen.
- Cost crosses over, and earlier than most people expect. Below a few hundred generations a month an included allowance usually wins. Above that, paying a provider directly is cheaper by a wide margin.
- No key does not mean no third party. Your content still leaves your site. It means one supplier instead of two, and a fixed bill instead of a metered one.
What an API key is, and why so many plugins ask for one
An API key is a long string that identifies your account with an AI provider such as OpenAI, Anthropic or Google. A plugin that holds your key can send text or images to that provider on your behalf, and the provider bills your account for what it uses. The key is a credential, not a setting: anything holding it can spend your money.
Plugins ask for one because it is by far the simplest thing for a plugin author to build. There is no service to run, no payment to collect, no capacity to plan for and no liability for what the model produces, because the account is yours. It also keeps the plugin free or cheap, which is why so many of the strongest AI plugins on WordPress.org are built this way.
The cost of that simplicity lands on you, in pieces that are easy to miss when you are looking at a feature list. You create an account with a provider, add a payment card, generate a key, decide on a spending limit, and then keep the whole thing working: renewing the card, rotating the key, watching what it is spent on. None of that is difficult. It is just work that the plugin author has moved to your side of the line.
The platform's own answer: Connectors
WordPress.org now publishes its own AI plugin, described as experimental, which brings alt text generation, summarising, translation, excerpts, editorial notes and image generation into the editor. It reports more than 50,000 active installs, and alongside it sit three separate connector plugins, AI Provider for OpenAI, AI Provider for Anthropic and AI Provider for Google, each in the tens of thousands of installs. Figures checked on WordPress.org on 19 September 2026.
Its own documentation states the position plainly. The plugin "does not include provider credentials or provider implementations by itself". You install the connector for whichever provider you want, then "configure it in Settings, Connectors". And on cost: "the plugin itself is free, but you'll need to pay for API usage from your chosen AI provider. Costs vary by provider and usage."
That is worth registering, because it sets the direction of travel for the whole ecosystem. WordPress is building a shared place for keys rather than each plugin holding its own, and it is building tooling around the consequences, including encrypting keys at rest and requiring administrator approval before a plugin or theme may use a connector configured on the site. Those features exist because a site-wide key is a genuine risk surface, not a checkbox.
AI Engine, the most widely installed third-party AI plugin on WordPress.org at 90,000 active installs and 4.9 stars from 865 ratings as of September 2026, takes the same route by a different road: it talks to the providers directly rather than through the Connectors screen, and the key is still yours. Its own FAQ tells you where to go when the bill stops you: the quota error "comes from OpenAI's API, not AI Engine. Set up billing limits in your OpenAI account."
Three ways to run AI on a WordPress site
Set the plugins aside for a moment and the market is only three shapes. Every product is one of them.
| Approach | What you set up | What you pay | Where it breaks |
|---|---|---|---|
| Bring your own key WordPress AI plus a connector, AI Engine, AI Product Tools and most free AI plugins |
A provider account, a payment card, a key pasted into WordPress, and a spending limit you set yourself | Per token, directly to the provider. Usually fractions of a penny per generation, with no monthly floor and no monthly ceiling | The setup is a real barrier for non-technical owners, the bill is unpredictable, and the key sits in your database where anything with admin access can spend it |
| Included in the plugin Jetpack AI, StoreAgent, Alt Text AI, and our five |
Install the plugin. There is no provider account to open and nothing to paste | A fixed price for a fixed allowance, usually monthly, often with a free tier to try it | You hit a ceiling, the per-unit price is many times the raw token cost at volume, and you are tied to whichever model the vendor chose |
| Run it yourself Ollama and similar, pointed at by the plugins that support it |
A machine that can run the model, and the patience to keep it running | Hardware and electricity. WordPress's own FAQ notes there are "local, open source, and free providers (like Ollama) that can be used as well" | It is the only option with no per-request cost and it is also the only one that needs a sysadmin. Quality at a given speed is behind the hosted frontier models |
Most people reading this are choosing between the first two, and the choice is usually made on setup friction when it should be made on volume.
What it actually costs, both ways
This is the part that vendors on our side of the line tend to leave vague, so here is the arithmetic.
Providers publish per-token prices. Anthropic lists Claude Haiku 4.5, a current low-cost model of the kind these plugins use, at $1 per million input tokens and $5 per million output tokens, checked on 19 September 2026. A typical generation in a WordPress plugin, say a product description written from a product's attributes or a short summary of a post, is in the region of a few hundred to a thousand tokens in and a couple of hundred out. That puts the raw provider cost of one generation at somewhere between a tenth and a fifth of a penny.
Run that out and the picture is unambiguous. Five hundred generations a month is roughly a dollar of tokens. Five thousand is roughly ten. Set against that, an included-AI subscription is a multiple, and anyone selling you one, us included, is charging for the service around the tokens rather than the tokens themselves.
And since we are asking you to trust that, here are ours, measured on 26 September 2026. An AltoScribe product description costs us about a tenth of a penny in tokens. Pro is £10.79 a month including UK VAT (£8.99 before VAT, which is what we keep) for 500 descriptions, which is 1.8p each before VAT if you use all of them, or more than fifteen times the token cost. At the top of the range, Agency is 10,000 descriptions for £41.99 a month including VAT (£34.99 before), 0.35p each before VAT, or about three times. AltoGraph, AltoSum and AltoFAQ cost us between a twentieth and about a third of a penny per generation, depending on the job, and Pro for each is £46.80 a year including VAT (£39 before), so a site generating a hundred things a month uses under £4 of tokens in that year. AltoRewrite was released after these were measured, so it is not in them. Those multiples assume you use your whole allowance; use less and you are paying more per generation. The difference pays for the hosting, payment fees, support and the plugins themselves. If those multiples look high at your volume, that is the threshold above working exactly as described, and your own key is the better deal.
What the subscription buys, and it is not nothing, is everything that sits around the request. Somebody else holds the provider relationship and absorbs its price changes. There is no card to keep alive, no key to rotate and no key in your database. The bill is the same every month, which matters more to a small business than the average of the bill. And the allowance is a spending cap that works by default, rather than one you have to remember to set.
The honest summary is a threshold rather than a winner. If you generate a few dozen things a month, an included allowance is cheaper than the time you would spend setting up an account. If you generate thousands, the key wins on cost and it is not close. The awkward middle is a few hundred a month, where it comes down to whether you would rather manage an account or pay a premium not to.
Five things that change when you paste a key into WordPress
None of these is a reason to avoid the approach. They are the things worth knowing before you choose it, and they are the reason WordPress is building Connectors rather than leaving every plugin to its own arrangement.
- Nothing caps your spending unless you cap it. Providers bill for usage. If a bulk job runs long, or a chatbot is busier than you expected, the bill follows. Set a hard limit in the provider's dashboard on the day you create the key, not the month you get a surprise.
- One key can serve many plugins. That is the convenience of a shared Connectors screen and it is also the risk: a key configured for one purpose becomes available to anything else that asks. The WordPress AI plugin ships an approval gate for this, requiring "explicit administrator approval before plugins or themes can use AI connectors configured on this site", which tells you the concern is real.
- The key lives in your database. Anyone with administrator access, and anything that gains it, can read or use it. The WordPress AI plugin encrypts keys at rest as an opt-in experiment, and notes that turning the experiment off or deactivating the plugin "restores plaintext keys". Assume plaintext unless you have checked.
- Rotation is on you. If a key leaks, you revoke it at the provider and replace it everywhere it was used. That is a fifteen-minute job if you know where it is and an afternoon if you do not.
- The provider relationship is yours. Their terms, their model deprecations, their outages and their price changes all reach you directly. That is genuine control, and it is also genuine ownership of the problem.
What "no API key" does not mean
We sell plugins in this category, which makes this the section we are least entitled to skip.
It does not mean your content stays on your site. A hosted plugin sends your text or your images to somebody's service and sends the result back. That is the same journey your content makes with your own key. What changes is who holds the account at the far end, not whether the journey happens. If you are working out what to put in your privacy notice, or whether a processor is involved, the answer is the same either way and the right thing to read is the plugin's external services section, not its marketing.
It does not mean unlimited. The allowance is the product. Ours are 10 a month free on each of AltoGraph, AltoSum, AltoFAQ, AltoScribe and AltoRewrite. Jetpack AI gives "a quota of 20 requests" free before you upgrade. Every vendor in this category draws the line somewhere, and the line is the thing to compare, not the absence of a key.
It does not mean you choose the model. With your own key you pick the provider and the model, and you can change either when something better appears. With an included service you get whatever the vendor runs, and you find out about a change when you notice the output is different. That is a real loss of control, traded for not having to think about it.
It does not mean the output is right. No arrangement of accounts improves accuracy. Whichever route you take, read what the model wrote before it is published, because the failures are quiet ones and they read fluently.
Where our five fit, honestly
We build the included-AI kind, one job per plugin rather than a suite, with the AI running on our service. There is no provider account to create, no key to paste and no separate AI signup.
The maturity gap is the first thing you should weigh, so here it is without decoration: as of September 2026 all four of our plugins then listed reported fewer than 10 active installs on WordPress.org, with no ratings yet. AltoRewrite, the fifth, was released on 20 November 2026. Jetpack AI ships inside Jetpack, which reports more than 3 million active installs. AI Engine has 90,000. Alt Text AI has 20,000. If you want the option with the longest track record in this category, it is not ours, and anyone telling you install counts do not matter is selling something.
| Plugin | The one job | Free allowance | Paid (including UK VAT) |
|---|---|---|---|
| AltoGraph | Alt text for images, plus SEO meta descriptions | 10 items a month | £46.80 a year |
| AltoSum | Post summaries, TL;DR and key takeaways | 10 summaries a month | £46.80 a year |
| AltoFAQ | FAQ sections from a post, with FAQPage schema | 10 FAQs a month | £46.80 a year |
| AltoScribe | WooCommerce product descriptions | 10 descriptions a month | From £10.79 a month |
| AltoRewrite | Rewrites post content in one of four tones | 10 rewrites a month | £46.80 a year |
Two things are true of all five and worth stating because they are the reason to pick this shape at all. Each sends a site ID, a hash of your site URL, rather than an account, so there is nothing to sign up for and nothing for us to lose. And each shows you what it wrote before anything is saved to your site, which is a review step by design rather than a setting you can regret leaving off.
Two things are equally true in the other direction. You are inside an allowance, and if you are generating at catalogue scale you will pay more per item than a key would cost you. And you are on our model choice rather than your own.
See each one working
Each plugin has a short screen recording of it at work on a test site. The voiceovers are AI-generated (ElevenLabs). The videos open on YouTube in a new tab.
AltoGraph demo (2:07)
AltoSum demo (2:14)
AltoFAQ demo (2:29)
AltoScribe demo (2:08)
AltoRewrite demo (2:12)
Each of our five plugins adds one thing to the screen you already use: a column with a Generate button in the media library for AltoGraph, a panel in the post editor for AltoSum, AltoFAQ and AltoRewrite, a button on the product screen for AltoScribe. You review what comes back before it is saved. The free allowance is there to find out whether the output is any good on your own content, which is the only test that settles it.
See the five pluginsChoosing, in four lines
- You generate at volume and will manage an account: bring your own key. The cost difference is too large to argue with. Start with the WordPress AI plugin plus a provider connector, or AI Engine if you want a full framework.
- You generate occasionally and want no setup: pick a plugin that includes the AI, and compare the allowances rather than the absence of a key.
- You want one thing done well rather than a suite: a single-purpose plugin will have a shorter settings screen and a smaller blast radius, whichever side of the line it sits on.
- You have hardware and opinions: run a local model and pay for neither. Only if you will maintain it.
Whatever you choose, do the same first thing: generate ten items on your own content and read them properly. The setup question takes an hour to resolve. Whether the output is worth publishing is the one that decides if any of this was worth it.
Frequently asked questions
Do I need an OpenAI API key to use AI in WordPress?
Not always. You need one for the plugins that are built to use your own provider account, which includes the WordPress AI plugin, AI Engine and many of the free AI plugins on WordPress.org. The WordPress AI plugin says so directly in its own FAQ: yes, currently you need to provide your own API key for the configured AI Connector plugin. You do not need one for plugins that run the AI on their own service and sell you an allowance, such as Jetpack AI, StoreAgent or our five. Both arrangements send your content to a third party, so the difference is who holds the account and how you are billed, not whether an AI service is involved.
Is it cheaper to use my own API key or a plugin subscription?
Your own key, once volume is high, and the gap is wide. Anthropic lists Claude Haiku 4.5 at 1 dollar per million input tokens and 5 dollars per million output tokens as of September 2026, which puts a single typical generation at between a tenth and a fifth of a penny. Thousands of generations a month therefore cost a few pounds in tokens, well under any fixed subscription. Below a few hundred generations a month the arithmetic reverses, because an included allowance costs less than the time it takes to open a provider account and keep it running. The crossover is volume, not preference.
Is it safe to put my API key into WordPress?
It is normal practice, and there are three things to do on the day you set it up. Set a hard spending limit in the provider dashboard, because nothing caps the bill unless you do. Check where the key is stored, since it sits in your site database and is readable by anything with administrator access unless the plugin encrypts it. And treat it as a credential with a lifespan: know where it is used so you can revoke and replace it quickly if it leaks. WordPress is addressing all three at the platform level with encrypted storage and an approval gate before a plugin may use a configured connector, which is a fair indication of how seriously to take them.
Does a no-key plugin keep my content on my own site?
No, and any plugin that implies otherwise is worth a closer read. A hosted plugin sends your text or images to its own service for processing and returns the result, exactly as a plugin using your key sends them to OpenAI or Anthropic. The journey is the same. What changes is that you have one supplier instead of two, no account to create, and a fixed bill. If you need to know precisely what leaves your site, read the plugin's external services section on its WordPress.org listing, which is where that has to be declared.
Related guides
- Best AI Product Description Plugins for WooCommerce (2026): the same key or no-key split, applied to one category, including where rivals beat us.
- How to Write WooCommerce Product Descriptions From Your Product Attributes: what to feed a model once you have decided how to pay for it.
- How to Write Alt Text for WordPress Images: the review step that matters most, whichever route you took.