Is GPTokens compatible with OpenAI SDKs?
GPTokens supports the common OpenAI-compatible request pattern. Set the GPTokens base URL, use a GPTokens API key, and choose a model ID returned by the live model list.
API documentation
Start with one base URL and a GPTokens API key, discover live Chinese LLM routes, and keep model selection configurable as availability changes.
Documentation map
Configure authentication, the base URL, model IDs, and chat completion requests.
Model directoryShortlist DeepSeek, Qwen, Kimi, GLM, MiniMax, MiMo, and other routes before live discovery.
BillingPlan for token usage, retries, fallback traffic, and live account-specific pricing.
SecurityKeep credentials server-side and separate keys across development, staging, and production.
Start here
https://gptokens.ai/v1./v1/models with your key to confirm the live model IDs available to your account.OpenAI-compatible request
import OpenAI from "openai";
const client = new OpenAI({
apiKey: process.env.GPTOKENS_API_KEY,
baseURL: "https://gptokens.ai/v1"
});
const response = await client.chat.completions.create({
model: "qwen3.7-plus",
messages: [{ role: "user", content: "Compare Chinese LLM routes for my task." }]
});Route discovery
Model pages help with planning, but provider availability, model identifiers, account access, and pricing can change. Check /v1/models and the live terms in Workspace before hard-coding a production route.
FAQ
GPTokens supports the common OpenAI-compatible request pattern. Set the GPTokens base URL, use a GPTokens API key, and choose a model ID returned by the live model list.
Use the model directory for planning, then call /v1/models with your API key before production because route availability and identifiers can change.
No. Keep GPTokens API keys in server-side secrets and use separate keys for development, staging, and production.
Use the pricing page for billing concepts, Workspace for live account terms and route prices, and the security page for key-handling guidance.