Frequently asked questions

Common questions about using 678API.

Why does my client request fail?#

Check the Base URL, API key, available credits, and model name.

Which funding source is used first?#

When an active subscription has credits, it is usually used before wallet balance.

Which top-up methods are supported?#

Online top-ups support WeChat Pay, Alipay, Visa and other supported cards, Apple Pay, and Google Pay when shown at checkout. Redeem codes remain available. Methods vary by region, currency, device, and browser.

Which clients are supported?#

Clients that accept an OpenAI-compatible Base URL, API key, and model ID are generally supported, including Cursor, Cherry Studio, Chatbox, Open WebUI, Claude Code, Codex CLI, CC Switch, and common SDKs. Specialized completion or built-in Agent features may still use the vendor's own service.

Do I need to sign out of the tool's existing account?#

Usually not. The tool account powers sync, subscriptions, or editor features, while the 678API key authenticates custom model requests. Select 678API in the model or provider settings unless the client explicitly asks you to reauthenticate.

Which Base URL should I use?#

OpenAI-compatible clients normally use https://www.678api.com/v1. Claude Code uses https://www.678api.com for its Anthropic gateway variable. Append /chat/completions only when a field explicitly requests a full endpoint.

Why is the model list empty even though the key is accepted?#

Some clients do not load compatible model lists or filter unknown model IDs. Copy the exact ID from the 678API console and add it manually.

How do I verify that traffic uses 678API?#

Send a short message with a dedicated client key, then match its time and key in 678API usage logs. The model label shown by a client is not conclusive by itself.

How do I restore the original provider?#

Select a built-in provider and disable the custom Base URL or 678API provider. CLI users should also unset the related environment variables, then restart the terminal or client.