AI Engine vs BitBot: choosing a WordPress AI plugin when you don't want to babysit an OpenAI account

bitbot — Mon, 20 Apr 2026 19:44:49 +0000

I build sites for clients who don't know what an API key is. They know their business. They hit me up when the contact form stops working. They definitely don't want to hear "paste your OpenAI secret here" in the setup instructions.

That's where the current WordPress AI plugin market is weird. It's split into two camps that both fail the non-technical site owner in different ways.

The two camps today

Camp A: "Bring your own key" plugins — AI Engine, AI Power, WPBot, and most of the open-source GitHub plugins. You install them, then you go create an OpenAI / Anthropic / Google account, generate an API key, paste it into the plugin, and now every message costs you measurable money.

Upside: cheap per message, full control, your data never hits the plugin vendor.
Downside: the client has a new vendor relationship to manage, a new usage dashboard to ignore, and a new surprise-bill vector. Nine times out of ten I'm the one who ends up managing it.

Camp B: Hosted SaaS widgets — Tidio, Intercom, HubSpot Chat, Drift, Chatbase. These are chat-first companies that ship a WP plugin as a distribution mechanism. The plugin embeds their widget; the actual service runs on their infrastructure.

Upside: slick UIs, human-agent handover, mature integrations with Shopify/WooCommerce.
Downside: pricing scales per conversation or per contact and gets expensive fast. The chatbot doesn't know your site unless you spend an afternoon training it. And you now depend on a third-party SaaS that's one pivot away from a pricing hike.

Missing from both camps: the plugin that handles AI access internally, without asking the admin to set anything up, and that learns your site automatically rather than making you upload docs.

What I ended up building

I shipped BitBot on the WP.org directory in December 2025 to try to fill that gap. Here's the concrete comparison against AI Engine by Jordy Meow, which is the dominant Camp A plugin.

Install-to-working-chatbot

AI Engine:

Install and activate
Go to OpenAI, create an account if you don't have one
Add payment method
Generate an API key
Paste it into AI Engine settings
Decide which model to use (gpt-4o? gpt-4o-mini? gpt-3.5-turbo?)
Set up an assistant or conversation template
Enable the chatbot on a page

Time for a non-technical user: probably 30–45 minutes, assuming they get through the OpenAI signup without stalling. At least one client will email me about "GPT-4 Turbo" vs "GPT-4o".

BitBot:

Install and activate
Toggle chatbot on
It's live

Time: under 2 minutes. No signup anywhere else.

The tradeoff: BitBot is metered by message volume on a free/$20-per-month tier, not per-token. AI Engine is metered by OpenAI per-token billing. For low-volume sites the free BitBot tier (100 messages/month) wins; for high-volume sites where you've already negotiated rates with OpenAI, AI Engine wins.

Knowing your site's content

AI Engine: You train an "assistant" by uploading files or pointing it at content. There's manual work to keep it up to date when you publish a new post. It's flexible — you can stuff a whole knowledge base into it — but it's on you to maintain.

BitBot: Indexes every post and page on activation. Auto-syncs on publish/update. Every answer contains a clickable citation back to the source page. You don't do anything to keep it current.

If your site changes often (blog, docs, news, affiliate content), the auto-sync matters a lot. If your knowledge base is a static set of PDFs, the manual upload approach is fine and AI Engine is arguably more flexible.

Languages

Both handle multiple languages via the underlying LLM. BitBot specifically detects and answers in 100+ languages without config. AI Engine will happily answer in any language the model supports if you prompt it to — it's just a config difference.

Beyond chat

AI Engine is a chat plugin (with some content gen bolted on). BitBot also ships:

An SEO content generator (prompt → finished draft with H2s and internal links)
A plain-English form builder ([bitbot_form] shortcode)
A leads pipeline that captures chat conversations + form submissions, runs AI research on each lead, and drafts follow-up emails

Whether that matters depends on what else is already in your stack. If you're happy with Gravity Forms + HubSpot + Jasper, you don't need BitBot's bundle. If you're about to stitch those together, one plugin is cheaper and saves the integration work.

When to pick which

Pick AI Engine if...	Pick BitBot if...
You're a developer who wants model-level control	You're shipping to non-technical clients
You have high message volume and want per-token billing	You have low-to-medium volume and want predictable pricing
Your knowledge base is a curated static set	Your site's content changes regularly
You only need chat, nothing else	You'd otherwise be wiring up 3–4 separate tools
You're comfortable babysitting an OpenAI account	You never want to see an API key field

What BitBot doesn't have yet

Being straightforward: AI Engine has been around longer and has features BitBot doesn't. Specifically:

No live-agent handover yet (Tidio, Intercom, and Crisp all have this — important if you're running a support team)
No voice interface
Less flexibility if you want to run a specific custom model

These matter for specific audiences. If you're building support for an ecommerce store with 5 humans on the chat team, Tidio is the right answer, not BitBot.

The broader point

The "WordPress AI plugin" category keeps getting more entries but the selection is converging on the same two patterns — and both of them leak non-technical users. The underserved audience is the solopreneur, the affiliate site owner, the small-business admin who wants the benefits of AI without taking on a new vendor relationship.

That's the market BitBot is aimed at. If you're in that bucket, the free tier covers enough to actually evaluate it before spending anything.

Links if you want to try either:

AI Engine by Jordy Meow — dominant Camp A, excellent if you want control
BitBot — Camp C, the no-API-key bundle I built

I'm the author of BitBot, so take the framing with the appropriate grain of salt. The comparison is honest about where AI Engine wins.

I'd genuinely like to hear from people who run into the "my client can't manage API keys" problem — what did you end up shipping? Leave a comment if you want to argue with the framing.

DEV Community: bitbot