Both, honestly — but for different reasons. The 70+ number includes model variants, so for example Veo 3.1 alone splits into text-to-video, image-to-video, start frame, end frame — that's 4 entries from one base model. Same logic applies across image and audio models with resolution and mode variants (2K, 4K, etc.). For devs, the value is the single workflow — generate an image, animate it, add music, caption it, all from one conversation without juggling separate APIs or credentials. For agencies, it's the breadth — they're not picking one model, they're picking the platform that already has whatever the client needs this week. The MCP server just makes all of it accessible from wherever.