AI customer service API · AI客服 API

Build customer support with GPT, Claude, DeepSeek and Qwen.

One OpenAI-compatible API for support bots that need China + global models, unified billing, logs, routing, WeChat Pay, Alipay, Team and BYOK.

Try demo Get API key Team/BYOK

Website support

Answer pricing, docs, onboarding, and product questions before a human joins.

WeChat / WhatsApp

Use Chinese models for local users and global models for complex English support.

SaaS helpdesk

Route simple FAQs to budget models and escalate complex cases to Claude or GPT.

E-commerce

Handle product questions, order policies, translations, and pre-sales support.

The profitable pattern

1Answer FAQs with low-cost modelsUse GLM, Qwen, or DeepSeek for common support questions.

2Escalate only when usefulUse Claude, GPT, or Gemini for complex issues and long-context docs.

3Capture paying intentRoute billing, invoice, BYOK, and enterprise questions to a sales intake.

TypeScript

import OpenAI from "openai";

const ai = new OpenAI({
  baseURL: "https://api.aipower.me/v1",
  apiKey: process.env.AIPOWER_API_KEY,
});

const reply = await ai.chat.completions.create({
  model: "deepseek/deepseek-chat",
  messages: [
    { role: "system", content: "You are a concise support assistant." },
    { role: "user", content: customerQuestion },
  ],
  max_tokens: 300,
});

Get an API key → your API key auto-fills in all code examples. Copy & run instantly.

Model routing for support

Support job	Model	Best use
Low-cost FAQ	zhipu/glm-4-flash	Simple routing, status, and policy questions.
Chinese support	qwen/qwen-plus	Strong Chinese answers, good cost control.
General support	deepseek/deepseek-chat	Balanced English/Chinese support with low cost.
Premium support	anthropic/claude-sonnet	Complex troubleshooting, account setup, and long replies.
Long context	google/gemini-2.5-flash	Long docs, policy pages, and large knowledge base snippets.

Use exact pricing from the pricing page. Do not sell customer support on "cheapest"; sell it on access, routing, billing, and support coverage.

Self-serve support bot

Best for founders and developers testing a support chatbot inside a website, SaaS dashboard, Discord, Telegram, or WeChat bot.

Create API key

Team / BYOK support layer

Best for teams that need shared budgets, invoices, provider-key routing, logs, and failover while keeping one API surface.

Start intake

FAQ

Do I need to build my own model?

No. Keep your support UI and call AIPower as the model layer. Your app owns conversation history, user identity, and business rules.

Can I avoid runaway cost?

Yes. Start with short replies, daily caps, user tags, and low-cost models for FAQs. Escalate only when needed.

Can it work in China?

Yes. AIPower supports China and global models, plus WeChat Pay and Alipay where available.

Can teams use BYOK?

Yes. Team/BYOK is for shared budgets, provider keys, logs, invoices, and routing control.

Start with one support conversation.

Test output quality, then choose the most efficient model that keeps customers happy.

Try demo