Grok Imagine Video 1.5 on Runway: 10, 16, 29 credits a second

Runway's API prices Grok Imagine Video 1.5 (grok_imagine_1_5) at 10 credits per second at 480p, 16 at 720p and 29 at 1080p, plus 1 credit for each image or audio reference, and a start frame counts as a reference. At Runway's $0.01 per credit that is $0.10, $0.16 and $0.29 per second. Sume exposes the same model as grok-imagine-video-1.5, and its API takes it as image-to-video: image_url is required.

Both Runway pages were read on 2026-10-02: API pricing and costs and available models. Sume's side comes from Video Router and Video generation, plus the OpenAPI schema.

What does one Grok Imagine clip cost on Runway?

Multiply seconds by the resolution rate, then add 1 credit per image or audio reference. Runway's pricing page states the per-second rates and the reference fee; the totals below are arithmetic on those numbers, not a quote from Runway.

Runway's models page lists the model as taking text or an image and returning video, so a text-only call is possible there.

What does Sume accept for this model?

Sume's catalog id is grok-imagine-video-1.5. The OpenAPI description of image_url says it is required for this model, and end_image_url is documented as not supported by it. Sume's Video Router notes list 480p and 720p and a 4 to 15 second range, so 1080p is not a choice on Sume for this id; confirm the live values in GET /v1/video-router/models before you build on them.

Sume bills provider list price times 1.25 on every Video Router model, and each catalog row carries its own pricing_skus and billable_formula. This post does not quote a Sume dollar rate for the model because the docs pages I read do not print one; the catalog does.

How do I send the same clip as a Sume job?

Post to /v1/video-router/generate with the model id, a first-frame image and a duration. The body mirrors the OpenAPI example for Grok Imagine image-to-video: 720p, 6 seconds. Send an Idempotency-Key so a retry returns the original job instead of a second one.

Poll GET /v1/jobs/{id}/status until the job finishes. If you need text-to-video or 1080p, pick another catalog row; the Runway table above is where that choice shows up in credits.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: grok-i2v-001" \
  -d '{
    "model": "grok-imagine-video-1.5",
    "prompt": "Subtle camera push-in with natural motion.",
    "image_url": "https://example.com/inputs/first-frame.png",
    "resolution": "720p",
    "duration": 6,
    "mode": "async"
  }'

What should I check before choosing a route?

Decide what inputs you have. A still image and a short move fits both routes. A text-only idea, or a 1080p deliverable, fits Runway's row but not Sume's grok-imagine-video-1.5. Then compare the dollar figure: Runway's from credits above, Sume's from the catalog row times 1.25 as the catalog states it.