OpenAI Official API gateway details

OpenAI's official developer platform; ideal for teams needing native GPT, image, speech, and vector interfaces. China access, payment, and compliance must be handled yourself.

Best for: For dev teams with high requirements for the responsible entity, terms, model capabilities, and compliance boundaries.

Current status

Test yourself

Latency reference

Depends on your deployment

/models check

See the platform docs

Last verified

Not verified yet

Status notes

Test plain responses, streaming, error codes, and rate limits yourself before launch.

Pricing mode

Official list price, pay-as-you-go; input, output, cache, and audio/video prices per the OpenAI pricing page.

Price tags

Standard price, High stability, Pay-as-you-go

Free quota

Subject to official account policy and promotions.

Usually you create an API key in the platform console, then replace the SDK's baseURL, model name, and auth details per the docs. Test streaming, function calling, error codes, and rate limits before launch.

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: process.env.AI_GATEWAY_API_KEY,
  baseURL: "see the platform docs"
});

const response = await client.chat.completions.create({
  model: "gpt-4.1-mini",
  messages: [{ role: "user", content: "Test one call through an AI gateway." }]
});

• Supported models: OpenAI, Embedding, Whisper.
• Capabilities: OpenAI-compatible, Streaming, Function calling, Image generation, Speech-to-text, TTS, Embeddings, Log query.
• Documentation completeness: High; editorial stability score 4.9 / 5.

• China networking, account region, and payment must be solved yourself; no multi-provider aggregation.
• Third-party relay pricing, models, and availability can change, so re-check them periodically.

Is OpenAI Official API compatible with the OpenAI API?

This entry is marked as supporting the OpenAI-compatible format, but the exact base_url, model names, and parameters still follow the official docs.

Is OpenAI Official API ready for production?

Run a small-traffic load test, rate-limit test, and error-code test first, and confirm the billing rules; keep a backup provider for important workloads.