Google Image generation trial
Nano Banana 2 Lite
Explore low-cost image ideas when queueing and occasional failures are acceptable.
Nano Banana 2 Lite is a discounted image-generation route in TokenHot's catalog. It accepts text and image input, returns images and is billed per call at the catalog trial price. The catalog description warns that generation may take longer and fail roughly 10% of the time, so use it for exploratory drafts rather than reliability-sensitive production output.
- Text + image input
- Image output
- Discounted trial route
This route is explicitly described as a discounted trial with longer waits and occasional failures. Do not promise a successful image or use it as the only production path; keep a regular route and a retry or fallback policy.
USD /call
Pricing
| Group | Price |
|---|---|
| default | $0.02 |
Public list prices are shown in USD. Final charges may vary by account group and usage tier.
Overview
What is Nano Banana 2 Lite?
Nano Banana 2 Lite is useful when the question is “which direction should we explore?” rather than “can this asset ship without review?” Keep prompts focused, save the accepted and rejected results, and record failures as part of the experiment.
The existing application treats this as an image route. Use the dynamic pricing table for the current call price and the API docs for request parameters; image quality and output latency still need a real check on your prompt.
Generate a small visual set
Ask for distinct directions with a selection rubric instead of an unbounded stream of variants.
State what must remain
Use an input image to anchor subject, palette or composition, then inspect drift in the result.
Record the failed attempts
Keep prompt, parameters, wait time and failure reason so a cheap trial remains measurable.
From brief to deliverable
Put Nano Banana 2 Lite to work
Creative and marketing teams
Explore a campaign direction
Generate several low-cost visual concepts for a brief and select one direction for a regular production route.
- Tools you need
- Image generation, asset storage and a human reviewer.
- Keep in mind
- A trial output is a draft; do not publish without copy, rights and visual QA.
View a task brief
Use the supplied brief and reference to propose a small set of image directions. Label each concept, state the selection criteria and mark any failed or unusable result.
Design and brand teams
Make a low-risk reference variation
Explore one controlled change to a supplied image before deciding whether the result deserves a production route.
- Tools you need
- Reference upload, image review and versioned storage.
- Keep in mind
- Occasional failure and visual drift are expected; keep the source and compare the output side by side.
View a task brief
Create a controlled variation from the supplied reference. Return a comparison checklist for the requested change, invariants and any visible drift. Do not claim the image rendered if the call failed.
Content teams
Prototype a thumbnail family
Create inexpensive thumbnail directions for a content queue while preserving title-safe space and a consistent visual system.
- Tools you need
- Image generation, batch storage and a content review pass.
- Keep in mind
- Generated text may be wrong or unreadable; inspect every title treatment before use.
View a task brief
Generate thumbnail directions from the supplied titles and visual rules. Return safe-area notes and flag any unreadable or incorrect text.
Capabilities in context
Key features
| Feature | What you get | Why it matters |
|---|---|---|
| Billing unit | The catalog lists a per-call image price | Use the current dynamic price and count failed or retried calls in the experiment budget. |
| Input modes | Text and image input are listed | Keep reference images and their intended role in the prompt record. |
| Image output | The route returns images | Store output metadata and inspect the actual image at its destination size. |
| Trial warning | The catalog describes longer waits and roughly 10% failure | Build a fallback or retry policy and tell reviewers when an output is only exploratory. |
| Route identity | TokenHot model ID: nano-banana-2-lite | Pin the exact ID so trial results are not mixed with Nano Banana 2 or another image route. |
The discounted-trial behavior and call billing note come from TokenHot's current catalog description. Verify the current endpoint response, queue behavior and account limits before relying on the route.
Audience & fit
Where Nano Banana 2 Lite fits
Creative teams exploring directions
Use the route for cheap concept discovery, with a regular model available when a direction earns production attention.
Content teams making thumbnails
Generate drafts quickly but keep title, safe-area and rights checks outside the model call.
Designers testing references
Record prompt, input and drift so a failed or unstable trial still produces useful evidence.
Cost context
Plan the cost of a useful result
Count attempts, not just successes
The catalog warns of occasional failures. Include failed calls, retries, storage and review in the cost per accepted concept.
Budget the fallback
A trial route is cheaper only when its failure and rerun policy is explicit.
Price human QA
Text, rights, crop and brand checks remain necessary for every candidate that might ship.
Use the current pricing table for available rates and account groups. Model IDs and prices come from TokenHot’s catalog; provider pricing and subscriptions are separate.
API
Code examples
curl --location --request POST 'https://api.tokenhot.ai/v1beta/models/nano-banana-2-lite:generateContent' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data-raw '{
"contents": [
{
"role": "user",
"parts": [
{
"text": "draw a baby"
}
]
}
],
"generationConfig": {
"responseModalities": [
"TEXT",
"IMAGE"
],
"imageConfig": {
"aspectRatio": "16:9",
"imageSize": "2k"
}
}
}'Blog
Related Articles
FAQ
Frequently asked questions
What is Nano Banana 2 Lite best suited for?
Nano Banana 2 Lite is suited to the input, output, and capability types listed on this page. Test production workloads before choosing it for a critical system.
How is Nano Banana 2 Lite priced?
Pricing is shown in the pricing section above. Actual cost depends on usage volume, account group, and the request payload.
How can I call Nano Banana 2 Lite?
Use the model ID shown above with one of the supported API protocols. Code examples are provided when usage data is available.
Is Nano Banana 2 Lite suitable for production?
The catalog describes it as a discounted trial with longer waits and roughly 10% failure. Use a regular route for reliability-sensitive production.
What can it accept and return?
The catalog lists text and image input with image output. Verify current image dimensions and request parameters in the API docs.
How should I budget the route?
Use the dynamic per-call price, then add failed calls, retries, storage and review to estimate cost per accepted image.
Why did a generation take longer or fail?
The catalog explicitly warns about queueing and occasional failures. Keep the failure visible and use the configured fallback rather than claiming a successful output.
Get started
Build with Nano Banana 2 Lite
API