Novita AI vs SambaCloud

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.

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.

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

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