Documentation
BYO-AI
Connect your own OpenAI, Anthropic, or Gemini key. No Replify markup, no proxy.
What BYO-AI means
Replify's AI features (KB summarisation, suggested replies, ticket summarisation, automation conditions) all run against API keys you provide. We don't proxy the calls. The traffic goes directly from your WordPress server to your chosen provider, on your account. You pay them. We don't take a cut.
The provider's data and privacy policy applies to that traffic, not ours. Replify never sees the API key after it's saved, and never sees the prompts or completions.
Supported providers
- OpenAI (GPT-4o, GPT-4o-mini, and the rest of the GPT family)
- Anthropic (Claude Opus, Sonnet, Haiku)
- Gemini (Gemini Pro, Flash)
- Grok (xAI)
Connecting a provider
- Go to Replify → Settings → AI in the WordPress admin.
- Pick a provider from the dropdown.
- Paste your API key. Replify validates it with a test request before saving.
- Pick a default model. Different features can override the default model in their own settings.
Cost control
Because the calls are direct, your usage shows up on your provider's dashboard. We recommend setting a hard monthly spend cap on the provider side. Replify shows token usage per AI feature in the activity log (Pro), so you can audit which feature is driving cost.
What runs on AI
- KB AI summaries. Generate a one-paragraph summary at the top of each KB article.
- Suggested chat replies. Replify proposes replies based on conversation context plus the KB.
- Ticket summarisation. Long ticket threads collapse into a one-paragraph summary.
- Automation conditions (Pro). AI-evaluated triggers, e.g. "if the chat is about a refund, route to the billing team".
Switching providers
You can switch providers at any time without losing data. Replify stores AI-generated artifacts (summaries, suggestions) in your own database, so they persist even if you remove the API key entirely.
Spotted something wrong or missing? Tell us. Replify is built in public.