Overview
Nano Banana 2.1 supports text-to-image generation and reference-guided image editing. It accepts flexible aspect ratios, up to 10 reference images in image-to-image mode, and 1K, 2K, or 4K output.Endpoint and authentication
Base URL:
All requests require your APIXO API key:
Copy-paste async quickstart
This request submits a text-to-image task and returns ataskId.
taskId; you need it to poll for the final result.
Poll for result
resultJson after state becomes success:
Request body
Text-to-image
Image-to-image
Parameters
Result delivery mode. Use
async for polling with statusTask, or callback for webhook delivery.Required when
request_type is callback. Must be a public HTTPS URL that can receive the final task payload. See Webhooks.image_urls is required only when mode is image-to-image. When omitted, aspect_ratio and resolution default to 1:1 and 1K.Response format
Submit task response
POST /generateTask/nano-banana-2-1 returns a task ID when the task is accepted:
Status response fields
Webhook callback mode
Use callback mode when your backend should receive the final result automatically instead of polling.Billing
Market display references equal the standard APIXO price multiplied by 1.30, rounded half up to three decimal places. They are comparison values, not live third-party quotes or the charged amount. New non-LLM requests use 1 credit =$0.001. Calculate the full amount, including billable quantity and add-ons, apply the applicable account discount, then round the request total upward to the next whole credit. Agreed fixed unit prices retain their precision and replace the standard price and discount; final rounding still applies. See credit conversion and rounding.
Nano Banana 2.1 is billed per generated image. The selected resolution determines the unit price.
For current published pricing, see API pricing.
Latency and polling
Actual latency varies by prompt complexity, reference image accessibility, resolution, and current queue load.
Rate limits and concurrency vary by account and API key. If you receive
429, slow down requests and retry with backoff.
Errors and troubleshooting
HTTP errors
Task failure codes
See Error Codes for the full error reference.
MCP integration
The complete model schema declares result decoding inmcp.result and supported file bindings in mcp.attachments. These are client integration metadata, not generation input parameters. Attachment paths: image_urls. Preserve the user’s file order. Model parameter validation remains on the API.