Skip to main content

​
Short answer

Open the call logs page and locate a request by time, model, status, or other filters currently available in the console. Call logs are primarily used to review billing, routing, error categories, and request status. LaoZhang API does not store API prompts or responses by default. This page follows the LaoZhang API Data Policy and was last verified on September 2, 2026. Console fields and filters may change; use the current interface as the source of truth.

​
What logs may contain

Under the Data Policy, request metadata may include:
  • account or API key identifier;
  • timestamp, model, endpoint, and route;
  • token, usage amount, or billing unit;
  • request status and error category;
  • latency and routing information;
  • information required for security, abuse prevention, and service integrity.

​
What is not stored by default

LaoZhang API does not store API prompts or responses by default. Upstream model and infrastructure providers may apply their own logging, retention, and safety-review rules. Those upstream boundaries cannot be inferred from the LaoZhang API call log alone.

​
Retention

Troubleshooting logs are generally retained for 7 days. Relevant metadata may be retained longer where reasonably necessary for security, abuse investigation, billing disputes, legal compliance, or service integrity. Billing records, transaction records, account and security events, and support materials follow separate retention purposes described in the Data Policy.

​
Troubleshooting a failed call

  1. Record the exact failure time and time zone.
  2. Confirm the model ID, endpoint, and API key group.
  3. Review the HTTP status, platform error, and whether usage was charged.
  4. Reproduce with a minimal request to separate parameter, permission, balance, route, and upstream errors.
  5. If unresolved, send redacted evidence to support.
Provide:
  • account email or username;
  • request time and time zone;
  • model ID, endpoint, and token group;
  • HTTP status, error category, and redacted error text;
  • a console request identifier that support can use for investigation;
  • retry attempts and results.
Do not send complete API keys, passwords, full prompts or responses, regulated data, or unrelated customer information. Do not assume that a public call-log API exists unless it is documented in the current official API reference or console.