AI Plugin Credits vs Your Own API Key: Which Wins?
If you are deciding between AI plugin credits vs your own API key, the short answer is this: use your own key. Bundled credits add a margin on top of what AI providers actually charge, and they cap your usage.
Your own key pays OpenAI, Google or Groq at their published rates, with no markup and no monthly ceiling. The difference is not trivial, and this article shows exactly what it costs and what else changes when you make that choice.
This is not a theoretical comparison. It affects how much you pay per workflow run, which models you can access, and where your data actually goes. Those three things matter regardless of whether you are a solo blogger or running a business site with thousands of automations per month.
Krom Automation builds AI actions into its free tier with a bring-your-own-key model from day one. No credits to buy, no markup on tokens, and no paywall between you and the AI actions. Browse the full feature list to see what that includes in practice.
Quick Summary
- Bundled credits are convenient to start but mark up tokens, cap usage, and limit model choice.
- Your own API key pays provider rates directly, no markup, no cap, no middleman.
- Cost difference is real: a plugin selling 1,000 AI credits at $10 may be charging 3x to 10x what the underlying API call costs.
- Data and privacy differ significantly between the two models, and that gap is almost never discussed.
- Your ChatGPT Plus or Claude Pro subscription does not cover API usage. Those are separate billing systems.
- BYOK (bring your own key) is not just for developers. Modern plugins make setup a five-minute task.
What Bundled Credits Actually Are
When a plugin sells you AI credits, it is buying API access from a provider at wholesale rates, then reselling that access to you at a higher price. The plugin vendor becomes a middleman between you and OpenAI, Google Gemini or whichever model powers the feature. That margin covers their infrastructure, support, and profit.
The markup varies, but it is almost never disclosed. A credit pack priced at $10 for 1,000 credits might represent API calls that cost the vendor $1.50 to $3.00 at provider rates. You are paying 3x to 7x the actual cost for the convenience of not setting up a key yourself.
Buying bundled AI credits is like paying a currency exchange booth at the airport. The rate exists, it is just not the real rate.
Credits also expire or cap out. If you hit your monthly allowance mid-workflow, your automations stop until you top up. That is a meaningful operational risk for any site where AI actions are part of a live customer-facing process.
What Your Own API Key Actually Does
When you supply your own API key, the plugin sends requests directly to the AI provider using your credentials. You are billed by the provider at their published per-token rates. There is no middleman, no markup, and no monthly credit ceiling.
As a concrete example: GPT-4o Mini via OpenAI’s API costs roughly $0.15 per million input tokens and $0.60 per million output tokens as of 2026. A typical WordPress automation prompt, generating a product description or moderating a comment, uses somewhere between 200 and 800 tokens.
That puts the cost of a single AI action well under $0.001. Running 10,000 of those in a month costs under $10 at provider rates, before any markup.
Your spend scales with actual usage. Low-traffic months cost almost nothing.
High-volume months cost proportionally more. There are no overages because you are paying per token, not per credit block.
Does Your ChatGPT Plus Subscription Cover This?
No, and this is one of the most common misunderstandings. ChatGPT Plus is a consumer product subscription. It gives you access to the ChatGPT web interface and app at a fixed monthly fee. It does not give you API access.
API access is a completely separate billing system. You create an API key in your OpenAI developer account, add a payment method, and you are billed per token based on your usage. The same separation applies to Anthropic (Claude), Google Gemini, and every other major provider.
- ChatGPT Plus ($20/month): consumer chat interface, no API access included
- OpenAI API: separate account, pay per token, no subscription required
- Claude Pro: consumer interface, no API access included
- Anthropic API: separate account, pay per token
- Google Gemini Advanced: consumer interface, no plugin API access included
- Google AI Studio / Gemini API: separate account, pay per token
If a plugin tells you to “connect your ChatGPT subscription,” read the documentation carefully. It almost certainly means your API key, not your Plus login.
The Models You Can Actually Access
Bundled credit systems often run on a single model, usually whichever is cheapest for the vendor to operate at scale. You get no choice. When a better model releases, you wait for the vendor to update their system, then potentially pay more credits per call.
With your own key, you choose the model per workflow or per action. Krom Automation supports seven models across three providers in the free version.
| Provider | Models Available | Best for |
|---|---|---|
| OpenAI | GPT-4o Mini, GPT-4o | General text generation, content moderation |
| Google Gemini | Gemini 2.0 Flash, Gemini 2.5 Flash Preview, Gemini 2.5 Pro Preview | Long context tasks, document processing |
| Groq | Llama 3.3 70B, Llama 3.1 8B | Speed-sensitive workflows, high-volume tagging |
Choosing the right model for each task is not academic. Groq’s Llama 3.1 8B is dramatically faster and cheaper than GPT-4o for a simple tagging job.
GPT-4o handles nuanced content moderation better than a smaller model. With your own key, you match the model to the task instead of accepting whatever the vendor chose.
Letting a vendor pick your AI model is like letting a restaurant pick your meal. They will pick whatever keeps their costs down.
The Cost Comparison Over Time
The setup cost of BYOK is real but one-time. Creating an API account, adding a payment method, and pasting a key into a plugin settings page takes about 5 minutes. After that, the ongoing economics strongly favour your own key.
| Scenario | Bundled Credits (estimated) | Own API Key (estimated) | Monthly difference |
|---|---|---|---|
| 500 AI actions/month (small blog) | $5 to $15 | $0.50 to $2 | Save $4 to $13/month |
| 5,000 AI actions/month (active store) | $40 to $80 | $3 to $8 | Save $35 to $70/month |
| 50,000 AI actions/month (agency or SaaS) | $300 to $600+ | $20 to $60 | Save $250 to $550/month |
These are estimates using published token costs and typical credit pack pricing from 2026. Your actual figures will vary by model, prompt length and vendor. The direction does not change: at every usage tier, your own key costs less, often by a factor of 5 to 10.
What Happens to Your Data: The Question Nobody Asks
This is the gap in almost every comparison article about AI plugin credits vs your own API key, so we are covering it directly. The data routing is fundamentally different between the two models, and it matters for business sites.
With bundled credits: your prompt, your content, and any data you pass into the AI action travel to the plugin vendor’s server first. The vendor proxies the request to the AI provider.
That means the vendor can see every prompt you send, log it, and is responsible for securing it. You are trusting the plugin vendor’s infrastructure, their logging policy, and their data handling practices, none of which are typically disclosed in plugin marketing pages.
With your own API key: the request goes from your WordPress server directly to the AI provider. The plugin vendor never sees the prompt content.
Your API key credentials are stored in your own database, not on the vendor’s servers. You are only trusting the AI provider’s handling, which is covered by their published API terms and privacy policies.
- What the vendor can see with bundled credits: every prompt, every response, usage patterns, content being processed
- What the vendor can see with your own key: that you made an API call, not what it contained
- Where your key is stored with bundled credits: the vendor holds the API key, not you
- Where your key is stored with BYOK: your own WordPress database, encrypted
For sites handling customer data, personally identifiable information, or proprietary content, the BYOK model is meaningfully more private. The AI provider’s data handling is a known quantity governed by published terms. The vendor’s logging behaviour usually is not.
Is It Safe to Paste Your API Key into a Plugin?
The honest answer is: it depends on the plugin. Entering your API key into any third-party tool creates risk if that tool is poorly secured. A few things to check before you paste a key anywhere.
- Is the plugin well maintained? Check the WordPress.org listing for recent updates, active install count, and support response rate.
- Does the plugin store your key encrypted? Reputable plugins encrypt API keys at rest in the database rather than storing them as plain text.
- Does the plugin use your key server-side only? Your key should never appear in frontend page source or browser requests. If it does, any visitor to your site can steal it.
- Can you set usage limits on the key? OpenAI, Google and Groq all allow you to set monthly spend caps and restrict keys to specific API endpoints. Use those controls.
- Can you rotate or revoke the key instantly? Generate a dedicated key for your WordPress plugin and nothing else. That way you can revoke it without affecting other systems.
Krom Automation stores keys server-side only and never exposes them to the browser. The AI actions reference covers exactly how that works. If you want to understand what the plugin does before connecting anything, the introduction to how Krom Automation works is the right place to start.
When Bundled Credits Are the Right Choice
We should be honest about this. Bundled credits do have a use case.
If you are testing an AI feature for the first time and you do not want to create a separate API account just to try something, credits lower the barrier to getting started. The friction of creating an API account, finding the key management section, setting a spend cap, and pasting the key is real, even if it only takes five minutes.
- Testing AI features before committing to a tool
- Very low-volume use where the markup is trivially small in absolute dollars
- Situations where you want a single invoice from one vendor covering everything
- Platforms where the bundled model is genuinely well-matched to the task
For any site running more than a few hundred AI actions per month, the economics of credits deteriorate fast. At 5,000 actions per month, the markup can cost more than many premium plugin subscriptions. That is the point where switching to your own key saves real money.
How Krom Automation Handles AI Actions
Krom Automation includes three AI actions in the free version: AI Generate Text, AI Content Moderation, and AI Auto-Tag. All three are available without any credit purchase and without unlocking a paid tier.
You connect your own API key from OpenAI, Google Gemini or Groq in the plugin settings. From that point on, every AI action in every workflow uses your key and bills your account directly. Krom Automation never charges per AI call, never adds a markup, and never holds a pool of credits that can run out mid-month.
Those AI actions slot into any workflow on the drag-and-drop canvas alongside the conditional branching and delay scheduling tools. So you can, for example, run a content moderation check on every new comment, branch on the result, and either approve or flag the comment for review, all without writing a line of code.
If you want to understand the practical applications of AI inside WordPress automation more broadly, our article on what AI WordPress automation actually does and does not do covers that territory honestly.
An AI action that costs $0.0008 to run should not cost $0.05 because a vendor decided to sit in the middle.
What You Pay Krom Automation vs What You Pay for AI
This is a question worth answering directly: if you bring your own key, do you still pay for the plugin?
Yes, the plugin itself has a free tier and a Pro tier. The AI actions are included in the free tier at no charge. What you pay the AI provider is completely separate from what you pay (or do not pay) for the plugin.
| What you are paying for | Who you pay | What it covers |
|---|---|---|
| The automation plugin (free tier) | Nobody | 16 triggers, 21 actions, 3 AI actions, visual builder |
| The automation plugin (Pro) | wpRigel, from $119/year for 1 site | 80+ additional triggers, 60+ additional actions, 24 integrations |
| AI API usage | OpenAI / Google / Groq directly | The actual AI calls your workflows make |
The two costs do not interact. A free plugin user with their own OpenAI key pays only for the tokens they use.
A Pro user pays for the plugin licence plus their tokens. Neither pays Krom Automation for AI credits, because there are none to buy.
You can download Krom Automation free from the WordPress.org plugin directory and connect your own API key without spending anything on the plugin itself. See how to install Krom Automation for the full setup walkthrough.
Practical Setup: Getting Your Own API Key in Five Minutes
The friction argument against BYOK is mostly overstated. Here is what the process actually looks like for OpenAI, which is the most common starting point.
- Go to platform.openai.com and create an account (separate from ChatGPT.com)
- Add a payment method and set a monthly spend limit, $5 or $10 is more than enough for most WordPress sites to start
- Navigate to the API keys section and click “Create new secret key”
- Copy the key and paste it into the Krom Automation settings page
- Run a test workflow using the workflow simulator to confirm it is working before enabling live execution
The Google Gemini API and Groq API follow the same pattern with their respective developer consoles. The process is identical in structure. Once the key is in place, you forget it exists and your workflows run at provider rates automatically.
Also from wpRigel
Pollify is our Gutenberg-native poll, survey and quiz plugin. Polls are built as real blocks inside the block editor, so there are no shortcodes to paste and no separate interface to learn. It fits into the writing flow rather than interrupting it.
Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search everything, and run admin actions without clicking through menus. It is the only WordPress command palette with genuine WooCommerce depth, covering orders, products and customers as first-class commands.
FAQ
Is using my own API key actually cheaper than plugin credits?
In almost every case, yes. At typical usage volumes, provider rates are 3x to 10x cheaper than what credit-based plugins charge per call. The gap widens at higher volumes because the markup is per-token, so it compounds.
What if I run out of API credits with my own key?
You set a monthly spend cap in your API provider account, for example $10 or $20. Once you hit that cap the provider stops accepting requests until the next billing cycle.
This is controllable and predictable. With bundled credits you run out of a fixed allowance and must purchase more manually.
Does BYOK mean my WordPress site has to handle the API calls directly?
Yes. Your WordPress server makes the API request to the AI provider.
That requires your server to be able to make outbound HTTP requests, which is standard on any modern hosting environment. The AI actions in the free version use this approach, and the HTTP Request action supports GET, POST, PUT, PATCH and DELETE.
Can I switch models mid-workflow or use different models for different actions?
With your own key, yes. You choose the model at the action level.
A single workflow can use GPT-4o Mini for a fast tagging task and GPT-4o for a detailed content moderation check. Credit systems typically lock you to one model across everything.
What should I do if my API key is compromised?
Revoke it immediately in your provider’s developer dashboard. Generate a new key, paste it into the plugin settings, and check your usage logs for unexpected spend. This is why keeping your plugin API key separate from any other key you use is important: one compromised key does not cascade to other systems.
The Verdict
For any site running AI-powered automation beyond a handful of test calls, your own API key wins on cost, model choice, and data privacy. The setup takes under five minutes.
The savings start immediately and compound with volume. The privacy benefit is structural: your prompts never touch the plugin vendor’s servers.
Bundled credits are a reasonable starting point if you want zero friction for a quick test. They are not a good long-term choice for anything running at meaningful volume, and they are never the right choice if you care about who can see the content your automations are processing.
See Krom Automation pricing, including the free tier that includes all three AI actions with your own key and no credits required.