romtuck/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(zai): correct misleading API key interoperability claim

Browse Source 
The previous documentation suggested API keys work on both general and
coding endpoints with just different billing. Research confirmed this
is misleading - keys are subscription-gated and will return error 1113
("Insufficient balance") when used on the wrong endpoint type.

Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
This commit is contained in:
Kyle Howells 2026-01-29 19:30:43 +00:00
parent d8fa00e9f2
commit 531b31efe5
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/providers/zai.md
View File

@ -113,9 +113,10 @@ use a single API key for both if desired.
## Important Notes ## Important Notes
- **Same API key, different endpoints**: Your API key works on both general and coding - **Keys are subscription-gated**: Your API key only works on the endpoint matching
endpoints, but the billing is different. Using a Coding Plan key on the general your active subscription. A Coding Plan key will return error 1113 ("Insufficient
endpoint may return error 1113 ("Insufficient balance"). balance") on the general pay-as-you-go endpoint, and vice versa. Choose the provider
variant that matches your subscription type.
- **Regional keys are not interchangeable**: Keys from z.ai don't work on bigmodel.cn - **Regional keys are not interchangeable**: Keys from z.ai don't work on bigmodel.cn
and vice versa. Create your key on the platform for your region. and vice versa. Create your key on the platform for your region.