GPT Image revised_prompt: what a Sume images response returns
OpenAI returns revised_prompt on the image generation call. A Sume POST /v1/images response has data[].url and usage, with no revised prompt field.

OpenAI returns the rewritten prompt in a revised_prompt field on the image generation call. A Sume POST /v1/images response has no such field: it returns data[].url, media_type and a usage object, so log the prompt you sent if you need to know what produced an image.
OpenAI facts are from its image generation guide; Sume facts from Image generation, both read 2026-10-01.
Where does OpenAI put the revised prompt?
In the guide's "Revised prompt" section, the mainline model revises your prompt when you use the image generation tool in the Responses API. You read the result from the revised_prompt field of the image generation call. The guide's example shows a descriptive sentence about a gray tabby cat hugging an otter.
What does a Sume images response contain?
The Sume docs say images "return as Sume-hosted URLs with usage data". The fields are below.
| Field | What the docs say |
|---|---|
created | Unix timestamp of the response |
model | Echoes the id you requested; sume/auto stays sume/auto |
data[].url | Sume-hosted, signed URL rather than inline base64 |
data[].media_type | For example image/png or image/webp |
usage | Token counts are 0 in v1; cost is the USD billed to your wallet |
Does Sume rewrite my prompt at all?
The docs describe prompt as a text description of the desired image and list no field that reports a rewritten version. They do not state whether any model rewrites the prompt internally, so do not assume either way. What the response gives you is the generated image URL and the billed cost.
How do I keep an audit trail of prompts?
Store the prompt string next to the returned data[].url in your own records. The request also accepts a metadata object that the docs say is stored on the job and not sent to the provider, which is a place to keep your own prompt id or template name. For related behavior on long requests, see how a long image request becomes a job.
Sources
Related posts
More in Developers
- GPT Image user error: don't retry unchanged; Sume failures unbilled
OpenAI says not to auto-retry image_generation_user_error without changing the prompt or inputs. On Sume, retry 429 with backoff; failed images are not billed.
- gpt-transcribe expected languages vs Sume STT language_code
OpenAI's gpt-transcribe accepts multiple expected input languages. Sume STT takes one optional language_code hint or auto-detect. What to send for mixed audio.
- Grok Imagine base64 response_format vs a Sume hosted URL
xAI lets you request base64 instead of a temporary URL. Sume returns Sume-hosted, signed URLs in data[].url, not inline base64, for x-ai/grok-image.
- HeyGen 429 Retry-After vs Sume rate_limited and queue_full
HeyGen sends 429 with a Retry-After header in seconds. Sume sends 429 rate_limited with retry-after when present, and a separate 429 queue_full.
Written by Sume