Which Sume media routes need a flag, and which are on prod?

Remix media and reference ingest are flag-gated: development has them on and production is opt-in. The trending-videos browse rebuild is on for dev and off in production. Video inspect, video frames, video trim, audio detach, video filter and Timeline 1.0 are documented as available on dest and prod.

That split matters if you want to read a reference clip with a production key today. The table is built from the headers of each docs page, read 2026-10-11, so check your own GET /v1/catalog before you ship.

What each docs page says about availability

Each row quotes the availability statement at the top of the matching docs page, or the closest one the page makes. Where a page states no flag, the table says so instead of guessing.

What to use on a production key

Each flagged capability has a plainer neighbor that the docs list as available everywhere. They do not do the same work, but they cover most reference reading.

How to tell in your own environment

The docs say the routes and the MCP tools are listed only where the flag permits. For MCP clients, read the tool list, since a tool that is not listed is the signal. For REST, a route that your environment does not serve answers with a not-found style error instead of a result, so test with one cheap call before you build on it. The remix media tools are sume_probe, sume_transcribe, sume_boundaries, sume_tile, sume_cut, sume_notes_write, sume_align and sume_understand_get, and reference_ingest is the ingest tool.

A missing route is a deployment fact, not a bug in your request. Reference ingest also names a runtime case: reference_ingest_unavailable means the media runtime has no function for it yet, and the docs say to fall back to video_inspect. Remix media has the equivalent remix_media_unavailable.

A note on prices

Prices in the second table come from the same pages: video trim lists $0.02 per job and audio detach $0.01 per job, both worked by worker ffmpeg with no provider inference. The flagged surfaces bill Modal compute, so confirm their rates in the live catalog instead of assuming a flat rate.

Planning around the gap

If your pipeline will eventually use remix media, develop against the dev environment where the flag is on, keep your calls behind a small adapter, and let production use inspect, frames and trim until the flag is opened for your account. The error codes above are stable and name the fix, so a fallback can key on them instead of on guessing.