Nano Banana 2 is part of a broader API suite and is not offered as a completely standalone service. It is accessed through the same API gateway and authentication system as the other models in the family, meaning you use a single API key and a single endpoint base URL to reach it. The model is selected by specifying its identifier in the request payload rather than by changing the endpoint. This design makes it straightforward to switch between model tiers in code—often a one-line change—without restructuring the integration.
Being part of a shared API surface means Nano Banana 2 inherits the same rate limiting, quota management, and billing infrastructure as the other models in the suite. Your usage is tracked under the same project credentials, and you can monitor token consumption across model tiers from a single dashboard. This is useful for teams that want to compare cost per output between Nano Banana 2 and the Pro tier using real production traffic data before deciding which tier to standardize on.
The API also provides a consistent request and response schema across model tiers, so the same client code that sends a prompt and receives a base64-encoded image for Nano Banana 2 will work without modification when pointing at the Pro model. Optional parameters—such as aspect ratio, style guidance, and safety settings—are available on all tiers, though their effect on output quality varies by model. This consistency reduces the engineering overhead of supporting multiple model tiers in a single application.