Adobe image API · Site 2 #127【YYY】4k Image 2.0 (Med) 4K image2.5 flare / sunburst

English translation. Model names, API fields and executable examples retain their original text, including prompts and comments.

Tip

New to the API? Start with the tutorial. Complete Your first image edit first, then return here for #127 Adobe parameters, aspect ratios and full examples.

Important

Start with a single-image baseline: gpt-image-2, size="1536x864", quality="medium", n=1. Use the corresponding API key when switching groups. Do not apply Grok's resolution/aspect_ratio rules directly to this group.

Group: 【YYY】4k Image 2.0 (Med) 4K image2.5 flare / sunburst. Updated: 2026-09-15.

• Base URL：https://yyds.seqnode.com/v1
• Authentication: Authorization: Bearer YOUR_GROUP_127_API_KEY
• Use the API key for #127【YYY】4k Image 2.0 (Med) 4K image2.5 flare / sunburst. These three names identify separate upstream models. They are not the same-name aliases in #75【YYY】image 2.0 1k (2k/4k upscaling) or #77【YYY】image 2.0 2.5 1k (integration, no upscaling).

1. Models and pricing

All three models are billed per image. Within this group, each model currently has one per-image price across resolutions. The table shows 1x retail prices, not upstream costs. Account-specific discounts are reflected in your actual bill. Official token prices displayed elsewhere are not these per-image prices.

2. Reference images, sizes and ratios

Number of reference images

These results reflect the channels tested on 2026-09-15. Intermediate counts such as 4–5 were not tested individually. We inspected the 10-reference Image 2 output and 6-reference Flare / Sunburst outputs: all numbered color cards appeared. This does not guarantee preservation of every complex reference. Flare returned 502 for 7, 8 and 15 references, followed by some 503 responses; these errors do not establish its image-count limit.

• JSON image editing: use images as an array of objects, each containing {"image_url":"图片URL或data URL"}. PNG Base64, two HTTPS references and two multipart references were verified for all three models.
• Local files: use multipart and repeat the image field. A top-level JSON image field is not equivalent.
• Image encoding: PNG is verified; see the parameter table for mixed JPEG / WebP references. Each multipart file must be strictly below 20 MiB. These tests used small files and did not verify the file-size boundary; gateway and upstream limits also apply to the entire request.
• URLs must download images directly. Base64 examples include a data:image/png;base64,, data:image/jpeg;base64, or data:image/webp;base64, prefix.
• JSON forms verified to return 400: images: [], images: ["URL"], top-level image, images[].file_id, and string-valued n: "1". n must be a number.
• n is the number of output images; the number of reference images is the length of the images array.

Image sizes and aspect ratios

Start with 16:9、9:16 and request 3840x2160 or 2160x3840. For a basic call, express the aspect ratio through size without additionally sending aspect_ratio.

This table contains common request templates, not a support allowlist exhaustively verified for all three models. Test other ratios, such as 3:1, 1:3, 21:9, 9:21, 5:4 and 4:5, with a small number of requests at your target dimensions. A complete upstream size allowlist or common maximum pixel count has not been confirmed.

size accepts positive integer pixel dimensions, for example 3840x2160, separated by a lowercase x. Do not infer actual output dimensions from the group's “4K” name alone.

Two-reference test results: All three were size="3840x2160", quality="medium", n=1 JSON editing requests and returned HTTP 200.

About actual dimensions: This Adobe group is not bound to the site's local upscaling proxy. The upstream may adjust dimensions. Inspect the image file before delivery, rather than relying on HTTP 200 or the 4K billing tier. The table confirms successful 4K requests; reference-image limits follow the latest boundary tests on this page. Not all aspect ratios were tested individually.

3. Request parameters

The three models use the same request structure, but some parameters behave differently. The table below lists confirmed JSON /v1/images/edits results. Text-to-image uses the basic structure in the examples below.

