401: authentication; 429: request limits

HTTP 401 means the request lacks valid authentication credentials. Check the base URL, Authorization format, key validity, and account. HTTP 429 means too many requests. Read the service’s limits and Retry-After header when provided, reduce concurrency, and back off rather than retrying continuously.

503: availability and retry safety

HTTP 503 indicates temporary service unavailability, such as maintenance or overload. Use the response and service status to investigate the actual cause. Before retrying a generation request, check whether a task was already created to avoid duplicate charges. Share a redacted timestamp, request ID, status code, and error summary when seeking help, never a full key.

TAKE THIS CHECKLIST WITH YOU

A few things to check next.

  • ✓Record redacted codes and request IDs
  • ✓Handle the cause instead of retrying forever
  • ✓Check task state before resubmitting

Sources and scope

This is workflow guidance and pre-use information. Platform entry points and model information were reviewed on public pages. No generation, payment, or integration acceptance was performed for you. Platform names, channel labels, and parameters do not establish original-provider identity or endorsement.

MDN · HTTP response status codes ↗