Seedream 5.0 Pro
Seedream 5.0 Pro is an image generation and editing model supporting text-to-image, one to ten reference images, 1K and 2K tiers, and exact output dimensions. It is suited to product visuals, advertising assets, concept design, image editing, and automated creative workflows that need repeatable API access. Use the playground below to test representative prompts, reference images, dimensions, quality settings, output formats, and image counts that are available for this model. Before production rollout, compare visual quality, instruction following, subject consistency, processing time, failure handling, and estimated cost with your actual workload. The controls shown on this page describe the currently supported integration options.
- Model ID
- seedream-5.0-pro
- Provider
- ByteDance
- API endpoint
- /v1/images/generations
- Pricing
- 0.002941176471
- Last updated
- 2026-08-13
Capabilities
- Image generation through the current public endpoint
- Editing or reference-image controls when exposed by the live schema
- Current parameters including prompt, image, size
Limitations
- Capabilities and parameter ranges can change; pin and validate the parameter set used in production
- Do not assume support for parameters absent from the live request schema
- Asynchronous jobs require explicit polling, failure, timeout, and safety-status handling
Use cases
- Product prototypes and automated content workflows
- Batch media generation and programmatic creative tooling
- Multi-model applications that need unified authentication, billing, and usage records
Pricing and billing examples
- image_input | 0.002941176471 | input_images
- image_output_high | 0.088235294118 | output_images | {"output_image_pixels":{"gt":2360000}}
- image_output_low | 0.044117647059 | output_images | {"output_image_pixels":{"lte":2360000}}
Request parameters
| Parameter | Type | Required | Default | Options |
|---|---|---|---|---|
| model | string | Yes | ||
| prompt | textarea | Yes | ||
| image | asset_list | No | ||
| size | size | Yes | 2K | 1K, 2K |
| aspect_ratio | select | No | 16:9 | 1:1, 4:3, 3:4, 16:9, 9:16, 3:2, 2:3, 21:9 |
| output_format | select | No | jpeg | jpeg, png |
| response_format | select | No | url | url, b64_json |
| watermark | boolean | No | true |
API examples
cURL
curl -X POST 'https://api.uniall.ai/v1/images/generations' \
-H 'Authorization: Bearer $UNIALL_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"aspect_ratio":"16:9","model":"seedream-5.0-pro","output_format":"jpeg","prompt":"Describe the output you want","response_format":"url","size":"2K","watermark":true}'Python
import json
import requests
payload = json.loads(r'''{"aspect_ratio":"16:9","model":"seedream-5.0-pro","output_format":"jpeg","prompt":"Describe the output you want","response_format":"url","size":"2K","watermark":true}''')
response = requests.post(
"https://api.uniall.ai/v1/images/generations",
headers={"Authorization": "Bearer " + UNIALL_API_KEY},
json=payload,
)
response.raise_for_status()
result = response.json()JavaScript
const response = await fetch("https://api.uniall.ai/v1/images/generations", {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.UNIALL_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({"aspect_ratio":"16:9","model":"seedream-5.0-pro","output_format":"jpeg","prompt":"Describe the output you want","response_format":"url","size":"2K","watermark":true}),
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const result = await response.json();Frequently asked questions
What API endpoint does seedream-5.0-pro use?
The endpoint is resolved from the current model capabilities and request schema and shown on this page.
How is seedream-5.0-pro priced?
The pricing section reads the current structured billing configuration, so editorial text does not need a rewrite after a price change.
Can I use Python?
Yes. The example uses the current endpoint and exact model identifier.
Are JavaScript and cURL examples included?
Yes. All examples share the same live request structure.
Which resolution, duration, or reference-image controls are supported?
Supported controls come from the current request schema. Do not assume fields that are not listed.
What should I validate before production use?
Validate parameters, timeouts, error handling, and asynchronous generation status behavior after model updates.