更新日: 2026-06-06

​

Nano Banana

Controlled testing only
POST /v1beta/models/nano-banana:generateContent

• nano-banana currently maps to nano-banana
• POST /v1/images/generations is no longer recommended for nano-banana
• nano-banana:generateContent can currently return image output
• but billing consistency on that native path is still under review, so it should be documented only as a controlled-test path, not as a stable production integration

​

Current Status

​

Current Risks

​

1. /v1/images/generations is no longer recommended

• Unknown name "imageOutputOptions" at 'generation_config.image_config'
• an abnormal billing sample on a failed request

​

2. The native path still has billing-consistency risk

• POST /v1beta/models/nano-banana:generateContent returned an image successfully
• but the consumption log quota and the token-side used_quota delta did not line up

​

Current Recommendation

1. If you need a usable image-generation or image-editing route right now, start with Nano Banana 2
2. If you must evaluate nano-banana, use only the native Gemini generateContent route
3. Do not put nano-banana into formal production traffic until billing consistency is cleared
4. Do not use POST /v1/images/generations with model: "nano-banana"

​

Controlled-Test Template

curl "https://api.crazyrouter.com/v1beta/models/nano-banana:generateContent?key=YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "contents": [
      {
        "role": "user",
        "parts": [
          {
            "text": "Generate an IMAGE of a clean banana icon on a white background. Return image output."
          }
        ]
      }
    ],
    "generationConfig": {
      "responseModalities": ["TEXT", "IMAGE"]
    }
  }'

​

Legacy Route

curl -X POST https://api.crazyrouter.com/v1/images/generations \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "model": "nano-banana",
    "prompt": "..."
  }'