DeepInfra vs Glimpse

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.

Glimpse

Glimpse reads images and video at $0.60 input and $3.00 output per million tokens, and OpenRouter serves it with tools, structured output and a 262,144-token context. It is a research preview with no public Elorian docs, model card or status page, and Elorian's terms allow training on submitted content unless a paid user opts out.

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

Glimpse

1. Call it through OpenRouter as elorian/glimpse at https://openrouter.ai/api/v1/chat/completions. Elorian's own API docs sit behind a console sign-in
2. Send video as a video_url content part, as a public URL or a base64 data URL. Batch requests are not available for this model
3. Set max_tokens yourself. The endpoint allows up to 256,000 output tokens, and visual reasoning spends many of them
4. Honour Retry-After on 429 and 503. With a single provider, a 503 means the Together deployment is unavailable, not that another host can take over
5. Treat counts and timestamps as unverified. Elorian's terms say outputs need independent human review before anyone relies on them