All Products
Search
Document Center

Global Accelerator:Use Global Accelerator to proxy and schedule AI models

Last Updated:Oct 21, 2026

When calling AI APIs across regions, enterprises often face challenges such as accessing multiple models based on different business scenarios, high latency due to clients and backend models being in different regions, complex cross-region and cross-model scheduling and disaster recovery when backend models are distributed across multiple regions, and request detours caused by self-managed gateways in different regions. Global Accelerator (GA) endpoint groups support the AI service type and, combined with service extension capabilities, enable unified integration of multiple AI providers at the GA entry point for traffic distribution.

This feature is in invitational preview. To request access, contact your account manager.
  • Model proxy: After configuring forwarding conditions for AI models, route traffic to different AI service endpoint groups based on model names.

  • Unified API key management: Store real provider API keys securely on the GA side and enable automatic rotation across multiple keys.

  • Fault tolerance fallback: Forwarding actions support fallback. When an endpoint group becomes unavailable, traffic automatically fails over to another endpoint group—across regions and models.

  • Service extension: GA supports service extensions. Use a service extension to perform API key pre-authentication. Each forwarding rule can associate with one service extension.

image

Unified multi-model access

To call multiple AI models through a single entry point, use GA endpoint groups with the AI service type to integrate multiple providers. Clients send OpenAI-compatible requests to GA and specify a model name. GA routes each request to the corresponding backend AI service based on the model name. This unified entry reduces business complexity and maintenance costs.

Before deployment, ensure the following:

  • You have activated Global Accelerator.

  • You have registered a custom domain. If your acceleration region includes the Chinese mainland or you use Model Studio in China (Beijing), complete ICP filing for your custom domain.

  • You have obtained at least one API key from an AI provider (obtain Alibaba Cloud Model Studio keys from the Model Studio console; contact your provider for OpenAI-compatible services).

  • If using an HTTPS listener (recommended), prepare a server certificate that matches your custom domain and upload it to Certificate Management Service.

If your configuration accelerates traffic between the Chinese mainland and China (Hong Kong), Macao (China), Taiwan (China), or other countries and regions, complete the cross-border data compliance commitment as prompted in the console. Evaluate your data transfer compliance and ensure it meets applicable laws, regulations, and product terms.

Console

Configure AI service endpoint groups

Log on to the Global Accelerator console and click Create Standard Pay-as-you-go Instance.

  1. Basic Instance Configuration: Select an Accelerated IP Address Type as needed.

  2. Configure Acceleration Area: Set the Acceleration Area and Assign Bandwidth.

  3. Configure Listeners: Set the Intelligent Routing. For Protocol, select HTTPS. Set Port to 443. For SSL Certificate Configuration, choose the uploaded server certificate that matches your custom domain.

  4. Configure an Endpoint Group:

    After creating the GA instance, go to the listener details page, select the Endpoint Group tab, and click Add Endpoint Group. Follow these steps to configure AI service endpoint groups in different regions. Each endpoint group supports only one backend service of type AI service. You cannot add other backend services after adding this type.
    • Region: Choose the region closest to your AI provider’s available service.

      If your business involves acceleration between the Chinese mainland and China (Hong Kong), Macao (China), Taiwan (China), or other countries and regions, read and sign the Compliance Commitments Regarding Cross-border Data Transfers as prompted.
    • Backend Service Type: Select AI Service.

    • LLM Provider: Currently supports Alibaba Cloud Model Studio and OpenAI Compatible.

    • Service Endpoint: Automatically filled after selecting a provider. Alibaba Cloud Model Studio defaults to https://dashscope.aliyuncs.com/compatible-mode/v1. OpenAI Compatible defaults to https://api.openai.com/v1. Modify as needed if using a self-hosted OpenAI-compatible service.

    • API key: Enter your provider’s API key. You can enter multiple keys (separated by line breaks). GA rotates among them to improve availability.

      This API key authenticates requests with your AI provider. Keep it secure and avoid exposure.
    • Weight (Valid values: 0 to 255): Each endpoint group supports only one AI service backend type. The weight is fixed at 255 and cannot be changed.

  5. Configuration Review: Submit your settings.

