Conclusion
- No-card APIs are good for validating a chatbot prompt and widget UX, not for unattended customer support.
- Provider keys should stay server-side; the browser should call your own endpoint only.
- Benchmark DeepSeek, Qwen, GLM, Groq/OpenRouter, and a routed endpoint on real visitor questions.
- Production WordPress chatbots need rate limits, logs, consent/privacy handling, and human handoff.
What to do next
- List the top visitor questions, lead forms, refund questions, and support escalation cases.
- Create a server-side WordPress REST route, worker, or backend proxy that stores baseURL, apiKey, and model in secrets.
- Test one no-card provider, one low-cost paid route, and one stronger fallback on 20 real site questions.
- Log provider, model, tokens, latency, error, visitor/session id, and final accepted answer.
- Use OpenLLMAPI when you want one compatible endpoint with fallback, budget caps, and UTM signup tracking.
Recommended paths
| Provider | Free / credits | Best for |
|---|---|---|
| OpenRouter/Groq | Free routes vary | Fast no-card chatbot prototypes |
| DeepSeek | Verify current pricing | Low-cost support answers after prototype |
| Qwen DashScope | Signup credits vary | China-friendly bilingual website chat |
| Zhipu GLM | Signup tokens vary | Domestic fallback for Chinese support |
| OpenLLMAPI | Trial varies | WordPress chatbot routing, logs, budgets, and fallback |
Global developer checklist
- Confirm whether signup, billing, and API keys work from your country before writing production code.
- Prefer OpenAI-compatible endpoints when you may need to switch models, regions, or providers later.
- Test free credits with a real smoke prompt and record latency, error shape, streaming behavior, and quota burn.
- Keep at least one fallback route for provider outages, model deprecations, and regional access changes.
Production handoff
Turn a WordPress chatbot test into a safe route
Keep free prototypes simple, then route live visitors through one compatible endpoint with server-side keys, spend logs, fallback, and UTM tracking.
FAQ
Can I put a free AI API key inside a WordPress plugin setting?
Only if the plugin keeps it server-side. Never expose provider keys in front-end JavaScript, page source, or public shortcode output.
Which free API should a small website try first?
Try a legitimate no-card route that works in your region, then compare it with a low-cost paid provider before public launch.
When should the chatbot use fallback or human handoff?
Refunds, legal/policy questions, angry users, low confidence, repeated failures, rate limits, and lead forms from high-value visitors.
How do I prevent spam costs?
Add CAPTCHA or abuse checks, per-IP/session caps, short context windows, FAQ caching, and daily provider budgets.