v1/videos/models `created` is a catalog date, not a release date

Do not use created to date a model. Every entry on Sume's /v1/videos/models returns the same value, 1767225600, which is 2026-01-01T00:00:00Z. The source comment states that it is the catalog publication date, not a provider release date.

Why it is fixed

OpenRouter-compatible descriptors carry a created integer, so Sume fills it in. A single constant is honest about what it knows: the date the video catalog was published, not the date any one vendor shipped a model. Adding a model later does not change the value.

Real launch dates come from vendors

MiniMax's H3 post is dated 31 Jul 2026 (read 2026-10-04). Google's Omni 1.1 Flash post is dated 27 Aug 2026 (read 2026-10-04). Both fall after 2026-01-01, yet both show the same created on Sume.

If you need a launch date, cite the vendor page; if you need to know that Sume serves the model, read the catalog.

What to read instead

Use supported_durations, supported_resolutions, supported_aspect_ratios and pricing_skus to decide whether a model fits. The script converts created to a date so you can see for yourself that it is constant.

import os
from datetime import datetime, timezone
import requests

resp = requests.get(
    "https://api.sume.com/v1/videos/models",
    headers={"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"},
    timeout=30,
)
resp.raise_for_status()
seen = set()
for m in resp.json()["data"]:
    when = datetime.fromtimestamp(m["created"], tz=timezone.utc)
    seen.add(m["created"])
    print(m["id"], when.date())
print("distinct created values:", len(seen))