メインコンテンツへスキップ
更新日: 2026-06-06

​
Chat Image Generation

As of March 23, 2026, production checks against Crazyrouter showed:
  • gpt-4o returns 200, but message.content is plain text, not standard multipart image content
  • gpt-image-2 also returns 200, but the current response shape is still text or Markdown containing a parameter block, an ID, and a preview link, not the standard OpenAI image_url multipart structure
  • If you need stable, machine-readable image output, the current recommended path is /v1/images/generations with gpt-image-2; for Grok image models, see Grok Image Models
  • If you need reference-image editing or multi-image input, do not keep treating the Nano Banana family as a stable /v1/images/generations entry point. Start with the native Gemini path documented on Nano Banana 2; Nano Banana is currently controlled-testing only
Do not parse the current Crazyrouter chat-image response as if it were standard OpenAI content: [{type: "image_url", ...}].

​
Currently Reproducible Chat Behavior

The following request hit gpt-image-2 in production and returned 200:
The observed message.content was a string shaped roughly like:
That means the current chat path behaves more like text-wrapped image-task output than a standardized multipart image message object.

​
Stable Path: Images API

If you need programmatic image retrieval, use:
The current gpt-image-2 stable path uses the primary image route https://api.crazyrouter.com/v1. Responses usually include:
  • data[0].url
gpt-image-2 does not support response_format; do not send response_format="url" or response_format="b64_json". To choose the image file format, use output_format="png", "jpeg", or "webp". So the stable automation path is still the Images API, not the chat-image compatibility path.
If you are only testing manually, the gpt-image-2 chat path is still useful for observation. If you need backend automation, storage, or post-processing, use the GPT Image docs or Grok Image Models. If your workload depends on reference-image editing or multi-image input, start with the native Gemini route documented on Nano Banana 2. Do not keep treating Nano Banana-family /v1/images/generations as the stable recommendation.