LTX API pricing SKUs vs Sume's pricing_skus catalog field

On LTX, a SKU is the combination of endpoint, model, resolution and output type a request resolves to, for example image-to-video-ltx-2-5-pro-1920X1080-audiovisual, and each SKU has its own per-second rate. On Sume, each video model in the catalog carries a pricing_skus object of billable rates, which are provider list times 1.25.

LTX's description is from its API pricing post, read 2026-10-01. Sume's side is from Video generation.

How is an LTX SKU read?

Per the post, the example name encodes the image-to-video endpoint, the ltx-2-5-pro model, a 1920x1080 resolution and audiovisual output. Change any one part and you move to another SKU with its own price. The /pricing endpoint returns every SKU as an array of price_cents and effective_date entries, needs no authentication, and the post says to treat it as the source of truth rather than hardcoding a rate.

curl --location 'https://api.ltx.video/pricing'

What does Sume return?

Each entry in the video models list has pricing_skus, described in the docs as pricing information per SKU. The OpenAPI schema describes it as Sume billable rates in USD, provider list times 1.25, keyed by SKU. The docs' example shows a key such as per-1000-video-tokens, so SKU keys differ by model and are not always per second. Read them from the catalog, not from a blog table.

curl "https://api.sume.com/v1/catalog" \
  -H "Authorization: Bearer $SUME_API_KEY"

How do the two compare field by field?

What should I do before estimating a cost?

Fetch the live rows on each side and multiply by your workload; neither side should be copied from a post. For a Sume-side method see video API cost calculator and pricing SKUs. Each Video Router row's billable_formula is the per-model truth, per the Video Router docs.