OpenAI
AvailableOpenAI has 39 models tracked on Modelglass across 8 verticals (Image, Language, Video, Audio, Science, Coding, Agentic, GDPval), most recently added 2026-07.
OpenAI has 3 image models (1 current-gen, 2 deprecated), 13 language models (7 current-gen, 6 previous-gen), 1 video model (1 current-gen), 5 audio models (1 current-gen, 4 previous-gen), 4 science models, 7 coding models, 3 agentic models, and 3 gdpval models on Modelglass, most recently added 2026-07.
Coverage across verticals
1 current-gen · 2 deprecated
Image pricing page ↗Creator and host for its own image models (DALL·E, GPT Image). Image pricing is published per model/quality/resolution.
7 current-gen · 6 previous-gen
Language pricing page ↗Creator and first-party host of the GPT / o-series / GPT-5 families. Standard per-1M-token input/output pricing is published on the developer pricing page (now served from developers.openai.com/api/docs/pricing).
1 current-gen
Video pricing page ↗OpenAI offers Sora video generation models via the API. Pricing is per-second of output video, tiered by resolution and quality (standard vs. pro). Sora access requires an API key with sufficient usage tier.
1 current-gen · 4 previous-gen
Audio pricing page ↗OpenAI offers TTS via the /v1/audio/speech endpoint (tts-1 and tts-1-hd models) billed per 1M characters, and STT via Whisper (/v1/audio/transcriptions) billed per minute of audio. Both are pay-per-use with no subscription required.
4 ungraded
7 ungraded
3 ungraded
3 ungraded
How much does OpenAI cost?
Most priced image models from OpenAI on Modelglass run $0.0060–$0.21 per image (10 models in this range). Compare exact pricing →
See how OpenAI's models fit into a cost-aware routing setup
See how →Release cadence
39 models tracked across all verticals. Earliest release 2022-09, most recent 2026-07.
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.