Z-Image Turbo API

What Z-Image Turbo does

Call Z-Image Turbo through one strict image API for posters, product visuals, and social creative. Aspect ratio is required and every request returns exactly one image.

• Built for text-rich visuals — Combines Chinese and English headlines, short copy, and imagery for posters, covers, menus, campaigns, and product creative.
• Five explicit canvas ratios — Choose 1:1, 4:3, 3:4, 16:9, or 9:16 directly, without ambiguous pixel-size conversion across publishing channels.

Z-Image Turbo API features

• Strict request contract — Accepts only model, prompt, aspect_ratio, and optional nsfw_checker; unsupported fields return a clear error.
• Synchronous OpenAI-style response — POST to /v1/images/generations and read the result from data[0].url without task polling.
• Predictable single-image billing — Each call generates one image and is billed only after success, making costs easy to forecast.
• Controllable content check — nsfw_checker is a real boolean; an explicit false value is preserved end to end.

What people build with Z-Image Turbo

• Bilingual posters and campaigns — Generate campaign posters, launch graphics, and social assets with Chinese and English headlines.
• Commerce and menu creative — Create product hero images, promotional banners, menu covers, and offer graphics.
• Editorial cover pipelines — Produce consistent-ratio covers for articles, videos, podcasts, and editorial series.

Getting started with the Z-Image Turbo API

The endpoint is OpenAI-compatible, so existing client code usually needs only a base URL and a model name.

• Step 1: Create an API token — Create a token with access to the qwen-A group.
• Step 2: Write the prompt — Describe subject, scene, lighting, style, and visible text in up to 1000 characters.
• Step 3: Choose an aspect ratio — Choose one of the five supported values and send it as top-level aspect_ratio.
• Step 4: Read the image URL — The generated result is returned in data[0].url.

Z-Image Turbo API pricing

Z-Image Turbo — $0.014493 per image, failed requests are not billed

• Unified auth and billing — Share one CCAPI token, usage history, and balance with the rest of your models.
• Fail fast on bad fields — The gateway validates fields before billing or upstream submission, avoiding silently ignored options.
• Playground mirrors the API — The playground exposes only production-supported fields, so its request can be copied directly into an integration.

Frequently asked questions