Start outside the app
Run one tiny chat request before debugging framework wrappers, agents, or coding assistants.
For overseas developers testing Chinese-strong models in coding assistants, document pipelines, localization QA, and batch jobs, compatibility should be verified before production traffic moves.
Run one tiny chat request before debugging framework wrappers, agents, or coding assistants.
Check JSON output, tools, streaming, and provider-specific fields separately.
Use China-model routes only for non-sensitive, retryable workloads that fit your policy.
Most integration bugs are easier to isolate with a raw request. Confirm the base URL path, API key, model ID, and whether your SDK expects the base URL to include /v1.
curl "$OPENAI_BASE_URL/chat/completions" \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"YOUR_MODEL_ID","messages":[{"role":"user","content":"Reply with one short sentence."}],"stream":false}'
A provider may accept the familiar chat completions shape without supporting every OpenAI feature exactly the same way. Build a small capability matrix for:
response_format, JSON mode, and strict schema behaviortool_choice, and malformed tool-output handlingtop_p, stop, seed, and penaltiesIf normal chat works but response_format fails, the route is reachable. Treat the provider as chat-compatible, fall back to prompt-for-JSON plus validation, and record a clear unsupported-parameter error.
Some Chinese-model routes can expose extra reasoning or metadata fields. Preserve unknown fields in sanitized debug metadata, then normalize the assistant message your application consumes.
Botat is an OpenAI-compatible gateway for overseas developers testing DeepSeek, Qwen, Kimi, and other Chinese-strong models for non-sensitive Chinese content, batch processing, coding assistance, and retryable tasks.
Do not send sensitive personal data, confidential customer data, regulated data, or workloads with strict residency requirements through China-model routes.