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

Nano Banana Pro

Use nano-banana-pro for image generation and reference-image editing through one public OpenAI Images API style contract.

What This Page Covers

  • This page only covers nano-banana-pro
  • The customer-facing entry point is POST /v1/images/generations
  • The input image field is image_input
  • The current public contract is limited to URL references in image_input; image and data: inputs are not exposed publicly
  • Gemini / Vertex and other providers may sit behind this route, but those provider details are not part of the customer contract

Capability Status

The Pricing page and this doc use the same status language: Verified means there is a current minimal live artifact, while Beta means the official capability exists but the public validation set or edge coverage is still being completed.

Currently Validated Capabilities

The following conclusions come from live validation on March 31, 2026:
  • official Vertex channel 318 (vertexsophie) direct truth:
    • 2 reference images work
  • local relay on localhost:4000, pinned to channel 318, verified:
    • single WEBP URL reference works
    • single JPEG URL reference works
    • 2 PNG URL references work
    • resolution: "1K" works
    • resolution: "4K" works
    • aspect_ratio: "1:1" works
    • aspect_ratio: "21:9" works
    • output_format: "png" works
    • output_format: "jpg" works
    • the response returns data[].url
Do not present the following as fully promised customer-facing capability yet:
  • whether the exact multi-image limit is 8 or higher
  • 2K
  • exact large-file URL limit
  • exact 30 MiB boundary
  • additional aspect_ratio combinations
  • exact output_compression semantics
nano-banana-pro currently exposes only image_input URL input publicly. The image field is rejected by the service, and data: / Base64 is not part of the current public contract.

Request Parameters

Current Multi-Image Status

  • 2 references: verified
  • higher counts: exact upstream max is still pending, so do not promise it publicly yet

Routing Note

  • single-image requests can use normal available carriers
  • multi-image requests are currently routed only to official Gemini / Vertex carriers
  • that is a server-side routing rule; the customer contract stays the same

Request Examples

Single-Image Edit

Two-Reference Input


Response Example

The recommended automation path is to consume data[].url:
To retrieve the generated image, read data[0].url. Crazyrouter currently archives upstream inline image output and returns a public URL to the client.

Validation Snapshot

Current Known Limits

  • image is not accepted
  • data: / Base64 is not part of the public input contract
  • the docs do not promise more than 2 references yet
  • the docs do not promise the exact 30 MiB URL boundary yet
  • the docs do not promise full closure on every screenshot-listed ratio or parameter yet
If you need Gemini native generateContent image endpoints, see Gemini Image Generation and Gemini Image Editing. If you care more about reference-count breadth, also see Nano Banana and Nano Banana 2.