API Reference

Image Generation

Image Generation

POST https://api.tu-zi.com/v1/images/generations
Preview guide

Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.

Preview guide

Image Generation

Updated · Reviewed

Endpoint and authentication

POST https://api.tu-zi.com/v1/images/generations

Transport: json

Use an inference API key. Examples contain placeholders; read credentials from environment variables.

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Minimal request example

{
  "model": "YOUR_MODEL",
  "prompt": "A white ceramic cup"
}

Before running

Replace https://api.tu-zi.com with this site origin (do not append /v1 twice), and YOUR_MODEL with the exact marketplace model ID. Install requests for Python; use Node.js 20+ and save JavaScript as .mjs. WebSocket samples list their own dependencies.

Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.

Start with a minimal request, then read the result using the response fields below. For async APIs, a returned task ID requires polling; acceptance does not mean generation has finished.

Constraints

This page describes the base protocol. Use the selected model quick start for supported fields, enums, limits and asynchronous behavior. Replace YOUR_MODEL. Form initial values are not upstream defaults. Inspect every item in data[]: url is an image download URL; b64_json is Base64-encoded image bytes to decode and save, not a URL. Handle either form. HTTP 200, empty data[] or text alone does not prove image generation succeeded. Do not send the site API key when downloading result URLs. Save and validate the actual image format/MIME; renaming an extension does not convert an image.

Body parameters

FieldTypeRequiredDescription / constraints
modelstringYesImage model identifier. Example: gpt-image-1
promptstringYesImage generation prompt. Example: 极简产品摄影,白色陶瓷咖啡杯放在浅色木桌上,柔和自然窗光,干净背景,细节清晰
sizestringNoOutput dimensions, for example 1024x1024. Form initial value (not an upstream default): "1024x1024" Values: "1024x1024", "1536x1024", "1024x1536", "512x512", "256x256" Example: 1024x1024
nnumberNoNumber of images to generate. Form initial value (not an upstream default): 1 Range in this definition: 1 ~ 10 Example: 1
qualitystringNoImage quality setting. Form initial value (not an upstream default): "standard" Values: "standard", "hd", "auto" Example: standard
response_formatstringNoImage response format, typically url or b64_json. Form initial value (not an upstream default): "url" Values: "url", "b64_json" Example: url
stylestringNoImage style: vivid or natural, where supported. Values: "vivid", "natural" Example: vivid
backgroundstringNoBackground mode; transparent requests transparency where supported. Values: "auto", "transparent", "opaque" Example: auto

Response fields

FieldTypeDescription / constraints
data[].urlstringImage URL in URL output mode.
data[].b64_jsonstringBase64 image when that output mode is supported.

Illustrative response; some endpoints show essential fields only. Optional fields may be absent.

{
  "created": 1793491200,
  "data": [
    {
      "url": "https://example.com/result.png"
    }
  ]
}

Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.

Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.