API domain migration: use api2.laozhang.ai

Published: July 23, 2026
Last verified: September 24, 2026
Status: Superseded. Since September 24, 2026, the default API domain is api.laozhang.ai. Servers in Europe or North America can connect directly through api-vip.laozhang.ai, and api2.laozhang.ai is the fallback when api.laozhang.ai can’t be reached. The API integration guide has the current setup; the rest of this page is the July 23 notice.

On some networks, the previous domain, api.laozhang.ai, can fail to resolve, fail to connect, or time out. If this happens, replace the request host with https://api2.laozhang.ai. Your API key, endpoint path, request parameters, and integration method do not change.

If requests fail to resolve, connect, or time out, switch to api2.laozhang.ai now. Do not disable HTTPS certificate verification, pin an unknown IP address, or use an untrusted DNS service to bypass the connection problem.

Which API domain should I use?

Domain	Status	Recommended use	Important limit
`api2.laozhang.ai`	Active and documentation default	Affected networks and general global traffic	Preferred for new integrations and migrations
`api-cf.laozhang.ai`	Active behind Cloudflare	Global fallback and normal synchronous requests	May return 524 if the origin does not respond within the default 120-second window
`api-vip.laozhang.ai`	Active direct route for Europe and North America	Europe/US users, non-CDN traffic, and long-running requests	No acceleration CDN; users in Asia may receive responses more slowly
`api.laozhang.ai`	Legacy compatibility domain	Europe/US servers where the legacy route still works normally	May fail to resolve or connect on some networks

The fallback and legacy rows describe the routes as announced on July 23, 2026.

How do I migrate?

Replace only the hostname. Keep the protocol, endpoint path, payload, and API key unchanged.

OpenAI-compatible API

Before:

https://api.laozhang.ai/v1/chat/completions

After:

https://api2.laozhang.ai/v1/chat/completions

Minimal request. Replace the placeholder with your LaoZhang API key:

export LAOZHANG_API_KEY="YOUR_LAOZHANG_API_KEY"

curl https://api2.laozhang.ai/v1/chat/completions \
  -H "Authorization: Bearer $LAOZHANG_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gemini-3.6-flash",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

Python SDK

Install the SDK with pip install openai, export LAOZHANG_API_KEY as above, then run:

import os

from openai import OpenAI

client = OpenAI(
    api_key=os.environ["LAOZHANG_API_KEY"],
    base_url="https://api2.laozhang.ai/v1",
)

response = client.chat.completions.create(
    model="gemini-3.6-flash",
    messages=[{"role": "user", "content": "Hello"}],
)
print(response.choices[0].message.content)

Environment variable

export OPENAI_BASE_URL="https://api2.laozhang.ai/v1"

For the Gemini native protocol, image APIs, video APIs, or balance queries, replace the domain in the same way:

https://api2.laozhang.ai/v1beta/models/{model}:generateContent
https://api2.laozhang.ai/v1/images/generations
https://api2.laozhang.ai/v1/videos
https://api2.laozhang.ai/api/user/self

The 120-second limit on the Cloudflare route

api-cf.laozhang.ai is proxied through Cloudflare. Cloudflare documents a default 120-second Proxy Read Timeout. If Cloudflare has connected to the origin but the origin does not respond within that period, the request may receive 524 A timeout occurred. This is not an API-key error and does not necessarily prove that the upstream task failed. For image, video, or complex agent requests that may run for a long time, prefer asynchronous tasks, polling, or streaming instead of one synchronous connection with no response data. api-vip.laozhang.ai connects directly to a server in Europe or the United States without an acceleration CDN, so Cloudflare’s default 120-second proxy read timeout does not apply. Client, origin, or other load-balancer timeouts may still apply.

Frequently asked questions

Do I need to create a new API key after changing the domain?

No. Your existing API key, model ID, endpoint path, request parameters, and billing account remain unchanged. Replace only the hostname in the request URL.

Must Europe/US servers migrate immediately?

No. Calls from Europe/US servers are theoretically unaffected and may continue using the legacy domain while it works normally. New projects and documentation use api2.laozhang.ai. If the legacy domain also fails from a Europe/US server, switch to api2.laozhang.ai or api-cf.laozhang.ai.

Can I access the console through `api2.laozhang.ai`?

Yes. Console, model-pricing, and account pages use api2.laozhang.ai; your account and sign-in details do not change.

Is 120 seconds a fixed total duration for `api-cf.laozhang.ai` requests?

More precisely, it is Cloudflare’s default read timeout to the origin. After the origin connection is established, Cloudflare may return 524 if it receives no response within about 120 seconds. Client, origin, load-balancer, and endpoint timeouts may also apply.

Which domain should I use for long-running requests?

Prefer asynchronous tasks, polling, or streaming. Europe/US users, or synchronous requests that need to avoid Cloudflare’s 120-second proxy read timeout, can use api-vip.laozhang.ai. Users in Asia should normally prefer api2.laozhang.ai, because the direct overseas route has no CDN acceleration and may respond more slowly.

Who should use `api-vip.laozhang.ai`?

The route is intended for servers in Europe or the United States, users who want a direct connection to the origin server, and requests that need to avoid Cloudflare’s proxy read timeout. It has no acceleration CDN, so network round trips and response delivery are usually slower from Asia; api2.laozhang.ai remains the preferred route for Asia and general use.

​Which API domain should I use?

​How do I migrate?

​OpenAI-compatible API

​Python SDK

​Environment variable

​The 120-second limit on the Cloudflare route

​Frequently asked questions

​Do I need to create a new API key after changing the domain?

​Must Europe/US servers migrate immediately?

​Can I access the console through api2.laozhang.ai?

​Is 120 seconds a fixed total duration for api-cf.laozhang.ai requests?

​Which domain should I use for long-running requests?

​Who should use api-vip.laozhang.ai?

​Related resources

Which API domain should I use?

How do I migrate?

OpenAI-compatible API

Python SDK

Environment variable

The 120-second limit on the Cloudflare route

Frequently asked questions

Do I need to create a new API key after changing the domain?

Must Europe/US servers migrate immediately?

Can I access the console through `api2.laozhang.ai`?

Is 120 seconds a fixed total duration for `api-cf.laozhang.ai` requests?

Which domain should I use for long-running requests?

Who should use `api-vip.laozhang.ai`?

Related resources