Models.dev exists to answer a very practical developer question: which model should I use, and what will it cost? The site organises every entry under a canonical identifier in the form provider/model, so the same model served by several providers can be compared directly rather than guessed at. Columns cover context window, maximum output, whether input and output are supported, reasoning, tool calling, structured output, temperature control, open versus closed weights, price per million tokens, and release and update dates.
Because model releases move fast, the catalogue is built to stay current, with sortable and searchable tables that let you scan by lab or provider and filter down to what matters. Entries include both closed flagship models and open-weight alternatives, making it useful for cost planning as well as capability research.
The project is open source and free to use, and it is intended to be consumed programmatically. Developers can pull the catalogue into their own tooling through a JSON API or a type-safe SDK, which makes it a practical backend for dashboards, routing logic, or internal cost calculators rather than just a reference page to browse.