Which provider gives this model the most room overall?
Each limit as a percentage of the best provider's for this model, averaged over the limits that provider was measured on. Video density counts as video tokens per minute; tokens per image are left out. 100 means it matches the best provider on every limit. Providers measured on fewer than two limits aren't scored. How it's scored.
measured limit ≥ the real limit is higher: nothing failed up to our probe's cap
Show as table
Model
Provider
Value
Nemotron 3.5 Super VL
Together AI
100
Nemotron 3.5 Super VL
Together AI via OpenRouter
100
Nemotron 3.5 Super VL
DeepInfra (fp4) via OpenRouter
75
How much of a video does the model actually see?
Every route got the same 5-minute 1080p video. Video tokens per minute is what the provider billed for it: the amount of visual input the model got, and what ranks providers. Frames per minute is how many frames that was, and how large, worked out from the bills and the model's own preprocessing code.
Video tokens / min billed for the video; ranks providersFrames delivered / min and the size each frame was resized to
"On the first minute", "on a 360p copy": the provider couldn't take the original file whole, so it got the first part or a smaller copy of the same video. That counts.
Fixed per video: the provider sends the same number of frames however long the video is, so longer videos get fewer per minute.
Bars are scaled within each model. Hover a row for how the frames were worked out. How we measure.
Show as table
Model
Provider
Video tokens / min
Frames / min
Frame size
Measured on
Nemotron 3.5 Super VL
Together AI
9,470
120
672×384
the first minute
Nemotron 3.5 Super VL
Together AI via OpenRouter
9,470
120
672×384
the first minute
Nemotron 3.5 Super VL
DeepInfra (fp4) via OpenRouter
900
6.2 (fixed per video)
the 5-minute clip
How many video frames fit in one request?
768×432 frames, the size most video pipelines send. Whichever limit hits first counts: image count, decoded pixels or the context window.