GLM Coding Plan Error 1113: Endpoint and Access Checks

GLM Coding Plan error 1113 can appear even after a subscription payment. The message alone does not prove that buying more credit will solve the problem. Z.ai’s official guidance connects this error with Coding Plan usage conditions, including the client, endpoint and eligible model.

This guide gives you a bounded troubleshooting sequence: confirm the request is using the intended subscription route before changing your billing. It is based on Z.ai documentation checked on 16 October 2026, not a new reproduction of the error in a paid account.

What error 1113 tells you—and what it does not

Z.ai’s Coding Plan FAQ explicitly addresses error 1113 after purchase. It says the plan is restricted to supported tools and requires its designated endpoint and supported models. On the check date, its model list names GLM-5.3 and GLM-5.3-Flash.

That makes 1113 a starting point for checking access conditions, not a complete diagnosis of your account. An active receipt, a working dashboard and a failed client request are three separate observations. Keep them separate until you know which account and route the client actually uses.

Online issue reports can help identify questions to ask, but another user’s successful workaround is not proof that your request has the same cause. We use the provider’s setup rules as the reference here.

Check the endpoint before adding money

Client route in Z.ai’s FAQ	Documented base URL	What to verify
Claude Code and Goose	https://api.z.ai/api/anthropic	The client uses the Anthropic-compatible route
Other officially supported Coding Plan tools	https://api.z.ai/api/coding/paas/v4	The selected tool is supported and uses its documented configuration

A base URL is the address your client sends requests to. Copying a working configuration from a different kind of application can therefore send a request through the wrong product route. Avoid treating an ordinary API integration, a coding subscription and a third-party relay as interchangeable.

Our GLM Coding Plan pricing guide explains the subscription budget. For diagnosis, use the provider’s current tool guide for the exact model and endpoint settings, since those can change independently of a saved pricing article.

A six-step troubleshooting sequence

1. Identify the failing request

Record the client name and version, the operation that failed, the time and the full error message after removing secrets. Note whether ordinary chat works while a separate search or vision operation fails. This gives support a defined problem instead of “the subscription does not work.”

2. Confirm the intended account and plan

Open the account that owns the subscription and compare it with the account used to obtain the client’s key. Z.ai’s Claude Code instructions distinguish individual-plan key creation from team-plan key creation. Use the route that matches your membership. Do not paste a key into a public issue to demonstrate that it exists.

3. Inspect the active configuration

Compare the configured base URL and environment-variable names with the official instructions for that client. For Claude Code, the guide documents ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN. Preserve unrelated settings, and keep a private copy of the configuration before editing it.

4. Check the requested model

Read the current provider model list and the client’s model mapping. A model name displayed in an interface may be an alias configured underneath. Avoid guessing a newer model identifier or copying an old screenshot’s identifier when the current documentation specifies something else.

5. Restart the client correctly

The Claude Code guide recommends closing its windows and starting a new command-line window after configuration changes. It also points to JSON syntax problems as a possible reason settings fail to apply. Validate sensitive configuration locally; do not upload a file containing your key to an online validator.

6. Try one small, ordinary request

Use a non-sensitive task that the tool is intended to support. Record the outcome and stop changing settings once you have a clear result. This is a recommended diagnostic step, not a request to run stress tests or repeatedly consume paid quota.

Distinguish plan quota from account balance

The FAQ says supported Coding Plan calls use the plan allowance and do not automatically charge the cash balance when that allowance runs out. It describes both five-hour and weekly limits. Check the subscription view for the actual allowance state rather than assuming every failure means the same reset window applies.

This distinction is important when assessing a top-up suggestion. A payment might increase one balance without repairing the client configuration or restoring a different allowance. Before spending anything, identify which product the failed operation belongs to and what limit the dashboard reports.

Write down the visible reset time and the time zone if one is shown. A support conversation is easier to follow when “it reset today” is replaced with a precise timestamp and the relevant allowance.

If chat works but an MCP tool fails

Z.ai documents vision, web-search and web-reader MCP tools separately within the plan FAQ. Treat a failure in one of these operations as its own case: record the tool name and error rather than replacing a working chat configuration immediately.

A useful isolation record has three rows: basic coding request, the failing feature and the client restart result. Mark each as passed, failed or not checked. This simple record avoids claiming the whole subscription is broken when only one integration was attempted. It also prevents a successful chat response from being treated as proof that every connected tool works.

What to send support if the checks do not resolve it

Prepare the client version, sanitized endpoint, model identifier, error code, timestamps and a description of the plan shown in your account. Include which of the six checks you completed and what changed. Share billing identifiers only through the provider’s private support channel when needed.

Do not send your API key, complete environment file, repository secrets or customer code. A sanitized configuration showing field names and a placeholder can explain the setup without exposing credentials. If support identifies an account-specific restriction, retain that reply with the troubleshooting record.

Resolve access before changing the purchase

If you are still choosing a plan, our GLM invitation and discount guide covers the existing referral route. It is not a workaround for a failed paid account. If your actual requirement is an app-building environment rather than a coding-model subscription, compare Base44’s separate building and running costs.

The useful outcome is a verified account, supported route and reproducible request. A changed error message or a successful response should be recorded as that specific result, not described as a universal fix for everyone who sees 1113.

Frequently asked questions