Groq's /models API Lists Non-Chat Models Alongside Chat Models With No Labels

A developer testing Groq's GET /models endpoint found that 5 of 14 listed models fail standard chat completion requests — not due to outages, but because they are speech-to-text, text-to-speech, or routing models mixed into the same flat list. None of the entries include a modality field to distinguish chat models from other types, leaving developers to identify them by name alone. Additional testing revealed that certain models, including guard models and allam-2-7b, silently enforce lower token limits than commonly used values like 8,192, with no indication of this in the API response. The compound router model returned a rate-limit error attributed to a different underlying model, exposing routing behavior only through error messages. Developers building model pickers are advised to probe each model individually and cache actual responses rather than relying on the catalogue.