Runway Grok Imagine 1.5 credits per second vs Sume's rate
Runway bills Grok Imagine 1.5 at 10, 16 or 29 credits per second by resolution, plus 1 per reference. Sume's grok-imagine-video-1.5 is one flat per-second rate.

Runway's API pricing page, read 2026-10-01, lists grok_imagine_1_5 at 10 credits per second at 480p, 16 at 720p and 29 at 1080p, plus 1 credit per image or audio reference. Credits are sold at $0.01 each, so a 5-second 720p clip is $0.80 before references.
On Sume the same model family is grok-imagine-video-1.5, with one per-second rate for both of its resolutions. A 5-second clip reserves $0.07 and a 10-second clip $0.13, at list x 1.25 rounded up to the cent.
How do the two price sheets compare?
The numbers are for each company's own product, so treat them as two quotes, not a like-for-like discount.
| Clip | Runway 480p | Runway 720p | Runway 1080p | Sume |
|---|---|---|---|---|
| 5 s | $0.50 | $0.80 | $1.45 | $0.07 |
| 10 s | $1.00 | $1.60 | $2.90 | $0.13 |
What does Sume's row not do?
The catalog row is narrower than the model Runway sells. It is image-to-video only, so image_url or first_frame_url is required, it has no end frame, no reference inputs and no audio, and it accepts 4 to 15 seconds at 480p or 720p. There is no 1080p tier and no aspect_ratio. See the video docs.
How do I call it?
Send the start image and a motion prompt. Sume reserves the amount at submit and releases it if the job fails.
curl -X POST https://api.sume.com/v1/videos \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: grok-run-001" \
-d '{
"model": "grok-imagine-video-1.5",
"prompt": "Slow push-in, the lantern sways in the wind",
"duration": 5,
"resolution": "720p",
"frame_images": [
{
"type": "image_url",
"image_url": { "url": "https://example.com/lantern.png" },
"frame_type": "first_frame"
}
]
}'Sources
Related posts
More in Pricing
- Runway grok_imagine_image_2 reference image cost, per request
On Runway, grok_imagine_image_2 costs outputCount × perImage plus 1 credit per reference, charged once per request. Worked example, and Sume's Grok image price.
- Runway h3_max at 5 and 8 credits a second vs Sume's H3 Max
Runway lists h3_max at 5 credits per second for 480p and 8 for 768p. Sume's minimax-h3-max bills 480p, 768p and 1080p per second at list x 1.25. Side by side.
- Runway Hailuo 3 2K: 15 credits a second, and Sume's H3 rate
Runway API lists hailuo3 at 15 credits per second at 2K plus 2 per reference image. Sume's minimax-h3 2K rate, the 5 to 15 second range, and list x 1.25.
- Runway image credits in dollars, and the Sume per-image rate
Runway prices images from 1 credit (muse_image) to 41 (gpt_image_2) at $0.01 a credit. Where Sume lists the same model, its per-image estimate sits beside it.
Written by Sume