Skip to main content

Short answer

Do not rely on a static “currently available models” list. First confirm the exact model ID, endpoint, billing unit, and available groups on the console pricing page, then send a minimal request using the target API key. A model appearing in a list does not prove that every endpoint, parameter, SDK, or account group is compatible. Models, channels, endpoints, prices, rate limits, and routes may change for upstream, security, legal, commercial, or operational reasons. This page follows the LaoZhang API Terms and was last verified on September 2, 2026.

Four confirmation layers

1. Model ID

Copy the exact model ID from the model and pricing catalog or console. Do not construct an ID from a product name, nickname, or third-party article.

2. Endpoint and protocol

Confirm whether the model uses Chat Completions, Responses, Images, Embeddings, audio, asynchronous video tasks, or another endpoint. A /v1/models entry does not prove support for every protocol.

3. API key group and permission

The same model may be limited to a particular API key group, billing type, or account. Validate with a separate test key before using a production key. Contact the site owner or support for enterprise access, discounts, or special groups.

4. Minimal real request

Send a request with the smallest useful parameter set and record:
  • test date;
  • API key group;
  • endpoint and model;
  • request and key response fields;
  • expected and actual result;
  • charge, limitations, and untested scope.
An HTTP 200 response or model-list entry proves only that the particular request or list succeeded. It does not prove tool calling, streaming events, multimodal input, error behavior, or all parameters are compatible.

Common error classes

What to provide to support

  • account email or username;
  • model ID, endpoint, and API key group;
  • request time and time zone;
  • redacted error and request identifier;
  • minimal request and expected result;
  • screenshot of the console model or pricing page.
Do not send complete API keys, customer data, or unrelated request content.