Skip to main content

​
Direct answer

Confirm the Claude model ID, API key group, and endpoint available to the current account in the model and pricing catalog. Use the Anthropic model catalog for official Claude IDs and capabilities; use the LaoZhang API console and call logs for gateway integration, groups, and billing. This page was last verified on September 2, 2026 and does not maintain a complete static model or upstream-pricing table that will quickly become stale.

​
Two protocol paths

​
Anthropic Messages-compatible entry point

Anthropic’s official Messages API uses structured messages, a required max_tokens, and a model ID. Whether the current LaoZhang API group exposes a native Messages-compatible route must be confirmed in the console, catalog, and a real request. Official contract: Create a Message

​
OpenAI-compatible entry point

Some Claude routes can be called through LaoZhang API’s Chat Completions compatibility layer:
This means the gateway translates protocols. It does not prove that Anthropic-native caching, thinking, tool, and error fields pass through unchanged.

​
Minimal OpenAI-compatible request

Copy the exact model ID from the console. Do not construct it from a product name, Bedrock ID, Vertex ID, or an old date pattern.

​
Capabilities that require validation

Official Anthropic support for a capability does not prove that every LaoZhang API Claude route passes it through. Record the API key group, endpoint, model, test date, and untested scope.

​
Model IDs and lifecycle

Anthropic documents different version patterns across model generations. A newer dateless ID can identify a fixed release, while an older short name can be an alias. Do not assume that every dateless ID automatically updates to the latest model. Production systems should:
  1. store the exact accepted model ID;
  2. monitor Anthropic deprecations and LaoZhang API announcements;
  3. test old and new models in parallel before migration;
  4. retain rollback configuration and call-log evidence.