DeepInfra vs SambaCloud

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.

SambaCloud

Per-token prices and the model list are readable without a key at /v1/models, and a free tier needs no card. Production models get two to three weeks' notice before removal, 13 model ids left between March and June 2026, and the docs disagree with the live catalogue on MiniMax-M2.7.

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

SambaCloud

1. Call GET https://api.sambanova.ai/v1/models at start-up and use only ids it returns. The docs name models the endpoint no longer lists
2. Read x-ratelimit-remaining-requests and x-ratelimit-remaining-requests-day on every response. The free tier allows 20 requests a day per model
3. Treat 429 queue_full and 503 maintenance as retryable after a delay, and 410 model_deprecated as a signal to change model
4. Validate JSON output yourself. Schema enforcement is best effort and strict: true changes nothing
5. Check max_completion_tokens per model. DeepSeek-V3.1 caps output at 7,168 tokens and Llama 3.3 70B at 3,072