DeepInfra vs GroqCloud

DeepInfra

The model list, context sizes and per-token prices are readable without a key, and keys can carry an IP allowlist, a monthly spending cap and model-limited JWTs. Deprecated models get one week's notice and are then redirected to another model, there is no changelog or SLA, and an account needs a card or prepayment before any call.

GroqCloud

Free plan with no card, at 30 requests a minute and 1,000 a day on gpt-oss. Four model shutdown dates between 2026-07-17 and 2026-09-21, with no stated minimum notice.

DeepInfra

1. Call GET https://api.deepinfra.com/v1/openai/models at start-up for ids, context sizes and prices. No key is needed
2. Check the model field of each response. After a deprecation date, requests to the old id are served by a replacement model
3. Ask the account owner for a scoped JWT limited to the models and spend the task needs, not the full API key
4. Stay under 200 concurrent requests per model. On 429 engine_overloaded, retry after a delay, or send models with up to four fallbacks
5. Never inspect a JWT with GET /v1/scoped-jwt?jwtoken=, which puts the token in the URL. Keep credentials in the Authorization header

GroqCloud

1. Call /models at start-up. Four model ids stopped working this quarter
2. Read retry-after on a 429 and the x-ratelimit-remaining-tokens header before the next call
3. Free plan allows 8,000 tokens a minute on gpt-oss, so keep prompts small or batch them
4. Don't build on Qwen 3.8 27B. It's a preview and previews can go at short notice
5. Treat a 498 as Flex capacity and retry later; 5xx responses aren't billed