Billing and credits

Pixapi meters model usage with credits. A request may consume credits based on the selected model, output count, resolution, duration, quality, and provider cost.

Credit lifecycle

1. Your app sends a request with a model id and parameters.
2. Pixapi estimates whether the account has enough credits.
3. The model provider is called.
4. Credits are consumed after successful output, or according to the model-specific task policy.

Cost examples

Model family	Typical unit	Notes
gemini-2.5-flash-image (nano-banana alias)	per image	Fast image generation and editing.
gemini-3.1-flash-image-preview (nano-banana-2 alias)	per image	Balanced Gemini image generation with broader size control.
gemini-3-pro-image-preview (nano-banana-pro alias)	per image	Premium Gemini image generation and editing.
gpt-image-1.5	per image	Higher-quality image generation can cost more at larger sizes.
veo	per second	Video cost depends on duration and quality.

Use the live pricing page for current plan limits and credit packages. Review account balance in Credits and subscription details in Billing.

Insufficient credits

If the account does not have enough credits, Pixapi returns:

{
  "error": {
    "code": "insufficient_credits",
    "message": "Not enough credits for this request."
  }
}

Your application should show Credits, Billing, or an upgrade action instead of retrying automatically.