OpenAI-compatible API
OpenAI-compatible API gateway for developers in Vietnam.
A good OpenAI-compatible API should let your app keep the same SDK pattern while changing the base URL, API key, and model ID. For Vietnam-based developers, payment and quota clarity matter just as much as model choice.
What to look for
Drop-in SDK shape
Use existing OpenAI SDK clients and set a custom base URL instead of rewriting client code.
Model IDs that tools can pin
Use exact IDs such as gpt-5.5-low so CLI tools and apps behave consistently.
Request-based plans
Predictable request quotas and RPM limits are easier to budget for small teams.
Payment that works locally
VietQR/VNPay support lowers friction when international cards are not convenient.
Base URL pattern
const client = new OpenAI({
apiKey: process.env.ZORA_API_KEY,
baseURL: 'https://api.zora.io.vn/v1',
});Use cases
- Internal apps that already use the OpenAI SDK.
- Codex CLI workflows that need a Responses-compatible custom provider.
- Claude Code workflows that need an Anthropic Messages-compatible route.
- Vietnamese teams that prefer VietQR/VNPay and fixed request packages.
FAQ
What is an OpenAI-compatible API?
It is an API that follows the OpenAI-style request shape, SDK configuration, base URL pattern, and endpoints closely enough that developers can reuse existing OpenAI SDK clients.
Why use an API gateway instead of one model provider directly?
A gateway can centralize API keys, model access, payment, quotas, RPM, and tool setup while keeping the application code close to the OpenAI SDK pattern.
What makes an OpenAI-compatible API useful in Vietnam?
Local payment, Vietnamese support, free testing, and clear request packages can reduce friction for developers and small teams.