ModelSmarterStart intake
ModelsPlansDocs
Browse documentationTap to expand
Documentation overview

Product basics

What Model Studio CoversFirst Qwen API CallChoose a ModelRegions and Deployment ModesRequest Quote Checklist

All sections

Scroll
Product basicsBilling and pricingAPI setupModel inferenceDeveloper toolsOperationsSecurity and complianceTutorials and support

Regions

Regions and Deployment Modes

Model Studio endpoints, API keys, data routing, and model availability depend on the deployment mode. A quote must specify the intended region before payment.

Product basicsOfficial source

Who this is for

Buyers with compliance, latency, or geographic requirements.

Configuration reference

Values to confirm before setup

International / Singapore

https://dashscope-intl.aliyuncs.com/compatible-mode/v1

United States / Virginia

https://dashscope-us.aliyuncs.com/compatible-mode/v1

China / Beijing

https://dashscope.aliyuncs.com/compatible-mode/v1

China / Hong Kong

https://cn-hongkong.dashscope.aliyuncs.com/compatible-mode/v1

Token Plan Team Edition

https://token-plan.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1

Token Plan Anthropic-compatible

https://token-plan.ap-southeast-1.maas.aliyuncs.com/apps/anthropic

Setup flow

Practical steps

  1. 01Ask where the buyer's users and data are located.
  2. 02Choose the deployment mode before creating keys.
  3. 03Use the matching base URL and key-management page.
  4. 04Confirm the chosen model supports that deployment mode.
  5. 05Record the region in the written quote and handoff document.

Why region matters

A base URL is not just a network address. It determines the deployment mode, where the access key belongs, and which model list should be checked.

Customer-facing rule

Never sell 'global' casually. Use precise phrases such as Singapore-hosted international mode, US deployment mode, EU deployment mode, or region subject to official terms.

Common mistakes

Check these before escalating

  • Region mismatch can look like an authentication or model-not-found error.
  • Some API examples use Singapore by default and should not be copied blindly.
  • Compliance review belongs to the customer and official provider, not ModelSmarter alone.

Related guides

OpenAI-Compatible Chat API

Most OpenAI-compatible integrations need only three changes: API key, base URL, and model name. The hard part is choosing the correct plan and endpoint.

Choose a Model

Select the model by workload, context length, modality, region, latency, and cost. The model list changes over time, so final quotes should reference the official current catalog.

Security and Compliance Checklist

Security review covers key ownership, permissions, transport, data location, privacy, training-data commitments, and customer approval.