Closed beta or open API? Seven checks before you plan on a model
Kling 4.0 Flash is a closed beta and Tavus Griffin-Lite is for select testers. Seven checks that separate a launch post from something you can call.
Short answer
Plan around a video model only if you can answer yes to these: it has a public model id, a published price, stated limits, an access path you qualify for, a date, a terms page and a fallback. Right now Kling 4.0 Flash is a closed beta for Ultra yearly subscribers (fal, read 2026-10-04) and Tavus says its Griffin-Lite research preview "will not be available for use for customers at this time" (Tavus, read 2026-10-04). Neither passes.
The seven checks
| Check | Kling 4.0 Flash | Griffin-Lite |
|---|---|---|
| 1. Public model id in an API | Not published | Not available to customers |
| 2. Published price | No API price | None |
| 3. Stated limits | 3 to 20 s, 720p, 8-bit SDR in beta | Research preview figures only |
| 4. Access you qualify for | Ultra yearly subscribers | Select trusted testers |
| 5. A date | Full Kling 4.0 expected in October | None given for customers |
| 6. Terms and data use | Not read here | Not read here |
| 7. Fallback you can call today | kling-3 on Sume | Avatar video jobs on Sume |
How to use the table
Score each model out of seven. Under four, treat it as news, not a plan: do not write code against it, do not quote it to a client, and do not promise a delivery date. Between four and six, run a small test if you have access, and keep your fallback live. Seven means you can budget it. Re-score weekly, because a launch week can move three checks at once.
Check seven in practice
Your fallback should be something you can call right now with a quote. On Sume that means reading the catalog and pinning an id, for example kling-3 at $0.14 a second with audio off or wan-3.0 at $0.125 a second at 720p. A pinned id in a config value means that when the new model arrives, swapping it is a one-line change and a re-test, not a rewrite.
curl https://api.sume.com/v1/videos/models \
-H "Authorization: Bearer $SUME_API_KEY"Applying it to your own launch list
Write the seven checks into a shared sheet with one row per model you hear about, and fill it from vendor pages, not social posts. Date each cell. A model that moves from three to six over a few weeks tells you when to start a test; one that sits at two tells you to ignore the noise. Keep the sheet next to your budget so a decision to adopt comes with a price and a fallback attached.
Caveats
- Kling's own release-notes page did not render its body when read, so beta details here come from fal.
- Check 6 is blank on purpose: read each vendor's terms yourself.
- Sume's catalog lists what you can call; a vendor's announcement does not change it.
Sources
Related posts
More in Use cases
- Coffee or tea pouch photos with AI: zip top, crimp and print
Pouches have a crimped top, a zip and a window. Stage them on a counter with Sume's image API and check the seal, the print and the shape before publishing.
- Course welcome video captions in your brand color (slam, $0.20)
Burn captions in your school's accent color: set design.colors.active on the slam style. It does not work on punch or tiktok-green. $0.20 for clips to 60 s.
- Article 50: creator duties vs provider duties, side by side
Article 50(4) puts deepfake and certain text disclosure on deployers, while 50(2) puts marking on providers. A two-column split for teams that publish AI video.
- Case study video narrated by an avatar: three scenes, 55 seconds
Narrate a written case study as a 55-second, three-scene Sume avatar video: problem, change, result. Cost by tier and a body you can send; no names needed.
Written by Sume