sume/auto video: default 8 s at 720p, and a 2 to 4,286 cent range
Video Router Auto defaults to 720p and 8 seconds, with 3 to 10 second clips at 16:9 or 9:16. The catalog reports a 50 cent estimate and a 2 to 4,286 cent range.

sume/auto is the Video Router Auto model: you send a prompt and Sume picks the model. Its create controls default to 720p and 8 seconds, and clips run 3 to 10 seconds at 16:9 or 9:16. The public catalog lists the Video Router entry with an estimated price of 50 cents, a minimum of 2 cents and a maximum of 4,286 cents.
Because Sume does not say which family served the request, the price you can plan on is a range, not a single rate. This post shows the arithmetic behind the defaults so you can set a spending cap.
What the docs and catalog say
Read 2026-10-09. The poll response reports model: sume/auto, and resolution is a pure function of the normalized request and the catalog version, so an idempotent replay gets the same price and route.
- Default resolution 720p, default duration 8 seconds, 3 to 10 second clips, 16:9 or 9:16.
- Catalog estimate: 50 cents; minimum 2 cents; maximum 4,286 cents ($42.86).
- Sume does not disclose which family served the request, and it tells you not to infer the family from the output.
- Video 1.0 is a compatibility alias for the same Auto pipe, and the docs say Sume will retire it.
An 8-second 720p clip on each pinned row
If you pin a model instead, the same default clip costs the amounts below.
| Row | 720p per second | 8 s at 720p |
|---|---|---|
| Gemini Omni Flash 1.1 | $0.125 | $1.00 |
| Wan 3.0 | $0.125 | $1.00 |
| Seedance 2.0 | $0.378 | $3.024 |
| Seedance 2.5 | $0.5778 | $4.6224 |
When to pin, when to use Auto
The 50 cent estimate is below every 8-second 720p price in the table: the cheapest, $1.00, is double it. The estimate is a catalog planning figure, not a quote, so do not size a budget on it. If cost per clip matters, pin the model; if you want one request shape that works while the catalog changes, use Auto and cap spend at the maximum.
A pinned request is below, for comparison with the Auto body {"model":"sume/auto","prompt":"...","aspect_ratio":"9:16","duration":5}.
curl -X POST https://api.sume.com/v1/videos \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"wan-3.0","prompt":"A vertical clip of rain on a window","aspect_ratio":"9:16","resolution":"720p","duration":8}'Setting a cap
The following figures use the same list prices as the tables above.
- If your application can fail a job above $5.00, check the estimate before you submit and compare it with your cap.
- The pinned Omni and Wan options both come to $1.00 for the default clip, which is a useful reference line.
- Replays with the same Idempotency-Key get the same price and route, so retries do not change the cost.
Sources
Related posts
More in Developers
- Sume error retry matrix: retry with the same key, or fix the request
Which Sume API errors to retry with the same Idempotency-Key, which to fix first, and which to leave alone. A table and a small Python function that decides.
- Sume job next_action: poll_status, fetch_result, inspect_events
The Sume status payload tells your client what to do next. Three next_action values map to five job states; here is the full table and a TypeScript switch.
- Sume MCP OAuth in six steps: from the first challenge to a call
Hosted Sume MCP OAuth takes six steps: challenge, authorize redirect, consent page, Write toggle, PKCE code exchange, then a bearer call to the MCP endpoint.
- pricing_skus has three key shapes: one Python function for the total
GET /v1/videos/models returns per-video-second-<res>, per-video-second and per-1000-video-tokens. A Decimal function totals a 30 s clip and flags token pricing.
Written by Sume