Grok Imagine Video 1.5 on Sume: one per-second rate for 480p and 720p
Sume's catalog prices grok-imagine-video-1.5 at one per-second list rate for 480p and 720p. Read the live rate from the catalog before budgeting.

In Sume's catalog, grok-imagine-video-1.5 has a single per-second list price that does not change with resolution: the repo constant is $0.01 per second for both 480p and 720p, which is $0.0125 per second at the catalog's list times 1.25 rule, before cent rounding. Treat the Sume figure as the repo's recorded list rate and read the live price from the catalog endpoint before you plan a budget.
Two facts about this row matter more than the exact cent: it is image-to-video only, and it has no aspect ratio field. Both come from Sume's model card and catalog, read 2026-10-03.
What the Sume row lists
Because the list rate is flat per second, the resolution choice here changes quality and file size but not the rate. A 10 second clip has the same list amount at 480p and 720p.
| Field | Value |
|---|---|
| Modes | Image-to-video only (no text-to-video, end frame, references or edit) |
| Resolutions | 480p, 720p |
| Duration | 4 to 15 seconds |
| Aspect ratio | No aspect_ratio field |
| Audio | No audio; generate_audio is rejected |
| Required input | image_url or first_frame_url |
| Price basis | Per second, one list rate for both resolutions |
Why read the live rate
The repo records its own list source for this row, dated 2026-06-29, and applies the catalog multiplier on top. Vendor pricing can change after that date, so the endpoint, not a blog page, is the number to budget with.
Check the live rate in a few lines
The catalog has a per-model route, GET /v1/video-router/models/{model_id}. This script prints what Sume returns for the row, including its pricing block.
import json
import os
import requests
def main():
key = os.environ["SUME_API_KEY"]
r = requests.get(
"https://api.sume.com/v1/video-router/models/grok-imagine-video-1.5",
headers={"Authorization": f"Bearer {key}"},
timeout=30,
)
r.raise_for_status()
print(json.dumps(r.json(), indent=2))
if __name__ == "__main__":
main()
When this row is the right one
If you need text-to-video, native audio or an end frame, pick a different row; the Video Router docs list capabilities per model.
- You already have a still and want a short motion version of it.
- You do not need sound, end frames or text-only generation.
- Your clip is 4 to 15 seconds and 480p or 720p is enough.
- You do not need to control the aspect ratio; the row has no such field.
Sources
Related posts
More in Pricing
- H3 Max Recast 768p or 1080p: draft cheap, publish in HD
Sume bills H3 Max Recast at $0.375 a second at 768p and $0.5625 at 1080p. Budget a 768p test pass and one 1080p final, and what each plan costs.
- H3 Max Recast 768p vs 1080p: price per second and per clip
fal lists H3 Max Recast at $0.30 a second for 768p and $0.45 for 1080p. On Sume the same two tiers cost $0.375 and $0.5625 a second; per-clip math for 5-30 s.
- H3 Max Recast price calculator: Python, 768p and 1080p per clip
A short Python function prices a Sume h3-max-recast clip from its length and resolution: $0.30 or $0.45 list per second, times 1.25, rounded up to the cent.
- H3 Max Recast price: why a 12.4-second clip bills 13 seconds
H3 Max Recast bills the source video length rounded up to a whole second, 5 to 30 s. Worked costs at 768p and 1080p, and how to read the length first.
Written by Sume