Cost estimation

Find out what a generation costs in credits without running anything or spending credits.

PlaygroundCopy Anchor Link

Authorization: Bearer <CLIPIA_API_KEY>

curl -X POST "https://example.com/v1/models/nano-banana-2/estimate" \  -H "Content-Type: application/json" \  -d '{    "input": {      "prompt": "a sunset over mountains, cinematic",      "aspect_ratio": "16:9"    }  }'

{  "credits": 40}

POST /v1/models/:model/estimate calculates the cost of the given input on the selected model. No job is created and no credits are reserved. Any valid key works — no extra permission is needed.

RequestCopy Anchor Link

curl -X POST https://api.clipia.ai/v1/models/seedance-2-fast-i2v/estimate \
  -H "Authorization: Bearer $CLIPIA_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "input": {
      "prompt": "aerial shot over a neon city",
      "duration": 8,
      "resolution": "1080p"
    }
  }'

Response 200

{
  "credits": 40
}

If input contains a key the model will not apply (a typo, a parameter of another model), the estimate lists it in warnings — in the same form as submit. This lets you check a set of parameters before launching.

Why use itCopy Anchor Link

The cost depends on the model and its parameters — duration, resolution, number of images, text length for speech — not on how long the job actually runs. That means you can know it in advance:

• confirm the price before an expensive high-resolution video;
• compare parameter options, such as 4 vs 8 seconds or 720p vs 1080p;
• check the budget in automated flows where software launches the generation.

Submit uses the same calculation: for the same parameters, credits matches cost in the POST /v1/models/{model} response. Credits are reserved on submit, charged on success, and refunded in full if the generation fails.

ErrorsCopy Anchor Link