Platform For AI:Deploy a dedicated OpenClaw with PAI-EAS in 5 minutes

1. Log on to the PAI console. Select a region on the top of the page. Then, select the desired workspace and click Enter Elastic Algorithm Service (EAS).

2. On the Inference Service tab, click Deploy Service. In the Scenario-based Model Deployment section, click OpenClaw Deployment.

3. Configure the following key parameters:

   Parameter	Description
   Service Name	Enter a custom service name. Example: openclaw_demo
   Image Configuration	Select the latest version.
   Resource Configuration	Select a CPU instance type based on your resource requirements. The default is ecs.c7a.large.
   Model Settings	Select an OSS path to store the OpenClaw configuration, such as oss://examplebucket/openclaw/.
   VPC	Create and configure a VPC, vSwitch, and security group. Note OpenClaw requires internet access for web searches or browser usage. We recommend using a VPC with internet access configured.

4. Click Deploy. Wait until the service status is Running. This indicates the deployment is successful.

1. Create an Internet NAT gateway and attach an EIP

Go to the NAT Gateway – Internet NAT Gateway purchase page.

• Billing Method: Pay-as-you-go.

• Region: Select the region where the EAS service is located.

• Network and Zone: Select the VPC configured for the EAS service. This setting cannot be changed after creation.

• EIP: Select an unattached elastic IP address (EIP) or purchase a new one.

2. Configure an SNAT entry

Go to the Internet NAT Gateway page. Find the Internet NAT gateway that you created, and in the Actions column, click Configure SNAT . Click Create SNAT Entry.

• SNAT Entry: Select VPC Granularity.

• Select EIP: Select the configured EIP.

Integrate with DingTalk

1. Create a DingTalk bot and obtain its Client ID and Client Secret. For more information, see Create an OpenClaw Bot with One Click.

2. In the OpenClaw WebUI, go to Configuration > RAW. In the channels configuration block, find dingtalk-connector. Enter your Client ID and Client Secret, and then save the configuration.

   In the dingtalk-connector block, after entering the clientId and clientSecret, make sure that enabled is set to true. You can also adjust other fields as needed, such as separateSessionByConversation, groupSessionScope, and sharedMemoryAcrossConversations.

Lark

1. Go to the Lark Open Platform. Click Create Enterprise Self-Built App, enter an application name and description, select an icon, and then click Create.

2. In the left-side navigation pane, click Credentials and Basic Information. Copy the App ID (for example, cli_xxx) and App Secret.

3. In the left-side navigation pane, click Permission Management. Click Batch Import/Export Permissions, paste the following JSON configuration, click Next, Confirm New Permissions, and then click Request Activation.

   View JSON configuration

   {
     "scopes": {
       "tenant": [
         "aily:file:read",
         "aily:file:write",
         "application:application.app_message_stats.overview:readonly",
         "application:application:self_manage",
         "application:bot.menu:write",
         "cardkit:card:write",
         "contact:user.employee_id:readonly",
         "corehr:file:download",
         "docs:document.content:read",
         "event:ip_list",
         "im:chat",
         "im:chat.access_event.bot_p2p_chat:read",
         "im:chat.members:bot_access",
         "im:message",
         "im:message.group_at_msg:readonly",
         "im:message.group_msg",
         "im:message.p2p_msg:readonly",
         "im:message:readonly",
         "im:message:send_as_bot",
         "im:resource",
         "sheets:spreadsheet",
         "wiki:wiki:readonly"
       ],
       "user": ["aily:file:read", "aily:file:write", "im:chat.access_event.bot_p2p_chat:read"]
     }
   }

4. In the left-side navigation pane, click Add App Capabilities. On the Add by Capability tab, find the Bot card and click Configure.

5. Configure event subscription

   1. In the OpenClaw WebUI, go to Configuration > RAW. In the JSON configuration for channels, find feishu, enter the App ID and App Secret you obtained, and then click Save. Note: For security, the secret is hidden and displayed as __OPENCLAW_REDACTED__ after you save it.

   2. On the Lark Open Platform, go to the Events and Callbacks page. On the Event Configuration tab, set Subscription Method to Receive Events via Persistent Connection and click Save. Verify that the subscription method is Persistent Connection (recommended).

   3. On the event configuration page, click Add Event, search for Accept Message, and then click Confirm Add.

