gpt-image

GPT Image 2.5 (via DroidProxy Codex)

POST http://localhost:8317/v1/images/generations (or /edits) with Authorization: Bearer dummy-not-used. Send only gpt-image-2.5-flare or gpt-image-2.5-sunburst. Never send an older image model, a dated snapshot, or a chat id (gpt-* without image). Never use an OPENAI_API_KEY. Chat models on :8317 do not generate images.

Default to Flare for fast, high-quality everyday generation. Use Sunburst when the user prioritizes demanding quality, editing precision, or subject preservation over latency. If Sunburst meets the requirements, prefer Flare only after it produces acceptable results on the same prompt, references, dimensions, and quality setting.

Use this for generating or editing visual assets, not for understanding an image the user already attached.

Generate

Requests often take 15–70s. Use --max-time 180. Default quality to auto; select a higher explicit setting only to meet a quality requirement.

RESP=$(curl -sS --max-time 180 http://localhost:8317/v1/images/generations \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer dummy-not-used" \
  -d "$(jq -n --arg p "A red balloon on a wooden table, soft natural light" \
    '{model:"gpt-image-2.5-flare", prompt:$p, size:"1024x1024",
      quality:"auto"}')")

if B64=$(printf '%s' "$RESP" | jq -er '.data[0].b64_json' 2>/dev/null); then
  printf '%s' "$B64" | base64 -d > out.png
else
  printf '%s\n' "$RESP" >&2
  exit 1
fi

Check .data[0].b64_json before decoding. On failure print the raw body — Codex errors are JSON (usage_limit_reached, auth_not_found, moderation_blocked).

Edit

Same auth. JSON with a data URL — no upload step, no file_id. Do not pass the data URL through jq --arg: a typical generated PNG is larger than ARG_MAX (~1MB on macOS) and jq dies with Argument list too long. Write the data URL to a file and use --rawfile, then POST with --data-binary. Decode the same way as Generate.