Configure forwarding rules

  1. After creating the GA instance, click the instance ID, select the Listeners tab, click the listener ID, then click the Forwarding Rule tab, and click Add Forwarding Rule.

  2. Configure forwarding rules to route requests for different models to their respective endpoint groups:

    • Name: Enter a custom name.

    • If (Matching All Conditions): Select AI Model and configure as follows:

      • Protocol: Fixed as OpenAI Compatible.

      • Model Name (Optional): Use Glob syntax to match model names. For example, qwen-* matches all Qwen series models, and * matches all models. You can add multiple model names; they are evaluated with an "OR" relationship.

    • Then: Select Forward and choose the corresponding AI service endpoint group.

  3. Click OK to create the forwarding rule.

  4. To route different models to multiple providers, repeat these steps to create separate forwarding rules for different Glob model names. For example, client requests with model=qwen-plus and model=gpt-4o hit different rules and route to their respective providers.

If no model name is specified, the condition matches all OpenAI-compatible requests. If specified, it matches only the named models. Drag rules to adjust priority.

Configure DNS resolution and verify

  1. On the instance details page, copy the GA accelerated domain name (CNAME). In your custom domain’s DNS provider, add a CNAME record pointing your custom domain to the GA accelerated domain.

    DNS propagation typically takes minutes, depending on your DNS provider’s TTL setting.
  2. Use your custom domain to call the AI service API and verify the integration.

    Taking the model name <kbd data-init-id="s2-cond-kbd-1" data-tag="userinput" id="21f447ae1e2hv">qwen-*</kbd> as an example.
    curl -X POST https://your-domain.com/v1/chat/completions \
      -H "Content-Type: application/json" \
      -d '{
        "model": "qwen-plus",
        "messages": [{"role": "user", "content": "Hello"}]
      }'

    On success, the model field in the response is qwen-plus, confirming the request was correctly routed to Alibaba Cloud Model Studio.

API

  • Call CreateEndpointGroup to create an AI service endpoint group. Key parameters: EndpointGroupType=default; EndpointConfigurations[].Type=AIService; SubType=Bailian (Alibaba Cloud Model Studio) or OpenAICompatible (OpenAI compatible); pass API keys in ApiKeys; set Weight=255.

  • Call the CreateListener API to create an HTTPS listener. By default, it associates with your created AI service endpoint group.

  • Call the CreateForwardingRules API to create forwarding rules:

    • RuleConditions[].RuleConditionType: Set to AIModel.

    • AIModelConfig.Protocol: Set to OpenAICompatible; pass Glob model names in AIModelConfig.ModelNames (optional).

    • RuleActions: Configure RuleActionType=ForwardGroup to forward to an AI service endpoint group.

If your business involves acceleration between the Chinese mainland and China (Hong Kong), Macao (China), Taiwan (China), or other countries and regions, complete the cross-border data compliance commitment first.

Cross-region disaster recovery

Building on unified multi-model access, configure fallback for cross-region disaster recovery. Forwarding actions support fallback. You can define multiple fallback targets. If the primary endpoint group becomes unavailable, traffic automatically switches to endpoint groups in other regions. Clients gain multi-region disaster recovery without code changes.

Console

Configure multi-region endpoint groups

After creating a GA instance, click the instance ID, select the Listeners tab, click the listener ID, select the Endpoint Group tab, and click Add Endpoint Group to configure AI service endpoint groups in different regions.

Configure forwarding rules

