DeepSeek API vs Glimpse

DeepSeek API

Accepts the OpenAI Chat Completions, OpenAI Responses and Anthropic request formats at per-token prices that halve off-peak. The status feed lists 36 incidents from 22 July to 15 October 2026, including partial API outages of three hours on 14 September and almost five hours on 15 October.

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.

DeepSeek API

1. Send only data you'd be happy to publish
2. Schedule bulk work off-peak for half price. Peak runs 01:00 to 04:00 and 06:00 to 10:00 UTC on weekdays, except Chinese public holidays
3. Set max_tokens yourself. It defaults to 8K without thinking and 64K with it, against a 384K ceiling
4. For schema-checked tool arguments use base URL https://api.deepseek.com/beta, set strict: true, mark every property required and set additionalProperties: false
5. Keep a fallback provider and re-run evals after model changes. 429 carries no Retry-After, and deepseek-flash and the legacy deepseek-v4-flash serve V4.1-Flash-1017 since 17 October 2026

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