> For the complete documentation index, see [llms.txt](https://bountyv.gitbook.io/vdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bountyv.gitbook.io/vdocs/frontier-passthrough/frontier-seedream-5-pro.md).

# Seedream 5 Pro

BytePlus ModelArk's newest image model. Same API shape as [Seedream 4.x](/vdocs/frontier-passthrough/frontier-seedream.md), higher quality, higher price.

```
POST /api/v1/frontier/seedream-5-pro
```

## Authentication

```
Authorization: Bearer sk_live_...
```

## Request

**Content-Type:** `application/json`

Identical to [Seedream 4.x](/vdocs/frontier-passthrough/frontier-seedream.md):

| Field       | Type      | Required | Default | Description                                                                         |
| ----------- | --------- | -------- | ------- | ----------------------------------------------------------------------------------- |
| `prompt`    | string    | ✅        | —       | What to generate                                                                    |
| `images`    | string\[] | —        | —       | Up to 10 references, in prompt order. `data:` URL, public https URL, or bare base64 |
| `image`     | string    | —        | —       | Single reference, same formats                                                      |
| `size`      | string    | —        | `"2K"`  | `"1K"` \| `"2K"` \| `"4K"`                                                          |
| `count`     | integer   | —        | `1`     | Sequential-set mode. References + generated ≤ 15                                    |
| `watermark` | boolean   | —        | `false` | Provider watermark                                                                  |

## Response

Same shape as [Seedream 4.x](/vdocs/frontier-passthrough/frontier-seedream.md#response), with `"model": "Seedream 5 Pro"`.

## Example

```bash
curl -X POST https://substance-api.com/api/v1/frontier/seedream-5-pro \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Editorial fashion photograph, backlit, 85mm, muted palette",
    "size": "4K"
  }'
```

## Errors

Same as [Seedream 4.x](/vdocs/frontier-passthrough/frontier-seedream.md#errors), plus:

| Status | Meaning                                                               |
| ------ | --------------------------------------------------------------------- |
| `503`  | Seedream 5 Pro isn't available on this deployment. Nothing is charged |

## Pricing

$0.49 **per output image**. Seedream 5 Pro costs roughly 3× what 4.x does upstream (it's priced by output pixels), which is why it carries its own rate rather than sharing the 4.x one. Bills on `images.txt2img.seedream5`. See [Credits & pricing](/vdocs/account/credits.md).

SFW only — see [Frontier Passthrough → Content policy](/vdocs/frontier-passthrough/frontier-overview.md#content-policy).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bountyv.gitbook.io/vdocs/frontier-passthrough/frontier-seedream-5-pro.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.