Retries, idempotency, and request IDs

• GET requests may be retried after a connection failure or timeout with exponential backoff and random jitter.
• When retrying an AI POST, reuse the same UUID Idempotency-Key for the same business operation.
• For 429, honor Retry-After when present and reduce concurrency. 401, 403, and insufficient balance are not transient.
• A 5xx or dropped connection can have an uncertain result. Retry only with a defined idempotency policy, maximum attempts, and total deadline.

You may send a UUID X-Request-Id for each business request. The platform also returns a request ID. Give support only this ID, the time, and a safe error code—not the request or response body.