Skip to main content
API preview: generation providers are not connected. An authenticated request can return 503 without creating a task or charging credits.

Handle the cause, not just HTTP status

One operation, one idempotency key

Use one stable Idempotency-Key for recovery of a particular request. The fingerprint includes model, normalized input, output_count, fallback, and max_credits. The same key with different business input is a conflict. Idempotency keys are not API credentials. They prevent duplicate business acceptance, not unauthorized access. A user-requested regeneration is a new operation with a new key.

Give support a traceable ID

Keep request_id, task_id, item_id, timestamp, and a sanitized error. Never send full API keys or provider credentials. Logs show the operation, each result item, its attempts, and the credit outcome. Open logs Get help