What is it
Per-video pricing is a billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms. Unlike token-based or character-based meters that count inputs, per-video pricing anchors on the discrete output — a rendered clip — making it one of the most buyer-legible units in generative AI.
The per-video unit emerged as AI video generation matured from research prototype to production API. Early platforms bundled video into subscription tiers or credit pools without surfacing per-clip cost; as compute costs became predictable enough to publish, vendors began quoting explicit per-clip rates. MiniMax is the most fully articulated example in the corpus: its Hailuo 2.3 model prices clips at $0.19–$0.56, with resolution (768P or 1080P) and length (6 or 10 seconds) each moving the rate to reflect the underlying GPU cost.
Per-video billing coexists with credit-based and dollar-denominated variants that surface the same economics differently. Arcads, a platform for AI-generated UGC video ads, wraps its video generation in a credit subscription: a monthly plan (approximately $200/month based on affiliate-program disclosures) includes a credit allotment, and each video consumes a variable number of credits. FLORA takes a third path — dollar-denominated usage at published model API rates — so a team generating Veo 3.1 or Kling 3.0 videos sees the exact dollar cost of each generation drawn from a pooled team budget, enabling direct client billing from usage history.
How it works
Per-video billing charges a fixed or tiered fee for each video clip the platform renders. The billable dimensions that drive rate variation are resolution, clip duration, and model quality tier. Vendors publish a rate table that crosses these dimensions; the buyer’s total cost is clip count multiplied by the applicable per-clip rate.
| Dimension | What it controls | Example |
|---|---|---|
| Resolution | Pixel count of the output frame | MiniMax Hailuo 2.3: 768P vs 1080P shifts the per-clip rate |
| Duration | Length of the generated clip in seconds | MiniMax: 6-second clips vs 10-second clips carry different rates |
| Model / quality tier | Compute cost of the generation run | xAI grok-imagine video is priced per second of output ($0.050–$0.080/sec), implying rate variation by quality |
| Credit or dollar abstraction | How the per-clip cost is surfaced | Arcads: one video consumes N credits from a monthly pool; FLORA: each clip billed at the published model API rate in dollars |
Unit math: Total bill = Σ (clips at resolution R × duration D × per-clip rateR,D). For MiniMax at 1080P / 10 seconds: 1,000 clips × $0.56 = $560.
The worked example clarifies why per-video cost can swamp the token bill on multimodal workloads. A MiniMax developer running 20,000 Hailuo 2.3 clips at roughly $0.30 average per clip accrues about $6,000 in video charges in a month — compared to roughly $33 for 50M input plus 15M output tokens on the MiniMax-M2 model at $0.30/M in and $1.20/M out. The meter migrates decisively from tokens to output units the moment a workflow goes beyond text. Choosing that output unit well is the core problem covered in choosing the right usage metric.
xAI’s per-second billing is an alternative formulation of the same idea — grok-imagine’s $0.050–$0.080/sec maps to roughly $0.30–$0.48 for a 6-second clip, comparable to MiniMax’s range. Pricing by the second is more granular and handles variable-length clips without a separate rate row per duration. Whichever way the meter is expressed, per-video billing is a form of usage-based pricing anchored on the rendered asset.
Companies using this
Four companies in the corpus meter video as an explicit billing unit — one per-clip, one per-second, one dollar pass-through, and one credit subscription. The table below lists each with its pricing model, billing units, and verification date.
| Company | Product | Pricing model | Billing units | Free tier | Verified |
|---|---|---|---|---|---|
| Adobe | Adobe's generative-AI monetization — Firefly (image/video/audio generation billed in generative credits) and GenStudio (enterprise gen-AI content platform) | Yes | 2026-08-06 | ||
| Arcads | AI-generated UGC video ads | No | 2026-06-11 | ||
| FLORA | AI-powered creative canvas and workflow platform | Yes | 2026-07-23 | ||
| Together AI | AI Acceleration Cloud — serverless inference, dedicated endpoints, GPU clusters, Code Sandbox, fine-tuning | Yes | 2026-08-04 | ||
| xAI | Grok API and agentic AI stack | Yes | 2026-08-04 | ||
| Zhipu AI | GLM foundation models, per-token API, and GLM Coding Plan | Yes | 2026-07-22 |
Explore this theme in the knowledge graph
FAQ
What is per-video pricing in AI platforms?
Per-video pricing is a billing unit where each AI-generated video clip is metered and charged as a discrete output. MiniMax charges $0.19–$0.56 per Hailuo 2.3 clip depending on resolution (768P–1080P) and length (6–10 seconds), while xAI meters grok-imagine video at $0.050–$0.080 per second of generated footage.
How much does AI video generation cost per clip?
It varies by platform and output settings. MiniMax's Hailuo 2.3 runs $0.19–$0.56 per clip. xAI's per-second rate of $0.050–$0.080 works out to roughly $0.30–$0.48 for a 6-second clip. FLORA passes through published model API rates (for Veo 3.1, Kling 3.0 and others), and Arcads bundles video into a credit subscription that starts around $200/month.
How does per-video pricing differ from credit-based billing for video?
Per-video pricing assigns a direct dollar cost to each clip, making spend predictable at the output level. Credit-based billing — used by Arcads — wraps the same economics in an abstraction layer where one video consumes a variable number of credits from a monthly pool, which simplifies budgeting but hides the per-clip cost.
Why do AI video platforms charge per clip instead of per token?
Video generation is compute-bound and its cost tracks the rendered output, not text tokens. Anchoring the price on the discrete clip — and its resolution and duration — makes the meter legible to buyers and directly reflects the underlying GPU cost of each generation run.
Related billing units
- Credit-Based BillingA billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.
- Token-Based PricingA billing unit common in LLM and AI products, where customers are charged per input and output token processed.
- Per-Seat PricingA billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
- Per-Resolution PricingA billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
- Bandwidth-Based PricingA billing unit where customers are charged per gigabyte of data transferred out of the platform.
- Per-Function-Invocation PricingA billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
- CPU-Hour PricingA billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
- GB-Hour PricingA billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
- GPU-Hour PricingA billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
- Per-API-Call PricingA billing unit where customers are charged per API request, regardless of payload size or processing time.
- Per-GB Storage PricingA billing unit where customers are charged per gigabyte of data stored on the platform per month.
- Media-Minute PricingA billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
- Per-Request PricingA billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
- Per-Event PricingA billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
- Vector Storage PricingA billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
- Per-Character PricingA billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
- Per-Document PricingA billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
- Per-Page PricingA billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
- Per-Transaction PricingA billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
- Active-User PricingA billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
- Per-Task PricingA billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
- Per-Unit PricingA billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.
- Workflow Execution PricingA billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
- Per-Message PricingA billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
- Per-Invoice PricingA billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
- Per-Action PricingA billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
- Per-Image PricingA billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
- Per-Conversation PricingA billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
- Per-Record PricingA billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
- Per-Word PricingA billing unit common in translation and localization platforms where the metered object is the word count of content processed.
- Milestone-Based PricingA billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
- Per-Outcome PricingA billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to 'outcomes' as a countable billing unit.
- Per-Datapoint PricingA billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
- Per-Interaction PricingA billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
- Data Licensing PricingA pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.
- Robot-Hour PricingA billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
- Per-Contact PricingA billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
- Per-Mailbox PricingA billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
- Browser-Hour PricingA billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
- Per-Generation PricingA billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
- Per-Ticket PricingA billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
- Per-Log PricingA billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
- Per-Trace PricingA billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
- Per-IP PricingA billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.
- Per-Device PricingA billing unit where each hardware device or endpoint connected to the AI platform is metered.
- Per-Case PricingA billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
- Per-Report PricingA billing unit where each AI-generated report or analysis document is metered as a discrete output.