Skip to main content
The model and pricing catalog lists public model IDs, endpoints, and prices. To confirm that a model works for you, check that your token group can use it on the console pricing page, then send a minimal request with that token. A model appearing in a list does not prove that every endpoint, parameter, SDK, or token group is compatible. Based on the LaoZhang API Terms, last verified September 2, 2026.

​
Four confirmation layers

​
1. Model ID

Copy the exact model ID from the model and pricing catalog or the 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, pricing, or special groups.

​
4. Minimal real request

Send a request with the smallest useful set of parameters, then check that:
  • the response contains the output you expect, such as text, an image, or a task ID;
  • the call log shows the model and token group you intended;
  • the charge matches the price shown in the console;
  • each feature you rely on, such as streaming, tool calls, or image input, works in its own small request.
An HTTP 200 response or model-list entry proves only that the particular request or list succeeded. It does not prove that 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.