DeepInfra vs Novita AI

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.

Novita AI

Per-token prices for about 140 language models are public, and each key can carry an expiry, a model allowlist and a source IP allowlist. No status page, SLA or security.txt was found, the per-model rate limit figures are drawn by script, and both vendor SDK repositories are archived while the docs still point to them.

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

Novita AI

1. Set the OpenAI client base URL to https://api.novita.ai/openai and send the key as Authorization: Bearer. Keys start with sk_
2. Do not close a connection to stop generation. A request that reached the model is billed in full under status 499, so cap output with max_tokens
3. On 429, check whether the code is RATE_LIMIT_EXCEEDED or TOKEN_LIMIT_EXCEEDED and back off exponentially. No Retry-After header is documented
4. Read the changelog for retirement notices before pinning a model id. One retirement in October 2026 came with 11 days' notice
5. Ask the account owner for a key with an expiry, a model access policy and an IP allowlist. Keys are created and deleted only in the console