Nano Banana is available on Pixapi — one endpoint, usage-based credits, ready for production.

3 Minutes to Leading Visual AI APIs

One API. Better pricing. Cleaner integration. Developer-first.

10+
Top models
99.9%
Uptime
~300ms
Latency
  1. 1curl https://api.pixapi.ai/v1/images/generations \
  2. 2 -H "Authorization: Bearer $PIXAPI_KEY" \
  3. 3 -H "Content-Type: application/json" \
  4. 4 -d '{
  5. 5 "model": "gpt-image-2",
  6. 6 "prompt": "A cinematic product hero shot",
  7. 7 "n": 1,
  8. 8 "size": "1024x1024"
  9. 9 }'
OpenAI
Gemini
Google Veo
Qwen
Doubao
Kling
Flux
MiniMax
Vidu

One prompt — use Pixapi from any Agent

Copy a single prompt to Codex, Cursor, or any coding agent so it understands Pixapi's models and endpoint patterns before writing code.

Pixapi — llms.txt prompt
Please read Pixapi's AI documentation and write production-ready code based only on the current Pixapi API docs.

Primary reference:
https://pixapi.ai/llms-full.txt

Also check these pages if needed:
https://pixapi.ai/docs/api-reference/
https://pixapi.ai/docs/guides/async-tasks/
https://pixapi.ai/docs/models/nano-banana/
https://pixapi.ai/docs/models/veo/

About Pixapi: Pixapi is a unified visual AI API gateway. It uses one account, one API key, usage-based credits, and separate endpoints for image and video workflows.

My task:
Write Node.js code that:
1. Generates an image with Nano Banana using POST /v1/images/generations.
2. Reads the generated image URL from response.data[0].url.
3. Creates a short image-to-video task with Veo using POST /v1/async/videos/generations.
4. Passes the generated image URL as input_image.
5. Uses duration for video length, not seconds.
6. Polls GET /v1/tasks/undefined until the task is completed.
7. Returns the final video URL from result.data[0].url.

Important constraints:
- Do not use async=true or "async": true.
- Do not use /v1/videos/generations.
- Do not use seconds for duration.
- Do not use image_url; use input_image.
- Keep the API key server-side and read it from process.env.PIXAPI_KEY.

From zero to first request in minutes

A familiar REST interface and predictable response format keep integration work small—even when the underlying model changes.

1

Create an API key

Open the developer console, create a scoped key, and keep it safely in your server environment.

2

Choose a model

Use the same endpoint for supported image and video models. Change models with one request field.

3

Ship and scale

Monitor credits and requests from one account while Pixapi handles provider routing and availability.

Create your API key
Pixapi — demo.request
curl --request POST \
  --url https://api.pixapi.ai/v1/images/generations \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "model": "nano-banana",
    "prompt": "A cinematic product shot",
    "size": "1024x1024"
  }'
200 OK · task queued · pay only for successful output

Why teams choose Pixapi

One platform, clear usage records, and production-minded support so you can focus on shipping image and video features.

One API contract

Use consistent authentication, task states, errors, and output formats across model providers.

Transparent credits

Estimate model costs before launch and monitor every request from the same developer console.

Curated routes

Access selected provider channels without maintaining separate accounts, SDKs, and invoices.

Fast integration

Familiar REST patterns and compact examples help teams make the first request quickly.

Secure key management

Create, rotate, and revoke API keys while keeping secret credentials on your server.

Human support

Open support tickets with request IDs and model details when an integration needs help.

Visual AI API platform

One API surface for image, editing, and video models

Pixapi keeps model access, API keys, credits, usage records, and async task handling in one developer workflow.

Call image generation, image editing, and async video tasks from your backend with one Pixapi API key.
Track credit balance, model usage, request history, and billing activity from the same account.
Use documented REST examples and model ids instead of rewriting provider-specific setup for every model.
Switch models by changing request fields while your product UI, rate limits, and customer plans stay under your control.

Pixapi is designed as a visual AI API for teams that are ready to put image and video generation inside real products. A visual AI API reduces the number of vendor decisions your backend has to make, because authentication, request style, usage records, and model routing live behind one Pixapi account. Instead of wiring every provider separately, your team can call a visual AI API and keep product code focused on users, permissions, and generated assets.

A useful visual AI API has to cover more than one media type. Pixapi connects image generation, AI image editing, and video generation so the same visual AI API can support a campaign image, a reference-based edit, and an async product video. That matters when a feature grows from a prototype into a customer-facing workflow. The visual AI API keeps the integration familiar while individual model choices continue to evolve.

Developers often start with one model, then need another model for cost, quality, speed, or availability. A visual AI API makes that comparison easier because the surrounding platform stays consistent. With Pixapi, the visual AI API links to model pages, pricing, docs, and examples, so a team can compare Nano Banana, GPT Image, Veo, Wan, and related routes without rebuilding billing and request handling for every experiment.

The commercial side is another reason to choose a visual AI API. If your product sells AI features, credits and usage records need to be clear before traffic arrives. Pixapi gives the visual AI API a credit ledger, purchase flow, and dashboard visibility so founders and product managers can estimate costs. The visual AI API becomes easier to explain to customers because each successful image or video request maps back to a visible account balance.

Security is simpler when the visual AI API stays on your server. Keep the Pixapi key in backend configuration, validate user inputs, call the visual AI API from trusted routes, and store generated asset URLs with your own user records. That pattern lets the visual AI API power public features while your application still controls rate limits, moderation policy, file retention, and customer entitlements.

Choose Pixapi when you want a visual AI API that is narrow enough to be understandable and complete enough to support production. The visual AI API covers model discovery, API keys, credits, image routes, video routes, documentation, and support touchpoints. For teams shipping visual features, a focused visual AI API is usually faster to operate than a loose collection of direct provider integrations.

Frequently Asked Questions

Everything you need to know before routing production image and video workloads through Pixapi.

Ship your next AI feature without rebuilding the model layer

Create an API key, choose a model, and send your first image or video request in minutes.