6. On the Version Management and Publishing page, create a new version. Enter the Application Version Number and Update Description, click Save, and then submit the version for review and publish it.

   In the version details, set both the Default capability on mobile and Default capability on desktop to Bot.

7. Add the bot to your favorites. In the Workbench, click Add to Favorites. Search for your bot and click Add. The bot appears in your favorites list. Double-click it to open the chat interface.

WeCom

1. Create a WeCom bot and obtain its Bot ID and Secret. For more information, see How OpenClaw integrates with WeCom intelligence.

2. In the OpenClaw WebUI, go to Configuration > RAW. In the channels configuration block, add the configuration for WeCom. Replace the placeholder values for botId and secret with your actual credentials.

       "wecom": {
         "enabled": true,
         "botId": "${WECOM_BOT_ID}",		// Replace with your actual content
         "secret": "${WECOM_SECRET}",	// Replace with your actual content
         "allowFrom": [
           "*"
         ],
         "dmPolicy": "open"
       }

Configure multiple model providers

In the WebUI, go to Configuration > RAW. In the JSON configuration, find the models block. You can configure multiple model providers under providers:

{ 
  // Other configurations omitted ...
  models: {
    mode: 'merge',
    providers: {
      dashscope: {},
      codingplan:{},
      eas:{},
    },
   },
}

providers: {
  codingplan : {
    baseUrl: 'https://coding.dashscope.aliyuncs.com/v1',
    apiKey: '__OPENCLAW_REDACTED__',        // Replace with your actual content
    api: 'openai-completions',
    models: [
      {
        id: 'qwen3.5-plus',
        name: 'qwen3.5-plus',
        reasoning: false,
        input: [
          'text',
          'image',
        ],
        contextWindow: 1000000,
        maxTokens: 65536,
      },
      {
        id: 'qwen3-coder-next',
        name: 'qwen3-coder-next',
        reasoning: false,
        input: [
          'text',
        ],
        contextWindow: 262144,
        maxTokens: 65536,
      },
    ],
  },
},

    providers: {
      eas: {
        baseUrl: 'http://xxxxxx.cn-hangzhou.pai-eas.aliyuncs.com/api/predict/quickstart_deploy_xxxx/v1/',
        apiKey: '__OPENCLAW_REDACTED__',
        api: 'openai-completions',
        models: [
          {
            id: 'Qwen3.5-27B',
            name: 'Qwen3.5-27B',
            api: 'openai-completions',
            reasoning: false,
            input: [
              'text',
            ],
            cost: {
              input: 0,
              output: 0,
              cacheRead: 0,
              cacheWrite: 0,
            },
            contextWindow: 1000000,
            maxTokens: 65536,
          },
        ],
      },
    },

  models: {
    mode: 'merge',
    providers: {
      dashscope: {
        baseUrl: 'https://dashscope.aliyuncs.com/compatible-mode/v1',
        apiKey: '__OPENCLAW_REDACTED__',    // Replace with your actual content
        api: 'openai-completions',
        models: [
          {
            id: 'qwen3.5-plus',
            name: 'qwen3.5-plus',
            reasoning: false,
            input: [
              'text',
              'image',
            ],
            contextWindow: 1000000,
            maxTokens: 65536,
          },
        ],
      },
    },
  },

Configure the default model

In the WebUI, go to Configuration > RAW. In the JSON configuration, find the agents block.

• agents.defaults.model.primary: Sets the default model.

• Model name: The format is provider/model, where provider is the provider name configured in providers and model is the model ID.

  agents: {
    defaults: {
      model: {
        primary: 'dashscope/qwen3.5-plus',
      },
      models: {
        'dashscope/qwen3.5-plus': {},
        'coding/qwen3-coder-next': {},
        'eas/Qwen3.5-27B': {}
      },
    },
  },