English

← Back to list

How do you solve OpenClaw's failure to call Precious?

itadol5j

How do you solve OpenClaw's failure to call Precious?

This problem has been bothering me for a long time and it's finally solved! If you also have a problem with OpenClaw's inability to call on the Alien Nebula model, this lesson is for you.

Problem description

During the recent use of OpenClaw, it was found that the DashScope model could not be correctly used. This is reflected in:

  • Configure API Key but call failed
  • Return InvalidApikey Error
  • Automatically switch system to fallback model
  • There's no deduction on the BPR.

Problem check.

1. Profile location

OpenClaw has two profiles to check:

  • ~/.openclaw/openclaw.json - master profile
  • ~/.openclaw/agents/main/agent/models.json – model profile

Focus: Models.json is the file that really controls the mode call!

2. Wrong API interface

In models.json, bailian's baseUrl configuration is wrong:

// ❌ 错误配置
baseUrl: https://open.bigmodel.cn/api/paas/v4

// ✅ 正确配置
baseUrl: https://coding.dashscope.aliyuncs.com/v1

Solutions

Step 1: Upgrade OpenClaw

Upgrade OpenClaw from the old version to the latest (2026.3.7):

cd /home/toor/Desktop/myworkspace/openclaw
git stash
openclaw update

Step 2: Get a new API Key

  1. Login to Ali Yunpur Control.
  2. Enter API-KEY management page
  3. Create a new API Key

Step 3: Modify Models.json

Edit the model profile and modify the bailian configuration:

bailian: {
  baseUrl: https://coding.dashscope.aliyuncs.com/v1,
  apiKey: 你的API-Key,
  api: openai-completions
}

Step 4: Restart Gateway

openclaw gateway restart

Summary

One of the key steps in addressing OpenClaw's inability to mobilize is:

  1. Upgrade to the latest version (2026.3.7)
  2. Models.json (not openclaw.json)
  3. Configure correct baseUrl
  4. Use valid API Key
  5. Restart Gateway

By following the above steps, 99 per cent of the 100% redeployment problem should be solved!

References: