API Errors & Troubleshooting

• Request content is incomplete or incorrectly formatted.
• The selected model, feature or setting does not support this request.
• Image, audio or video materials do not meet the requirements.

1. Send a short message without attachments to check whether a basic call works.
2. If it succeeds, add images, files or other features one at a time.
3. If it still fails, check the model and integration setup, or contact us.

• The key is incorrect or includes spaces or line breaks.
• The key has been deleted or disabled, or the client is still using old settings.
• Claude Code / CC Switch is not connected to LanoX as described in the integration guide.

1. Check the API key, base URL and selected provider again.
2. For Claude Code / CC Switch, use an API key created on the platform and set the base URL to https://api.lanox.ai, without /v1 or a trailing slash.
3. Save the settings, fully quit and reopen the client, then send a short message.

Use only when the full message confirms a LanoX key or integration issue. Do not change keys to try to fix upstream authentication failures.

• The personal account balance is insufficient.
• The shared enterprise balance is insufficient or the employee’s allocated budget is exhausted.
• The shared key has a separate quota limit.

1. Personal users: check your account balance.
2. Enterprise employees: check the enterprise balance, allocated budget and key quota.
3. Top up the relevant account, or ask your enterprise administrator to adjust employee budgets and key quotas.

Use only when the full message confirms insufficient LanoX balance, enterprise budget or key quota. Do not top up based solely on an upstream 402 or balance message.

• There is an issue with the account, enterprise, employee or key status.
• The current account does not have permission to use the selected model.

1. Check the account and key status.
2. Confirm that the selected model is available to this account.
3. Enterprise users should contact their administrator first. Contact us if the issue remains.

• The base URL is incorrect.
• The selected model is currently unavailable.
• The task is being queried with a different account or key, or the task ID is no longer valid.

1. Check the request URL against the integration guide.
2. Select an available model offered by the platform.
3. Check the task ID and the account or key used to create the task.

• The network or service is responding slowly.
• The generation task was submitted, but the client did not receive the response in time.

1. Try again later.
2. For image / video tasks, check task status and existing results first. Confirm that the task did not succeed before deciding whether to resubmit.

• The task has already been submitted, completed or moved to another state.
• An operation was repeated before the previous operation finished.

1. Check the existing task’s status first.
2. Confirm whether the task has already produced results before choosing the next action.
3. Do not simply resubmit the same task.

• Request conditions, model capabilities or the current task state do not meet the requirements.
• The full message may specify an issue with the content, attachments or other conditions.

1. If the message explicitly says the content is too large, reduce attachments or conversation history.
2. If the message is unclear or changes do not help, keep the full message and contact us.

• There are too many attachments or a file is too large.
• The conversation history is too long, with excessive irrelevant content or tool output.

1. Reduce the number of attachments, compress files or split them up.
2. Remove unnecessary conversation history and tool output.
3. Summarize the conversation or start a new one to reduce irrelevant context.

• The file extension or encoding format is unsupported.
• The submitted media format does not match the selected model’s capabilities.

1. Check the integration guide or page requirements for supported file and media formats.
2. Convert the file to a supported format before resubmitting. If needed, test a basic call with a short text message first.

• The input may violate safety policies.
• The input may be subject to copyright restrictions.
• Reference images or videos failed moderation.

1. Revise the input as directed by the message.
2. Use permitted reference materials and avoid restricted copyrighted content.
3. Before resubmitting, confirm that the materials meet the current model and platform rules.

• Too many calls failed within a short period.
• Concurrent requests exceed the allowed number.
• A low balance triggered a concurrency limit, or the model service is temporarily busy.

1. Pause repeated retries.
2. Close extra sessions and reduce concurrent tasks.
3. Check your balance. If calls were already failing, resolve the original error first.

• An error occurred during service processing.
• There is a temporary issue in model or task processing.

1. Keep a screenshot and the full error message, then try again later.
2. For image / video tasks or requests that have started producing output, check task status and existing results first.
3. Contact us if the issue persists.

• The connection to an upstream service failed.
• The model service is temporarily unreachable.

1. Keep the full error message and try again later.
2. For generation tasks, check existing results first to avoid duplicate submissions.
3. Contact us if the issue persists.

• The selected model is temporarily unavailable.
• The service is busy or not operating normally.

1. Contact us with the time of the issue, model name and full error message.
2. You can wait briefly or select another available model.
3. Do not retry continuously or repeatedly change keys.

• The service is taking too long to respond.
• Processing has started, but the client did not receive the result in time.

1. Keep the error message and try again later.
2. For image / video tasks, check existing results and task status first.
3. Contact us if the issue persists.