GPT Image 2.5 quality auto reserves max on Sume: pin quality
Sume's image docs say quality auto reserves max, and auto size reserves the output token upper bound. What to set instead, plus the 1024 by 1024 figures.

On Sume's GPT Image 2.5 models, quality: auto reserves the max price, and auto size reserves the output token upper bound. If you know the tier you need, name it, and the amount held before the job runs gets smaller.
OpenAI's guide lists the quality values as low, medium, high, xhigh, max and auto. Sume defaults to high when the field is omitted.
What the docs state
Figures from Sume's Image API page, read 2026-10-03. Sume prices are before Sume's own pricing is applied, as the page says.
| Item | Value |
|---|---|
| Output image tokens | $30 per million |
| Input image tokens | $8 per million |
| Input text tokens | $5 per million |
| 1024 by 1024, xhigh output | $0.09366 before input tokens and Sume pricing |
| 1024 by 1024, max output | $0.21072 before input tokens and Sume pricing |
quality: auto | Reserves max |
auto size, or presets without a verified pixel mapping | Reserve the output token upper bound |
Omitted quality | Defaults to high |
What the hold means
Before a paid job runs, the platform reserves funds against its worst case. Sume's errors and credits docs cover what happens when a wallet cannot cover a request, so a large reservation matters most for small balances or many parallel jobs. The docs state the reservation rule for auto; they do not publish a hold amount for a given request, so read the live cost from the response rather than computing it here.
A request that pins quality
Setting quality removes the max reservation. For size, the docs allow custom pixels through image_size: both edges multiples of 16, a maximum edge of 3840, an aspect ratio of at most 3:1, and 655,360 to 8,294,400 pixels. The docs excerpt used here does not show the value's JSON shape, so read it from the model's catalog descriptor before sending one. The request below pins quality only.
import os, requests
body = {
"model": "openai/gpt-image-2.5",
"prompt": "a ceramic mug on a wooden desk, morning light",
"quality": "medium",
}
r = requests.post("https://api.sume.com/v1/images",
headers={"Authorization": "Bearer " + os.environ["SUME_API_KEY"]},
json=body, timeout=60)
print(r.status_code, r.json())Choosing a tier
A starting rule, not a benchmark.
- Drafts:
lowormedium. You are judging composition. - Finals:
high, the default, unless a close look shows a flaw that a higher tier fixes. xhighandmax: only after a side by side shows a visible gain on your content. The 1024 by 1024 figures above show max output costing more than twice xhigh.- Leave
autofor cases where you want the model to decide and your balance can carry the reservation.
Sources
Related posts
More in Pricing
- gpt-image-2.5 sync vs batch vs Sume: cost per 1,000 images
OpenAI bills gpt-image-2.5 output at $30 per 1M tokens, $15 in batch; Sume lists $0.2225 an image. A 1,000-image budget with the token inference.
- Grok Imagine: 20 MiB image cap and per-second prices
xAI lists Grok Imagine video at $0.020 to $0.080 a second and a 20 MiB image limit. On Sume, check the live catalog and add the x1.25 billing rule.
- Grok Imagine Image 2.0: auto means low, then medium
xAI's Grok Imagine Image 2.0 price list by quality, what auto resolves to, and how to read a model's price lines on Sume before you spend.
- Grok Imagine Video 1.5: cost of 10 seconds
At xAI's listed per-second rates, a 10-second Grok Imagine Video 1.5 clip costs $0.80 at 480p, $1.40 at 720p and $2.50 at 1080p. Check Sume's catalog prices.
Written by Sume