Google has 25 models tracked on Modelglass across 8 verticals (Image, Language, Video, Audio, Science, Coding, Agentic, GDPval), most recently added 2026-06.
Google has 4 image models (2 current-gen, 1 previous-gen, 1 deprecated), 5 language models (3 current-gen, 2 previous-gen), 4 video models (2 current-gen, 2 deprecated), 2 audio models, 3 science models, 4 coding models, 2 agentic models, and 1 gdpval model on Modelglass, most recently added 2026-06.
Coverage across verticals
2 current-gen · 1 previous-gen · 1 deprecated
Image pricing page ↗Hosts Google's Imagen family via Vertex AI (and the Gemini API). Per-image pricing, billed only for requests that return success.
3 current-gen · 2 previous-gen
Language pricing page ↗Creator and first-party host of the Gemini family (Gemini API / Google AI Studio; also on Vertex AI). Some models use tiered pricing by prompt size (e.g. a higher rate above 200K input tokens).
2 current-gen · 2 deprecated
Video pricing page ↗Google DeepMind's Veo video generation models are accessible via the Gemini Developer API. Pricing is per-second of output video. Vertex AI may carry different rates; the Gemini Developer API (ai.google.dev) rates are the canonical public numbers recorded here. Free tier is available but limited.
2 ungraded
Audio pricing page ↗Google Cloud AI services covering Text-to-Speech (WaveNet, Neural2, Studio voices) and Speech-to-Text (Chirp 2, standard). Pricing is per-character for TTS and per-minute for STT, with a free tier (0–1M characters/month for TTS, 0–60 minutes/month for STT). Billed via Google Cloud Platform account.
3 ungraded
4 ungraded
2 ungraded
1 ungraded
See how Google's models fit into a cost-aware routing setup
See how →Release cadence
25 models tracked across all verticals. Earliest release 2018-03, most recent 2026-06.
Derived from Modelglass's per-vertical provider registries — image/llm/video/audio's registry/providers/*.yaml records, plus science/coding/agentic/gdpval's benchmark registries, where a provider is identified by the prefix before "/" in each model's model_id rather than a registry record of its own. Where the same company uses a different provider slug or model_id prefix across verticals (e.g. Google DeepMind vs. Google Cloud, or Qwen's "alibaba" model_id prefix in the coding registry vs. its "qwen" provider slug elsewhere), coverage is merged onto a single profile per an explicit, human-reviewed alias list (registry/provider-aliases.yaml) — everything else reflects exact-slug or exact-prefix matches only.