帮助支持

遇到问题时，先按这个顺序排除，大部分情况能自己定位：

1. 地址对不对 —— OpenAI 格式带 /v1，Anthropic 与 Gemini 原生不带。写错了通常报 404
2. Key 有没有问题 —— 是否完整复制、是否已删除或停用、余额是否充足。对应 401 与 402
3. 是不是限流 —— 看响应头 Retry-After，按指示等待即可。对应 429

When you hit a problem, rule these out in order — most issues can be traced this way:

1. Is the URL right — OpenAI-format endpoints include /v1; Anthropic and Gemini native endpoints don't. A mistake here usually means a 404
2. Is the key OK — was it copied completely, has it been deleted or disabled, is the balance sufficient? These map to 401 and 402
3. Are you being rate limited — check the Retry-After response header and wait as instructed. This maps to 429

写邮件到 [email protected]，附上这些信息能大幅缩短定位时间：

1. 请求的时间点与接口路径
2. HTTP 状态码与完整错误体
3. 响应头里的 Retry-After、request id 等标识
4. Key 名称（不要贴完整 Key）
5. 最小可复现的请求体

Email [email protected]. Including the details below shortens diagnosis considerably:

1. When the request happened and the endpoint path
2. The HTTP status code and the full error body
3. Identifiers from the response headers such as Retry-After and request id
4. The key name (never paste the full key)
5. The smallest request body that reproduces the issue