From 531b31efe54a23505e6b071d08a239b74e5a40f1 Mon Sep 17 00:00:00 2001 From: Kyle Howells Date: Thu, 29 Jan 2026 19:30:43 +0000 Subject: [PATCH] docs(zai): correct misleading API key interoperability claim 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 Co-Authored-By: Happy --- docs/providers/zai.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/providers/zai.md b/docs/providers/zai.md index 674e6e493..ea4ff007d 100644 --- a/docs/providers/zai.md +++ b/docs/providers/zai.md @@ -113,9 +113,10 @@ use a single API key for both if desired. ## Important Notes -- **Same API key, different endpoints**: Your API key works on both general and coding - endpoints, but the billing is different. Using a Coding Plan key on the general - endpoint may return error 1113 ("Insufficient balance"). +- **Keys are subscription-gated**: Your API key only works on the endpoint matching + your active subscription. A Coding Plan key will return error 1113 ("Insufficient + 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 and vice versa. Create your key on the platform for your region.