Most people who install an AI chatbot are not trying to become AI engineers. They want fewer repetitive questions, a clearer path to contact, and a site that feels helpful after hours. Then the setup screen asks for an API key—and for a lot of site owners, that is where momentum dies.
That reaction is normal. An API key is not just a password field. It usually means creating an account with another company, adding a payment method, reading model names you did not choose, and hoping nothing breaks if billing stops. Some people are fine with that. Many are not—and they should not have to abandon the chatbot over it.
Limb supports both ways to power the chatbot. This article is about giving people who want less setup friction a clear path—without making the key-based path look wrong.
The real friction is not “AI.” It is a second setup project
Connecting ChatGPT, Gemini, or Claude with your own key is a valid, powerful setup. Agencies and technical owners often prefer it. You keep the provider relationship, you see usage on that provider’s dashboard, and you can tune models as you like.
For everyone else, the hard part is rarely “can the chatbot answer?” It is:
- Which provider should I pick?
- Where do I create a key—and is this safe to paste into WordPress?
- Why am I paying somewhere else before I even know if visitors will use the chatbot?
- What happens if the key is wrong, expired, or out of credit?
Those are fair questions. A good product answers them with choice, not pressure.
Two good doors: Limb AI credits or your own key
Think of powering the chatbot like powering a car: some people bring their own fuel card; some want to fill up at the station attached to the shop. Neither group is “doing it wrong.”
Door 1 — Limb AI credits (less setup friction)
You stay inside Limb. You do not create a separate AI provider account just to see the chatbot work. On a live (public) website, Limb gives you 100 free AI credits so you can run real conversations before you pay anything for AI usage. Local / development sites are not eligible for free credits or credit packs—use your own API key there if you need to test offline.
When those free credits run out, you buy from fixed packs inside Limb: 500 credits for $5, 2,000 credits for $20, or 10,000 credits for $100. Checkout happens on wpaichatbot.com and the balance applies back to that site.
This path is for site owners who want the shortest path from install to a working chatbot on a public site, and are okay topping up with Limb packs when they need more usage.
Door 2 — Bring your own key (full control)
You connect OpenAI, Gemini, Claude, OpenRouter, or another supported provider with your own API key. You pay that provider directly for model usage. Limb still runs the chatbot on your WordPress site—training, widgets, WooCommerce tools (Pro), Live Agent (Pro), and the rest of the product stay yours.
This path is for people who already have keys, want maximum control, or prefer provider billing at scale. Step-by-step: How to add ChatGPT or Gemini to WordPress.
Who you pay (the honest part)
Keep this simple:
- Limb AI credits — on a live public site you start with 100 free credits; after that you buy packs of 500 credits for $5, 2,000 credits for $20, or 10,000 credits for $100 from Limb (plus your Limb plan if you use Pro features).
- Your own key — you pay the AI provider for usage; Limb does not sell you those tokens.
Credits are convenience: one setup, free starter on a public site, fixed packs when you need more, no second AI dashboard required. Your own key is control: you own the provider relationship. You can treat them as different comfort levels—not as a “real” vs “fake” chatbot.
For planning numbers on either path, see How much does a WordPress AI chatbot cost?
What low friction does not remove
Skipping the API-key wall gets you to a working chat faster. It does not replace the work that makes answers trustworthy:
- Train the chatbot on your pages, FAQs, and policies
- Test real visitor questions in Playground
- Decide when a human should take over
Setup path is about how you power the chatbot. Quality is about what you teach it. Guide: How to train an AI chatbot on your WordPress website. Broader start: AI chatbot for WordPress practical guide.
How to choose in one minute
- Choose Limb AI credits if you want the chatbot live quickly and prefer paying for AI usage inside Limb.
- Choose your own key if you already use a provider, need tight control, or want provider billing at higher volume.
- Unsure? Start with credits to validate that visitors actually chat—then move to your own key later if that fits better.
Related guides
Continue with these guides:
- AI chatbot for WordPress: the right way to start
- How to add ChatGPT or Gemini to WordPress
- WordPress AI chatbot cost
- Chatbase alternative: BYOK vs message credits
- Train your WordPress AI chatbot
FAQ
Are you saying API keys are a bad idea?
No. Keys are a strong option when you want provider control. Limb keeps supporting that setup. Credits exist so people who do not want that second project can still run a real chatbot.
Is the chatbot different on credits vs my own key?
The product around it—WordPress install, training, widgets, Pro store and Live Agent features—is the same idea. What changes is how AI usage is billed and whether you manage a provider key yourself.
Can I switch later?
Yes in principle: start where setup feels comfortable, then move if your volume or workflow changes. Pick based on how you like to pay and operate—not on fear of missing a “real” mode.
How many free credits do I get?
100, on a live public website. That starter amount is for trying real chats after install—roughly 2 million tokens, or about 100 typical support chats, depending on the model. It does not last forever, and it is not offered on local / development sites.
What is 1 credit?
One credit is roughly 20,000 tokens—about one typical support chat. That is a rough figure. It depends on which catalog model you pick under Limb AI: a small/fast model lasts longer; a larger model uses credits faster. Full pack sizes: AI Settings.
What credit packs can I buy?
After free credits are used, you buy a predefined pack: 500 credits for $5 (about 10 million tokens, or about 500 typical support chats), 2,000 credits for $20 (about 40 million tokens, or about 2,000 typical support chats), or 10,000 credits for $100 (about 200 million tokens, or about 10,000 typical support chats). Or connect your own key if you prefer provider billing.
Does skipping keys mean I can skip training?
No. Low-friction power gets the chatbot online. Accurate answers still need your content, clear policies, and a quick test pass before you rely on it with customers.
Bottom line: on a public site, Limb gives you 100 free AI credits so you can start without an API key; when you need more, buy a 500-credit pack for $5, 2,000 for $20, or 10,000 for $100—or switch to your own key anytime. If you already live in API keys, keep using them. The goal is a working WordPress AI chatbot with less unnecessary friction, not one approved way to pay.