Is Kling O3 or LTX-2.5 on Sume? Read the catalog before you plan
New video models appear weekly in vendor feeds. Sume's catalog is one authenticated GET: this checks for Kling O3, LTX-2.5 and Wan 3.0 and reads capabilities.

Whether a new model is on Sume is answered by one call, GET /v1/video-router/models, not by a blog post. The catalog this post was written against lists kling-3 (Kling Video v3 Pro), wan-3.0, seedance-2.5, two MiniMax rows, gemini-omni-flash-1.1, grok-imagine-video-1.5, h3-max-recast and, when its provider is configured, a motion-transfer row. It lists no Kling O3 and no LTX model id. Re-run the call before you build around any name.
A vendor changelog proves a model exists, and a catalog proves a route does.
Check by id
This Python call prints every id the catalog returns and flags the names you care about. It uses only the documented catalog endpoint.
import os
import requests
r = requests.get(
"https://api.sume.com/v1/video-router/models",
headers={"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"},
timeout=30,
)
r.raise_for_status()
ids = [row["id"] for row in r.json()["data"]["models"]]
print(ids)
for want in ("kling-o3", "ltx-2.5", "wan-3.0"):
print(want, want in ids)What the vendor pages show
Runway's changelog (2026-09-18) lists Kling O3 4K, Kling 3.0 Standard, Kling O3 Standard and Kling 3.0 Motion Control as available on Runway MCP. That page says what Runway offers. They do not say what Sume exposes.
| Name | Vendor page | In Sume's Video Router catalog |
|---|---|---|
| Kling O3 4K | Runway changelog, 2026-09-18 | no |
| Kling 3.0 Motion Control | Runway changelog, 2026-09-18 | separate route and MCP tool, not a catalog row |
| Kling Video v3 Pro | Kling developer page | yes, as kling-3 |
| Wan 3.0 | Runway API changelog, 2026-08-26 | yes, as wan-3.0 |
| LTX-2.5 | not read for this post | no id |
What to do when it is not listed
You have three honest choices. Use the route the vendor offers, pick the closest catalog row and test it, or ask for the model through your usual support channel. Do not guess an id: an unknown model returns an error, and a similar-looking id may be a different product.
- Same model family, different resolution: compare the row's
capabilities.resolutions. - Same job, different model: use Video Router Auto with
sume/autoand accept that Sume does not disclose which family ran. - Pinned model required: stay on the vendor until the id appears.
Where the facts are
The catalog contract is on the Video Router page, and the response fields are in Video generation. Vendor claims are on Runway's changelog and Kling's developer page for the vendor's own model list.
Sources
Related posts
More in Developers
- Why is my TTS job slow? Read the Sume job events timeline
GET /v1/jobs/{id}/events returns a sanitized lifecycle timeline. Use it to tell queue wait from generation time and failed webhook deliveries.
- Jupyter contact sheet: one prompt across four Sume image models
A notebook cell that sends one prompt to four Sume image models, tiles the results into a labeled contact sheet with Pillow, and prints each billed cost.
- Keep your Sora-style create_video() call: map it onto Sume
Sora's seconds, size and input_reference become duration, resolution plus aspect_ratio, and a first frame. Here is that map as a Python wrapper over Sume.
- Kestra webhook trigger has no HMAC: verify Sume deliveries first
Kestra's Webhook trigger is protected by its key alone. Verify Sume's sume-v1 signature in a thin relay, then start the flow, and submit with a stable key.
Written by Sume