Sume Videos page default: an 8 s 720p Auto clip costs 100 credits

The Sume Videos page opens on Auto, Create mode, 16:9, 8 seconds, 720p, with audio on. Auto prices like Gemini Omni Flash 1.1, so that default clip costs $1.00, which the button shows as 100 credits (1 credit is one cent). Stepping to 1080p raises the same 8 s clip to $1.50.

Where the default comes from

defaultVideoControlsValue() in the Agents videos controls sets mode create, model sume/auto, aspect 16:9, duration 8, resolution 720p and generateAudio true. A code comment says the stored preference key was bumped so that old sticky 1080p choices reset to the 720p default.

Auto offers two resolutions (720p and 1080p), two aspect ratios (16:9 and 9:16) and the durations 3, 4, 5, 6, 8 and 10 seconds. The audio toggle is hidden for Auto, because the model it resolves to always produces native synced audio.

How the button price is computed

estimateCreateCreditCost calls the same pricing helpers that API admission uses. For Auto it picks the Gemini Omni Flash estimator. The comment in video-create-credit-estimate.ts says a credit is one US cent of billable amount, and that the estimate is list price x 1.25. The Omni list rates are $0.03, $0.10, $0.15 and $0.30 per second at 360p, 720p, 1080p and 4K.

Cents round up

The catalog formula is list x 1.25, rounded up to the next cent, so a 3 s clip at 720p (0.375 dollars) shows as 38 credits. Auto does not offer 4K on this page, so the button never shows a 4K price.

Changing the setting before you submit

Credits come from the live balance of the workspace. If the estimate is above the balance, the API refuses with 402 insufficient_credits on submit, and the page does not start a job. Try a shorter duration first: Auto prices per second, so halving the length halves the price.

The same clip sent through the API with "model": "sume/auto" defaults to 8 s and 720p, and the default target for text, frame and reference requests is Gemini Omni Flash 1.1.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"sume/auto","prompt":"A barista pours latte art, close shot, cafe sounds","aspect_ratio":"16:9"}'

Reading the credit number

The CTA shows whole credits. Because the amount is rounded up to the cent, a 5 s 720p clip shows 63 credits, not 62.5. Switching to Wan 3.0 at the same settings gives 63 credits for 5 s too, since both rows are $0.125 per second at 720p. Kling 3.0, H3 and Grok use their own estimators, so their numbers differ.

The estimate is a price, not a promise of a result. If a job fails, see how reserve and refund work in the billing docs before you retry.