API Documentation

Quick Start

Base URL

Both hosts serve the same API with the same key, interchangeable at any time. We recommend the first host: every generation endpoint (image, video, audio and LLM) is served directly by our origin servers, with request bodies up to 100MB. The second host remains fully supported but caps request bodies at ~4.5MB (413 beyond) — large images and base64 payloads will hit that ceiling.

Setting base_url in an SDK

base_url is the root only. Do not paste a full endpoint (…/v1/messages, …/v1/images/generations) into it — your SDK appends its own path on top, and the request ends up at something like /v1/messages/chat/completions, which does not exist. The ENDPOINT values in the examples on this site are full endpoints meant for curl; for an SDK use one of the two roots above.

Authentication

All API requests require a Bearer token in the Authorization header:

Authorization: Bearer YOUR_API_KEY

HTTP Error Codes (sync request)

Generation Failure Codes (async task)

When an async task fails, the query returns state="failed" with a standardized failCode, a human-readable failMsg, and a boolean retryable — so your client can decide between "retry / switch model" and "fix the prompt / input / top up".