After configuration, verify: when the primary endpoint group fails, requests automatically fall back in sequence to other regional endpoint groups, which respond via their respective providers or regions.

  1. On the listener details page, click the Forwarding Rule tab, then click Add Forwarding Rule or Edit an existing rule.

  2. Configure the forwarding rule:

    • If (Matching All Conditions): Select AI Model and configure as follows:

      • Protocol: Fixed as OpenAI Compatible.

      • Model Name (Optional): Use Glob syntax. For example, qwen-* matches all Qwen series models, and * matches all models. Add multiple names with an "OR" relationship.

    • Then: Configure two actions in order:

      1. Forward: Select an endpoint group in one region.

      2. Click Add Action, select Rollback, and choose an endpoint group in another region.

      Fallback action must come after the Forward To action. Each forwarding rule must contain exactly one action of type Forward To, Redirect To, or Return Fixed Response.
  3. Click OK to create the rule. Repeat for different Glob model names as needed.

If no model name is specified, the condition matches all OpenAI-compatible requests. If specified, it matches only the named models. Drag rules to adjust priority.

API

  • Call CreateEndpointGroup to create multi-region AI service endpoint groups, and use CreateListener to create an HTTPS listener.

  • Call CreateForwardingRules to create forwarding rules:

    • RuleConditions[].RuleConditionType: Set to AIModel.

    • AIModelConfig.Protocol: Set to OpenAICompatible; pass Glob model names in AIModelConfig.ModelNames (optional).

    • First RuleActions entry: RuleActionType=ForwardGroup, linked to the primary endpoint group.

    • Second RuleActions entry: RuleActionType=Fallback, linked to another regional endpoint group. It must follow the ForwardGroup action.

Service extension

GA supports service extensions. Currently, you can use an API key authentication service extension to validate client credentials at the GA entry. Clients use a unified API key issued by GA. Only authenticated traffic forwards to AI service endpoint groups. Client credentials can be issued, rotated, and revoked independently of backend provider API keys, simplifying unified business management.

Console

  1. Go to the GA console – Service Extensions page and click Create Service Extension.

    • Component Name: Currently supports only API Key Authentication.

    • Timeout (ms): Maximum time to wait for the component response. Requests fail if this time is exceeded.

    • Failure Policy: How to handle requests if the component fails. Currently supports only Terminated, which blocks unauthenticated traffic.

    • Credential Source:

      • Authorization:Bearer: Extract credentials from the HTTP Authorization header using the Bearer scheme. Recommended for OpenAI-compatible protocols.

      • Custom HTTP Header: Extract credentials from a specified HTTP header.

      • Custom Query String: Extract credentials from a specified URL query parameter.

    • Credential management: Configure up to 3 credentials. Generation Method: Custom. After saving, credentials display as *******. Keep them secure.

  2. On the service extension details page, go to the Associate Resource tab and click Add Associated Instance. Select the configured Forwarding Rule to associate.

    Service extensions take effect on listener traffic by associating with forwarding rules. You can associate multiple rules.
  3. Use the GA-issued credential to call the AI service API and verify authentication:

    • With a valid credential matching the configured source: Traffic forwards normally to the backend AI service, where the provider’s API key handles backend authentication.

    • With an invalid or missing credential and failure policy set to Terminate: GA rejects the request at the entry.

More information

Limits

  • Only standard pay-as-you-go instances support AI service endpoint groups.

  • AI service endpoint groups:

    • Only HTTP and HTTPS listeners are supported.

    • Do not support health checks.

    • AI model forwarding conditions and path-based conditions are mutually exclusive. You cannot configure both in the same rule.

    • Custom header names in forwarding rules cannot use these reserved prefixes: X-Ga-, Ga-.

Quotas

Quota item

Default

Maximum

Increase quota

Credentials per API key authentication component

3

3

Cannot be increased.

Fallback services per forwarding rule

5

10

Request an increase in Quota Center.

Service extension components per user

5

20

Request an increase in Quota Center.

Total service extensions per user

50

50

Cannot be increased.

Resources per service extension

200

300

Request an increase in Quota Center.

Service extensions per GA instance

200

500

Request an increase in Quota Center.

Billing

AI model proxy features—including AI service endpoint groups, model-based forwarding conditions, fallback actions, and API key authentication service extensions—are currently free for a limited time. You pay only for the standard Global Accelerator instance fees. For details, see Global Accelerator billing.