Extend a Grok Imagine video on Sume: chain by last frame
xAI's guide lists video extension from the final frame. Sume's Grok row has no extend, so pull a late frame with video-frames and start the next clip from it.

Sume cannot extend a Grok Imagine clip in one call, but you can chain clips yourself: extract a frame from just before the end of the first MP4, then submit it as the first_frame of the next Grok job. Each hop is a separate job and a separate charge, and 15 seconds is the most a single Grok job can run on Sume.
What xAI offers and what Sume exposes
xAI's video guide lists extension as a mode that continues a video from its final frame, alongside editing and reference-to-video. The Sume Grok row accepts one start image only, so extension is not offered. The chain below is a workaround, not the same feature, and the join is only as smooth as your prompt makes it.
Step 1: take a late frame
The video-frames API reads a clip stored on media.sume.com and returns durable stills at the times you list in at[]. Each time must satisfy 0 <= t < duration, so you cannot ask for the exact last instant. Ask for a point a fraction of a second before the end. If the clip is not already a media.sume.com artifact or asset of your workspace, import it first with POST /v1/media-imports, because the API refuses off-host URLs.
curl -X POST https://api.sume.com/v1/video-frames \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: chain-001-frame" \
-d '{"video_url": "https://media.sume.com/artifacts/artf_demo/clip1.mp4", "at": [5.8], "format": "png"}'Step 2: start clip two from it
When resource_status is ready, frames[0].url is a durable image. Send it as frame_images[0].image_url.url with frame_type: "first_frame" in the next POST /v1/videos for grok-imagine-video-1.5, and describe what happens next in the prompt.
Costs and caveats
Costs add up per hop at the Grok rate of 1.25 cents a second, plus the video-frames job, which Sume charges by its own compute time. Expect visible differences at the cut: Grok sees one image, not the motion before it, so keep the camera move and lighting words the same across prompts and join the clips on a cut or a short transition in the timeline.
| Hop | Seconds | Unrounded Grok cost |
|---|---|---|
| Clip 1 | 10 | $0.125 |
| Clip 2 from a frame of clip 1 | 10 | $0.125 |
| Clip 3 from a frame of clip 2 | 10 | $0.125 |
| Total video | 30 | $0.375 unrounded; $0.39 billed (3 x $0.13) |
Sources
Related posts
More in Developers
- Claude Code 2.1.296: MCP tool names over 128 characters, and Sume's
Claude Code 2.1.296 leaves out an MCP tool whose name exceeds 128 characters. The longest tool name in Sume's hosted list is 28, so none are near it.
- Claude Code subagent autoCompactWindow: keep Sume job ids
Claude Code 2.1.296 lets a subagent auto-compact earlier than the main chat. Keep Sume job ids out of the summary and re-read state with jobs_status.
- CLAUDE_CODE_WORKFLOW_SUBAGENT_MODEL: model choice vs Sume spend gates
Claude Code 2.1.296 can run every workflow agent on one model. Sume's idempotency_key, dry_run and max_spend_credits gates do not change with the model.
- Claude MCP connector denylist: switch off Sume's paid tools
Enable all Sume tools in an mcp_toolset, then disable the paid ones by name. Anthropic recommends denylisting write tools for read-only assistants.
Written by Sume