Overview
Seedream 5.0 is a ByteDance image generation model for text-to-image creation and reference-guided image generation. It supports 2K and 3K output presets, optional web search, selectable output format, and flexiblesize input for callers who prefer explicit dimensions.
Endpoint and authentication
Base URL:
All requests require your APIXO API key:
Copy-paste async quickstart
This minimal request submits a text-to-image task and returns ataskId.
taskId; you need it to poll for the final result.
Poll for result
Request body
Text-to-image
Image-to-image
Explicit size
Parameters
string
default:"async"
Result delivery mode. Use
async for polling with statusTask, or callback for webhook delivery.string
Required when
request_type is callback. Must be a public HTTPS URL that can receive the final task payload. See Webhooks.object
required
Seedream 5.0 input parameters.
Size presets from resolution + aspect_ratio
When aspect_ratio is provided, Seedream 5.0 maps resolution and aspect_ratio to these output dimensions:
Response format
Submit task response
POST /generateTask/seedream-5-0 returns a task ID when the task is accepted:
integer
API status code.
200 means the task was accepted.string
Human-readable status message.
string
Task identifier used for later polling or webhook matching.
Polling and delivery guidance
Seedream 5.0 tasks are asynchronous.
For production systems, prefer
callback_url instead of tight polling loops.
Billing
New non-LLM requests use 1 credit =$0.001. Calculate the full amount, including billable quantity and add-ons, apply the applicable account discount, then round the request total upward to the next whole credit. Agreed fixed unit prices retain their precision and replace the standard price and discount; final rounding still applies. See credit conversion and rounding.
Seedream 5.0 is billed per generated image. The current public APIXO price is a single flat rate for this model.
Billing behavior:
MCP integration
The complete model schema declares result decoding inmcp.result and supported file bindings in mcp.attachments. These are client integration metadata, not generation input parameters. Attachment paths: image_urls. Preserve the user’s file order. Model parameter validation remains on the API.