The Complete Guide to OpenAI-Compatible APIs for Chinese LLMs

One of the smartest decisions OpenAI made was making their API the de facto standard for LLM interaction. The openai Python package, the ChatCompletion interface, and the message format have become the HTTP of AI — nearly every major model provider now supports some form of OpenAI compatibility.

This means you can swap models without changing your code. Here's how to use that to access China's best LLMs.

The OpenAI SDK Pattern

If you've used OpenAI's API, you already know the pattern:

from openai import OpenAI

client = OpenAI(api_key="sk-...")
response = client.chat.completions.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "Hello!"}]
)

To access Chinese models through an OpenAI-compatible gateway, you change exactly two things :

client = OpenAI(
    base_url="https://api.tokenmaster.com/v1",  # ← Changed
    api_key="tm-..."                              # ← Changed
)

Everything else stays the same. The same SDK, the same method calls, the same message format.

What This Unlocks

By switching to an OpenAI-compatible gateway for Chinese models, you gain access to:

All accessible through the same SDK, the same API key, the same base URL.

Migration Guide

Step 1: Get Your Gateway Key

Sign up at an OpenAI-compatible gateway for Chinese models. Most offer free trial credits:

# I use TokenMaster
# Sign up at https://api.tokenmaster.com
# Get your API key from the dashboard

Step 2: Update Your Client Instantiation

Python:

# Before: OpenAI only
import os
from openai import OpenAI

client = OpenAI(api_key=os.getenv("OPENAI_API_KEY"))

# After: Multi-model access
TM_KEY = os.getenv("TOKENMASTER_API_KEY")

deepseek_client = OpenAI(
    base_url="https://api.tokenmaster.com/v1",
    api_key=TM_KEY
)
qwen_client = OpenAI(
    base_url="https://api.tokenmaster.com/v1",
    api_key=TM_KEY
)

Node.js:

// Before
import OpenAI from 'openai';
const openai = new OpenAI({ apiKey: process.env.OPENAI_API_KEY });

// After
const tm = new OpenAI({
    baseURL: 'https://api.tokenmaster.com/v1',
    apiKey: process.env.TOKENMASTER_API_KEY
});

Step 3: Choose Your Model

Gateway model names typically follow a convention like provider-model-variant:

# DeepSeek for coding tasks
response = client.chat.completions.create(
    model="deepseek-v4-pro",
    messages=[{"role": "user", "content": "Write a quicksort in Rust"}]
)

# Qwen for long-context analysis
response = client.chat.completions.create(
    model="qwen-3.7-max",
    messages=[{"role": "user", "content": long_document}]
)

# GLM for structured reasoning
response = client.chat.completions.create(
    model="glm-4.5",
    messages=[{"role": "user", "content": complex_prompt}]
)

Model Selection Strategy

Based on months of production usage, here's my recommendation:

Performance Benchmarks

I ran these models against my production workload (summarization + content generation):

Key takeaway: For coding and reasoning, DeepSeek V4-Pro is within 3-5% of GPT-4o at roughly 10% of the cost. The main trade-off is English nuance — if your application depends on perfect English output (marketing copy, creative writing), keep a GPT-4o fallback.

Cost Analysis

For a real-world production workload of 20M input + 5M output tokens/month:

The optimal strategy depends on your workload's quality requirements. Most developers find that 80-90% of their traffic can be handled by Chinese models without noticeable quality degradation.

Production Tips

1. Implement a fallback chain:

models = ["deepseek-v4-pro", "qwen-3.7-max", "gpt-4o"]
for model in models:
    try:
        return await call_model(model, messages)
    except Exception:
        continue

1. Monitor latency: Gateway responses are usually faster than direct OpenAI (edge caching), but can spike. Set up alerts for >500ms responses.

2. Cache aggressively: At $0.18/1M tokens, DeepSeek V4 Flash is cheap enough that you can cache fewer responses. But for identical requests, caching still saves money.

3. Use the right model for the job: Don't use DeepSeek V4-Pro for "what's the weather" — use V4 Flash. Save the expensive models for tasks that need them.

Summary

OpenAI-compatible gateways have made Chinese LLMs accessible to overseas developers without friction. The migration is trivial (change a base URL), the cost savings are substantial (60-80%), and the quality gap is narrowing every month.

If you're paying for GPT-4o out of pocket, it's worth running a side-by-side benchmark with Chinese models through a gateway. The $2 trial credit most gateways offer is enough to evaluate your entire workload.

Built with Chinese LLMs in production. Not affiliated with any gateway. Always benchmark against your specific use case.