Alibaba Cloud Model Studio provides services in multiple regions. Each region offers workspace-specific endpoints, DashScope endpoints, and other endpoint types, and supports multiple service deployment scopes to meet access requirements in different scenarios.
Region overview
The region determines the access point and data storage location. Choose a nearby region to reduce latency.
- Service deployment scope: determines the inference execution location. Select a deployment scope with specific geographic boundaries for data compliance requirements, or select the global deployment scope for a larger inference resource pool if no compliance requirements apply.
- Endpoint: affects concurrency limits, timeouts, and other service guarantees. Each region has independent endpoints.
- The application sends a request to the selected region through the endpoint, and the request data is stored in that region.
- The access region forwards the request to an inference node within the service deployment scope for computation. Transmission is encrypted end-to-end.
- The inference result returns to the access region for storage and is then returned to the application. User static data is always stored in the selected region.
Region | Service deployment scope |
|---|---|
China (Hong Kong) | Global (any available node, including Chinese mainland and overseas) |
China (Hong Kong) (inference within the region) |
Endpoints
Model Studio provides three types of endpoints for model inference APIs in the China (Hong Kong) region: workspace-specific endpoints, DashScope endpoints, and trial endpoints. These are suitable for scenarios ranging from trial experiences to enterprise-level production. Workspace-specific endpoints are recommended. The key differences are as follows:
Item | Workspace-specific endpoint (recommended) | DashScope endpoint | Trial endpoint |
|---|---|---|---|
Endpoint format |
|
China (Hong Kong) region |
|
Applicable scenario | Recommended for production environments. Provides higher concurrency capacity and network isolation, ensuring stable, low-latency access in high-traffic scenarios. | For existing business compatibility. We recommend migrating to the workspace-specific endpoint. | For quick trials and functional validation. Not recommended for production environments. |
Authentication method | Access only the current workspace | Access all workspaces | Access all workspaces |
Rate limit | RPM and TPM vary by model and are aggregated at the Alibaba Cloud account level | RPM and TPM vary by model and are aggregated at the Alibaba Cloud account level | RPM is 1000 (at the Alibaba Cloud account level); TPM varies by model |
Request timeout | 3600 seconds | 600 seconds | 600 seconds |
Protocol support | HTTP, SSE, WebSocket, WebRTC, AOQ (AI over QUIC) | HTTP, SSE, WebSocket | HTTP, SSE |
SLA | 99.9% | 99.9% | Not provided |
Access information
The China (Hong Kong) region has independent endpoints, API keys, and model lists. These cannot be mixed across regions.
Region | Region ID | Workspace-specific endpoint | DashScope endpoint | Trial endpoint | API Key | Model list |
|---|---|---|---|---|---|---|
China (Hong Kong) |
|
|
|
|
- The China (Hong Kong) region distinguishes service deployment scopes by workspace. Before you start calling APIs, go to the Workspace Management page to create a workspace and select a service deployment scope: China (Hong Kong) (Global/China (Hong Kong)).
Migrate to workspace-specific endpoints
Migrating from a DashScope endpoint or trial endpoint to a workspace-specific endpoint requires only two steps, with no need to modify business logic code:
- Obtain the workspace-specific endpoint: On the Workspace Management page, copy the content in the API Host column.
-
Replace the domain name in the request address: Replace the original domain name in your code with the copied API Host (for example,
llm-xxx.cn-hongkong.maas.aliyuncs.com).llm-xxxis the workspace ID. The request addresses for APIs in the China (Hong Kong) region are as follows:- OpenAI-compatible API: replace
https://cn-hongkong.dashscope.aliyuncs.com/compatible-mode/v1withhttps://llm-xxx.cn-hongkong.maas.aliyuncs.com/compatible-mode/v1 - DashScope API: replace
https://cn-hongkong.dashscope.aliyuncs.com/api/v1withhttps://llm-xxx.cn-hongkong.maas.aliyuncs.com/api/v1 - Anthropic-compatible API: replace
https://cn-hongkong.dashscope.aliyuncs.com/apps/anthropicwithhttps://llm-xxx.cn-hongkong.maas.aliyuncs.com/apps/anthropic
- OpenAI-compatible API: replace
Feature support
Region | Real-time inference | Batch inference | Model experience | Model monitoring (basic) | Model monitoring (advanced) | Model alerting | Transmission security | Permission management | Model fine-tuning |
|---|---|---|---|---|---|---|---|---|---|
China (Hong Kong) | Supported | Not supported | Supported | Supported | Not supported | Not supported | Supported | Supported | Not supported |
Related documents
- Tongyi Qianwen API reference
- Recommended models — Models and context lengths by region
- Model inference pricing — Pricing by region /China (Hong Kong)/
- Rate limiting— RPM and TPM limits
- Obtain an API key — Create and manage API keys
- Base URL overview — Model service endpoints
- Regions and endpoints - More region information