MiniMax H3 now lists 2K and 4K in Sume's supported_resolutions

Yes. Since commit fab7d59af (#11356), the minimax-h3 row of Sume's Video Router catalog lists 480p, 768p, 2K and 4K, so supported_resolutions on GET /v1/videos/models shows all four. Before, 2K and 4K were accepted and billed through a hidden admit list while the public row listed only 480p and 768p.

The gap this closes

A client that built its picker or its validation from the catalog could not see that minimax-h3 takes 2K or 4K, even though the request worked. The commit message says both tiers render (2560 by 1440 and 3840 by 2160) and that they are now listed at their existing list prices. The per-model hand allowlist in refineVideoRouterModelLimits is gone; one catalog check, videoRouterAdmitResolutions, serves every model.

The catalog comment for the row keeps the nature of the tiers: 480p and 768p are native, and 2K and 4K are upscales from 768p. 768p is not 720p; a 720p request to minimax-h3 is not on the list.

What the endpoints now show

The test in apps/api/src/videos/catalog.test.ts at that commit pins the pricing SKUs the models endpoint returns for minimax-h3.

What stays the same

minimax-h3 still takes 5 to 15 seconds, and the docs table at docs.sume.com/models/video-router still describes 2K and 4K as upscales from 768p. minimax-h3-max is a different row: it lists 480p, 768p and 1080p, with no 2K or 4K. The 4K token is the uppercase 4K; lowercase 4k is an alias, covered in a separate post.

The SKU values are the figures the unit test pins, and they equal the per-second list rates times the 1.25 house margin that the video-router docs describe for each row. The docs page is the place to confirm a current rate before you budget.

What to change in a client

Both /v1/video-router/generate and /v1/videos admit the same list for this model, which the commit's new test checks for every catalog row against every resolution in the schema enum.

• If you hard-coded H3 as 480p and 768p only, read supported_resolutions from the models endpoint instead.
• If you filtered 2K and 4K out of a picker because they were unlisted, remove the filter for minimax-h3.
• Keep sending minimax-h3-max for 1080p; do not expect 2K or 4K on that row.