FlashAPI
← API preview

Developer migration guide · 24 September 2026

Move an OpenAI-compatible chat client to Qwen or DeepSeek in Southeast Asia

Keep the text chat request shape, then change the provider base URL, API key and model ID. The easy part is sending one request; the production decision requires checking region, language quality, error behavior, latency and the full token bill.

The short answer

Alibaba Cloud documents an OpenAI-compatible Chat Completions base URL in Singapore for Qwen, and DeepSeek documents an OpenAI-compatible base URL for its API. Run the same small text request against each with its own key and model ID. Treat an HTTP 200 as a connectivity check, then evaluate your real Indonesian, Vietnamese and Thai tasks before moving users.

Published routes to test directly

These are provider endpoints, not FlashAPI routes. Each needs an account and a key issued by that provider. Check the linked documentation again before use because model availability and API details can change.

Direct provider Chat Completions configuration checked 24 September 2026
ProviderSDK base URLExample model IDRegion note
Alibaba Cloud Model Studiohttps://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1qwen3.8-flashDocumented Singapore deployment. Replace {WorkspaceId} with your workspace ID and use the matching account key. Official Chat API ↗
DeepSeek APIhttps://api.deepseek.comdeepseek-flashThe public base URL does not itself establish a Singapore processing region. Official models and base URL ↗

FlashAPI has no connected upstream provider today. We are using these public references to decide which routes a future unified API pilot should support.

One server-side smoke test for both routes

In a local Node.js project, install the official openai package with npm install openai. Set AI_BASE_URL, AI_API_KEY and AI_MODEL in your shell or secret manager, then run node route-smoke.mjs. Use the Qwen row or DeepSeek row above; never put a provider key in a browser bundle or repository. This is an example for your own provider accounts, not a FlashAPI credential.

// Save as route-smoke.mjs. Run on a trusted server with Node.js and "openai" installed.
import OpenAI from "openai";

for (const name of ["AI_BASE_URL", "AI_API_KEY", "AI_MODEL"]) {
  if (!process.env[name]) throw new Error(`Missing ${name}`);
}

const client = new OpenAI({
  baseURL: process.env.AI_BASE_URL,
  apiKey: process.env.AI_API_KEY,
  timeout: 60_000,
  maxRetries: 0,
});

const result = await client.chat.completions.create({
  model: process.env.AI_MODEL,
  messages: [{
    role: "user",
    content: "Reply in Bahasa Indonesia in one sentence: A parcel is late. Ask for the order number; do not invent a delivery date.",
  }],
  max_tokens: 1024,
  stream: false,
});

console.log(JSON.stringify({
  model: result.model,
  finish_reason: result.choices[0]?.finish_reason,
  answer: result.choices[0]?.message?.content,
  usage: result.usage,
}, null, 2));

The code prints the provider-reported model, answer, finish reason and token usage. A missing answer or finish_reason: "length" is a failed acceptance result even if the HTTP call succeeded. This request can incur provider charges. The 1,024-token cap limits this one test, but the providers document different token-limit behavior for thinking output; compare the returned usage and current billing rules before extrapolating. DeepSeek currently defaults to thinking mode, so a short visible answer can still consume reasoning tokens.

Before a production switchKeep your existing route as a fallback until the new account, model and region pass the checks below. Change one variable at a time so errors are diagnosable.

Five checks before moving Southeast Asian traffic

  1. Account and route. Confirm the selected key, workspace (for Qwen), model ID and billing region in the provider console. Save the exact endpoint and model version with your test result.
  2. Language and task quality. Run representative Indonesian, Vietnamese and Thai support requests, including mixed-language messages and local names. Have native-language reviewers score whether the reply follows instructions, invents facts or needs a human escalation.
  3. Compatibility beyond the smoke test. Exercise the exact features you use: streaming chunks, structured output, tool calls, timeout handling, errors and usage fields. A shared Chat Completions request does not guarantee identical optional behavior.
  4. Actual cost. Measure your input and output token mix, reasoning usage, retries and caching. Apply the published rate for your account and region. Try our public-list-rate cost calculator; it is an estimate, not a provider invoice or FlashAPI quote.
  5. Regional response time. Test from your application's actual Southeast Asian network paths. Report first visible text and full response p50/p95, failure count, concurrency and time window. Use the reproducible streaming benchmark method.

Our selection rubric is a suggested test plan, not a published head-to-head benchmark. We have not run these models through FlashAPI or measured FlashAPI latency.

Compare public model rates and selection criteria ↗

Questions teams ask before switching

Can I switch providers by changing only base URL, key and model ID?

For this basic text-only Chat Completions smoke test, that is the starting point. It does not prove that streaming, tool calls, JSON output, token limits, errors or data handling behave the same way. Validate each feature your application actually uses before switching production traffic.

Does Qwen's Singapore endpoint guarantee fast responses in Indonesia, Vietnam or Thailand?

No. The official URL identifies a Singapore endpoint, but client-visible speed also depends on the user's network path, request size, model load and concurrency. Run the same streaming test from your target countries and report failures alongside p50 and p95.

Does DeepSeek's public base URL identify a Southeast Asian processing region?

No regional location follows from the URL alone. Confirm processing and data terms directly with the provider for your account and use case; do not infer residency from a compatible API format.

Can I call these models through FlashAPI today?

No. This guide describes direct calls to the providers' published APIs. FlashAPI's unified gateway is in development; no upstream provider is connected and no FlashAPI customer API key has been issued.

Primary documentation

Provider route and model details were checked on 24 September 2026. The code and acceptance checklist are FlashAPI's practical synthesis of these published interfaces; no provider connection or benchmark result is implied.

Would one API simplify your next migration?

Tell us your target country, language mix, current client, must-have features and monthly token volume. We will use that specification to prioritize the first real upstream pilot.

Share your requirements