Grok Imagine Video API: Cost per Finished Clip
At first glance, AI video pricing looks almost suspiciously cheap. Grok Imagine Video 1.5 Lite starts at just $0.02 per generated second at 480p, or $0.03 at 720p. The flagship 1.5 model costs more, but even then, those headline rates tempt developers and creative teams to budget as if every generation will be a clean, cinematic bullseye on the first try.
Anyone who has actually shipped generative video knows that rarely happens. Models drift, physics glitches, hands warp, and lighting flickers. The smarter move is to budget around the exact endpoint, output resolution, conditioning media, and a realistic retry count. One more thing worth saying early: a consumer Grok subscription is a different purchase from API usage. Having an active X Premium or SuperGrok account doesn't magically put unmetered API tokens into your developer console (we all wish it did).
Rates verified in late 2026 against the official API price table. All figures in USD before applicable taxes. Candidate counts represent real-world production assumptions rather than vendor quality benchmarks.
Select the model before calculating
Here's how xAI structures the rate card across its video endpoints:
| API model | 480p output / second | 720p output / second | 1080p output / second | Listed media input rates |
|---|---|---|---|---|
| grok-imagine-video-1.5-lite | $0.02 | $0.03 | $0.14 | $0.01 per image |
| grok-imagine-video-1.5 | $0.08 | $0.14 | $0.25 | $0.01 per image |
| grok-imagine-video | $0.05 | $0.07 | Not listed | $0.002 per image; $0.01 per input video second |
What to keep in mind: the standard endpoint is not the full 1.5 endpoint, and Lite at 1080p is not priced like Lite at 720p. I'd log and lock the exact model string on every batch request, because jumping from 720p to 1080p on Lite increases your raw output cost by 4.67× ($0.03 to $0.14/s). That's the kind of surprise you'd rather not discover on the invoice.
Before you design an automated pipeline, skim the generation guide for supported durations, aspect ratios, and input modes. A per-image input rate doesn't mean every endpoint accepts multiple reference frames or arbitrary control nets. Verify supported features with a single test request before you queue up a thousand calls.
A 20-clip 720p project: The reality of iteration
Say your marketing team needs 20 approved eight-second clips for a short-form video campaign. If you assume a fairly forgiving two candidates per approval, you're generating 40 takes totaling 320 generated seconds.
At Lite 720p, the raw output usage is 320 × $0.03 = $9.60.
Now suppose each prompt is conditioned on a high-res brand product image. Each request incurs an input image charge, adding 40 × $0.01 = $0.40. That brings your total listed generation and input-image usage to $10.00, or exactly $0.50 per approved clip. Producing and licensing those input assets remains a separate budget item.
Run that same 20-clip project on the full 1.5 model at 720p and the story changes: 320 × $0.14 = $44.80 for output, plus $0.40 in image fees, reaching $45.20. I held candidate counts constant here so you can compare unit tariffs fairly. In practice, full 1.5 may deliver higher visual fidelity with fewer retries, but only a controlled pilot with your actual art style can settle that.
A 100-clip month: How candidate pools scale
Now let's scale up to 100 approved ten-second clips at three candidates per keeper, a fairly typical commercial standard. That means generating 300 candidates and 3,000 output seconds:
| Selected route | Output usage | One image per request | Combined usage |
|---|---|---|---|
| Lite 480p | $60.00 | $3.00 | $63.00 |
| Lite 720p | $90.00 | $3.00 | $93.00 |
| Full 1.5 720p | $420.00 | $3.00 | $423.00 |
| Full 1.5 1080p, supported single-image mode | $750.00 | $3.00 | $753.00 |
This is exactly why unit rates mislead newcomers. The 720p Lite bill is not $30 just because the final reel contains 1,000 seconds. You generated three times that volume to find the winners. At two candidates per accepted clip, the same brief would consume $62.00 including the 200 input images; at five candidates it would consume $155.00. That wide swing is the whole story: measuring your prompt acceptance rate is the single most effective way to protect your video budget.
And if your creative team finds that only the first three seconds of a ten-second take are usable, there's no reason to keep paying for full-length generations. Tighten the shot descriptions, trim more aggressively in post, or reduce the requested generation length.
Editing and extension need their own quote
The standard video endpoint lists input video processing at $0.01 per second alongside output generation. For a supported video extension or edit with ten input seconds and ten newly generated output seconds at 720p, the base rate calculation is $0.10 + $0.70 = $0.80 before other inputs. Repeat that request three times and you're at $2.40 of usage, not $0.80.
The practical catch: don't assume every extension route bills the same way. Confirm whether input video seconds are billed on failure, whether prompt rejections trigger charges, and whether intermediate takes are retained in your workspace. Unsuccessful generations, safety filter blocks, and technical API drops can all have different billing behavior, so reconcile your daily dashboard instead of assuming creative rejections get refunded automatically.
Consumer plans and the full production budget
Consumer subscriptions like X Premium+ or SuperGrok come with their own private rate limits and web interface features. Our dedicated Grok subscription guide covers those details. You can't deduct a personal consumer subscription against raw API consumption unless your enterprise contract explicitly consolidates them.
Also keep in mind that video API bills are only one piece of the puzzle. They don't cover audio mastering, licensed soundtrack music, upscaling, editing suites, or creative direction. When you build your project spreadsheet, track input media, generation seconds, prepaid credits, and burn rates in separate columns.
My rule of thumb: start production on Lite when the visual style allows it, and step up to full 1.5 when hero marketing or higher resolution demands it. Anchor your workflow to approved deliverables rather than theoretical benchmark scores. For a broader look at the competitive market, check out our video cost guide.