A short generated video can cost much more than a text response. The important inputs are billable generated seconds, the model’s selected output option, and the number of charged clips—not how many finished videos a customer keeps.
Keep platform and resolution explicit
The same model family can have different prices by output resolution, audio inclusion, service variant, and billing platform. Choose the exact listed option. If your arrangement is not in the catalog, enter a custom per-second rate rather than borrowing a similar model’s price.
The catalog’s Veo profiles identify the Gemini Developer API and video with audio. Their notes explain which resolutions are supported. Check Google’s published pricing before relying on a rate. Do not add an automatic failed-attempt surcharge where the provider only bills successfully generated output.
A credit example
At an illustrative $0.10 per generated second, an eight-second clip costs $0.80. Ten clips monthly cost $8 per normal customer. If 10% of paying customers generate five times that volume, expected cost becomes $11.20 per paying customer.
At a $19 subscription, $7.80 remains before payment fees, free-user usage, and operating expenses. Offering fifty clips to every subscriber changes the model dramatically: fifty eight-second clips cost $40 at that same entered rate.
This example excludes editing, enhancement, delivery bandwidth, and retention. Those may need additional components or variable costs. A “video credit” should therefore map to a defined generated duration and supported option, not an unspecified promise.
Stress the creative workflow
Customers may generate several alternatives before choosing a final clip. Count charged alternatives, not only the chosen result. Compare an economical-resolution baseline with a higher-resolution scenario and review the margin at each price.