DeepInfra vs OpenAI API

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.

OpenAI API

Official OpenAPI document and an llms.txt index. Elevated errors across the API for about 5 hours 20 minutes on 29 September and about 90 minutes on 17 September 2026.

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

OpenAI API

1. Build on the Responses API. Astra calls tools only there
2. Use gpt-6-luna for routing and extraction and gpt-6.1-sol for most work. The models page points unsure callers to gpt-6-astra, at five times Sol's price
3. Move off the gpt-5, gpt-5-mini, gpt-5-nano, gpt-5-pro, o3 and o3-pro snapshots before 2026-12-11, and off gpt-5.1, gpt-5.3-codex and gpt-5.4-nano before 2027-04-01
4. Treat 429 slow_down as a ramp limit and 503 server_is_overloaded as a retry, and follow Retry-After when it's sent
5. Prompts over 272K tokens cost double on input. Trim before you pay for it