- Publication date: October 16, 2026
Which API key should I use?
For Standard and Coding Plan keys created from October 16 onward, the key type determines how calls are billed. Across supported endpoints, Standard keys use standard API billing, while Coding Plan keys use the corresponding plan. Changing the endpoint does not change the key’s billing type.
For example, using a Standard API Key in a coding tool does not consume your Coding Plan quota, even if you have a subscription. It may incur pay-as-you-go charges against your account balance.
What happens to existing API keys?
Keys created before October 16, 2026 are classified as follows. Your key values remain unchanged, and this classification update does not require you to reconfigure existing keys.
Some existing keys for dedicated enterprise services or partner channels retain their previous compatibility behavior. Refer to the key’s classification in the console and your existing service agreement.
How Compatible keys work and are billed
A Compatible label means your key retains its existing calling behavior and billing rules. You can continue using it as before. Billing for an existing Compatible key depends on both the endpoint and whether the account has ever had a Coding Plan, regardless of which list the key appears in. Common endpoints and their billing behavior are listed below:| API / endpoint | Base URL configured in your tool | Billing for a Compatible key |
|---|---|---|
| OpenAI Chat Completions — standard API | https://api.z.ai/api/paas/v4 | Uses your account balance or applicable usage bundles. Does not consume Coding Plan quota. |
| OpenAI Chat Completions — Coding Plan endpoint | https://api.z.ai/api/coding/paas/v4 |
|
| Anthropic Messages — general endpoint | https://api.z.ai/api/anthropic | |
| OpenAI Responses — general endpoint | https://api.z.ai/api/v1 |
For example, if your account currently has an active Coding Plan with available quota, the same existing Compatible key uses plan quota at https://api.z.ai/api/coding/paas/v4. If you change the Base URL to https://api.z.ai/api/paas/v4, calls use standard API billing and may deduct from your account balance even while plan quota remains.
FAQ
How does this update affect me? Do I need to reconfigure anything?
- You can keep using your existing keys. This update does not require you to replace keys or reconfigure your tools.
- Choose the right entry point when creating a new key. To use Coding Plan quota, get a key from API Keys → Personal Coding Plan or Team Coding Plan → My Plan. For pay-as-you-go usage or usage bundles, create a Standard API Key on the API Keys page.
Why is my account balance being charged when I have a Coding Plan?
Check the key configured in your tool. Standard keys do not use Coding Plan quota. An existing personal Compatible key also uses standard API billing when calling the standard API endpoint. To use plan quota, get a key from the corresponding Coding Plan entry point and replace the key in your tool. For setup instructions, see the Quick Start.How do I switch an existing Compatible key to pay-as-you-go after my plan expires?
After your plan expires, calls made with an existing Compatible key to plan endpoints do not automatically switch to pay-as-you-go billing. To continue:- Open the API Keys page and create a Standard API Key.
- Replace the Compatible key in your tool or application with the new Standard key. You can keep the same endpoint.
Why can’t I find the API Key entry for my Individual Plan?
The Personal Coding Plan tab on the API Keys page appears for accounts that have subscribed to an Individual Plan. If it is missing, make sure you are signed in to the account used for that subscription. Team Plan members should get their keys from Team Coding Plan → My Plan.If your key’s classification or API responses do not match the expected behavior, contact Technical Support with the error details and request ID. Keep your API keys secure and never share a complete key.