xZI 1.0 Pro

REQUIRED. Email of YOUR real end-user inside your product — the person who actually triggered this generation. We use it to attribute every request and give you a chain of responsibility: you can list, audit, and delete that user's generations. Do NOT pass a fake address, a shared placeholder, or someone else's email — that's a policy violation. If an end-user generates disallowed content and you do not act, your account can be suspended (see Acceptable use).

Example: "alice@your-product.com"

Public model alias. Required — pass `xZI1.0Pro` to use this model.

Example: "xZI1.0Pro"

Text prompt describing the image: subject and action first, then setting, then style, lighting and composition.

Example: "A cinematic portrait of an astronaut standing in a field of wildflowers at golden hour"

Output dimensions: preset `1K` or `2K`, or explicit pixels `WxH` with **each side between 256 and 2560** (e.g. `1440x2560` for a tall 9:16, `2560x1080` for an ultrawide banner). Anything outside that window is rejected with `400 validation_error` before any debit. A preset is always resolved to explicit pixels before generation — see `aspectRatio` for which shape you get. The price is the same for every size.

Example: "1440x2560"

Shape of a preset `size`: `square` (1:1), `landscape` (16:9), `portrait` (3:4). `auto` resolves to the square shape of the chosen preset, because this model is always sent explicit pixels. The exact dimensions behind a preset are not a fixed contract; pass an explicit `WxH` to pin them (an explicit size wins and `aspectRatio` is then ignored).

Example: "landscape"

Images per request. This model produces exactly one, so only `1` is accepted; send several requests for several images.

Example: 1

Determinism seed. Same seed + same prompt + same size + same other params = same output. If omitted, the server picks a random seed for you and returns it in `GET /v1/generations/:requestId` (`input.seed`), so any generation can be reproduced after the fact. Pass a value of 1 or more to reproduce: `0` asks the model to pick a random seed of its own. With `promptExtend: true` the prompt is rewritten before generation and the rewrite differs between runs, so the same seed no longer guarantees the same image.

Example: 42

Let the model rewrite your prompt into a longer, more detailed one before generating. Off by default. It usually helps short prompts and gets in the way of carefully written ones — the prompt that runs is not the prompt you sent. With this on, the same seed no longer guarantees the same image.

Example: true

How images are returned. Only "url" is supported — signed CDN URLs valid for 23 hours. "b64_json" is rejected with `400 validation_error` before any debit; download from the returned URL instead.

Not supported by this model — it produces one independent image. Passing `"auto"` is rejected with `400 validation_error` before any debit.

Not accepted — this model is text-to-image only. Any value is rejected with `400 validation_error` before any debit, rather than silently ignored.

Optional public HTTPS URL we will POST the final record to once the generation is succeeded or failed. The body is identical to what GET /v1/generations/:requestId returns. Each delivery is HMAC-signed (`X-XMode-Signature: v1=<hex>`) and timestamped (`X-XMode-Timestamp`); reject anything older than 5 minutes. Private/loopback IPs are refused (SSRF guard). See the Webhook delivery section in the Introduction for verification code.

Example: "https://your-app.example.com/hooks/xmode"

Unique id of the generation. Use it with GET /v1/generations/:requestId to poll.

Public alias of the model that will produce the images.

Lifecycle marker. POST always returns `queued`. GET returns the current state. `expired` means the request succeeded more than 23 hours ago and signed URLs no longer work — re-run if you need the images again.

Present on `queued` responses only. Absolute URL to GET for status. Recommended polling cadence: every 5 seconds until terminal.

Present only when status=`succeeded`. Holds one item with `id`, `expiresAt`, and EITHER `url` (signed, valid 23 h, PNG) OR `error: { code: "storage_failed" }` if our storage layer dropped the image — in which case there is nothing to deliver and the request comes back `failed` and refunded instead. The URL is re-signed on every read, but that never moves `expiresAt`, which is fixed when the generation completed. Once it passes, the record returns status `expired` with no URL and the bytes are gone.

Present only when status=`failed`. `{ code, message }`. The same code values as the top-level error format (validation_error, content_policy, provider_error, provider_timeout, internal_error).

Present only when status=`succeeded`. `{ xTokens: number }`. Debited at request time; refunded automatically on `failed`.

Present on terminal statuses (`succeeded`, `failed`, `expired`). When the generation reached its final state.

Echoed back so you can confirm the grouping. Always lowercase.

When the request was accepted (POST time).