Basic examples explicitly set quality="medium". HTTP 200 confirms request success only; it does not prove that every supplied field took effect. seed, mask, background, output_compression, moderation, input_fidelity, style, partial_images, streaming responses and output_format="webp" are outside the currently confirmed range.

Full test records: Parameter verification results (Chinese source). Errors and retests are included; 502 / 503 responses were not simplified into “unsupported parameter”.

Recommended request configuration

Read the delivered file format and dimensions. Flare and Sunburst may adjust requested dimensions. quality="high" and multiple outputs are outside the confirmed range.

4. Request examples

Text to image: a payload for each model

Choose one example and save it as request.json. Each example requests one landscape image.

gpt-image-2 · $0.025/image

{
  "model": "gpt-image-2",
  "prompt": "白色陶瓷杯放在木桌上，柔和自然光，无文字",
  "size": "3840x2160",
  "quality": "medium",
  "n": 1,
  "response_format": "b64_json"
}

gpt-image-2.5-flare · $0.05/image

{
  "model": "gpt-image-2.5-flare",
  "prompt": "白色陶瓷杯放在木桌上，柔和自然光，无文字",
  "size": "3840x2160",
  "quality": "medium",
  "n": 1,
  "response_format": "b64_json"
}

gpt-image-2.5-sunburst · $0.08/image

{
  "model": "gpt-image-2.5-sunburst",
  "prompt": "白色陶瓷杯放在木桌上，柔和自然光，无文字",
  "size": "3840x2160",
  "quality": "medium",
  "n": 1,
  "response_format": "b64_json"
}

Send the request （Bash / WSL）：

export YM2API_KEY="YOUR_GROUP_127_API_KEY"

curl --max-time 300 "https://yyds.seqnode.com/v1/images/generations" \
  -H "Authorization: Bearer $YM2API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @request.json \
  -o response.json

Image editing: two local references

Use the structure below for all three models, changing only MODEL. For one reference, remove the second image field.

export YM2API_KEY="YOUR_GROUP_127_API_KEY"
MODEL="gpt-image-2.5-flare"
# MODEL 也可填写 gpt-image-2 或 gpt-image-2.5-sunburst

curl --max-time 300 "https://yyds.seqnode.com/v1/images/edits" \
  -H "Authorization: Bearer $YM2API_KEY" \
  -F "model=$MODEL" \
  -F "prompt=保留图1的主体，采用图2的配色，白色背景，无文字" \
  -F "image=@reference-1.png" \
  -F "image=@reference-2.png" \
  -F "size=3840x2160" \
  -F "quality=medium" \
  -F "n=1" \
  -F "response_format=b64_json" \
  -o response.json

Let cURL generate the multipart headers; do not manually set Content-Type.

Image editing: URL / Base64 references

Save the following as edit.json and replace the model name and both reference images:

{
  "model": "gpt-image-2.5-sunburst",
  "prompt": "保留图1的主体，采用图2的配色，白色背景，无文字",
  "images": [
    {"image_url": "https://YOUR_IMAGE_HOST/reference-1.png"},
    {"image_url": "data:image/png;base64,YOUR_REFERENCE_2_BASE64"}
  ],
  "size": "3840x2160",
  "quality": "medium",
  "n": 1,
  "response_format": "b64_json"
}

curl --max-time 300 "https://yyds.seqnode.com/v1/images/edits" \
  -H "Authorization: Bearer $YM2API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @edit.json \
  -o response.json

Responses

{
  "created": 1789380000,
  "data": [{"b64_json": "BASE64_IMAGE_BYTES"}]
}

Decode data[].b64_json and save the image. If you choose url, read data[].url and download promptly. Use the actual image encoding to choose the file extension: Image 2 still returned PNG when JPEG was requested. Check usage after a timeout before resubmitting.

To list models available to the current key, call GET https://yyds.seqnode.com/v1/models with the same authentication header.