Usage-based pricing
Pay with credits based on the selected model and output settings, with no separate provider account.
Connect Google's latest Gemini image generation family through Pixapi's unified authentication, billing, and response format.
Keep the model quality you want while simplifying the infrastructure around it.
Pay with credits based on the selected model and output settings, with no separate provider account.
Use Nano Banana aliases for Gemini 2.5 Flash Image, Gemini 3.1 Flash Image Preview, and Gemini 3 Pro Image Preview from the same endpoints.
Consistent task states and errors make the integration easier to monitor and maintain.
A compact REST request is enough to add Nano Banana generation to an existing backend.
Each Nano Banana name maps to a canonical Gemini image model, so you can choose the naming style that fits your integration.
nano-banana-2Alias for Gemini 3.1 Flash Image Preview, the balanced choice for modern production workloads and broad size control.
nano-banana-proAlias for Gemini 3 Pro Image Preview, for professional creative work where fidelity and composition matter most.
nano-bananaAlias for Gemini 2.5 Flash Image, a cost-efficient option for previews and latency-sensitive product flows.
The Nano Banana API page explains how Nano Banana aliases map to Gemini image models and how Pixapi keeps billing, keys, and responses consistent.
The Nano Banana API is useful for teams that want Google's Gemini image family without building a separate provider workflow. Pixapi treats Nano Banana, Nano Banana 2, and Nano Banana Pro as practical aliases for canonical Gemini image models. That means a Nano Banana API request can stay readable for product teams while still using precise model ids behind the scenes.
A good Nano Banana API should make the alias mapping obvious. Pixapi explains which Gemini model each Nano Banana API variant points to, how the variants differ, and when a team should use the balanced, premium, or cost-efficient route. The Nano Banana API page reduces confusion for developers who see community names and canonical model names used together.
The Nano Banana API is especially valuable when a product needs both image generation and image editing. Teams can use the Nano Banana API for prompt-based generation, reference-aware workflows, and product image experiments while keeping one Pixapi key on the server. The Nano Banana API does not require customers to manage a separate Google AI account for supported Pixapi routes.
Cost planning is clearer when the Nano Banana API sits inside Pixapi's credit system. Product teams can compare the Nano Banana API variants with GPT Image routes and other image models before deciding which option belongs in a free tier, paid plan, or internal workflow. Because the Nano Banana API shares usage records with the rest of Pixapi, finance and engineering see the same account history.
Implementation should keep the Nano Banana API server-side. Store the Pixapi key in backend configuration, choose the Nano Banana API alias or canonical Gemini model id, send the request to the image generation endpoint, and save the returned asset URL. This Nano Banana API pattern keeps browser code free of secrets while your product controls permissions and rate limits.
Choose the Nano Banana API when your product needs Gemini image generation with simpler account operations. Pixapi wraps the Nano Banana API with docs, pricing, model comparison, credits, and support workflows. That makes the Nano Banana API practical for campaign images, product photos, creative previews, reference edits, and other visual features that need a stable production path.
Use your Pixapi key and the shared image generation endpoint. The model field can use a Nano Banana alias or the canonical Gemini model id.
curl https://api.pixapi.ai/v1/images/generations \
-H "Authorization: Bearer $PIXAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "nano-banana-pro",
"prompt": "Editorial product photo",
"n": 1,
"size": "1024x1024"
}'The essentials for choosing and integrating the model family.
Create a Pixapi key and send your first request with the same account you can use for other image and video models.
Create API key