Claude API vs Glimpse

Claude API

Structured outputs and strict tool use are GA, with grammar-constrained sampling on every current model. Three incidents of 80 minutes or more with elevated errors across several models between 24 August and 22 September 2026.

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.

Claude API

1. Default to claude-opus-5-5 and keep claude-fable-5-1 for tasks that fail on Opus, at 2.5 times the price
2. Don't send tool_choice any or tool to Opus 5.5, Sonnet 5.5 or Fable 5.1. Use auto with strict: true on the tool
3. Put cache_control on the system prompt and tool list. Reads cost 0.05x input on Opus 5.5
4. Wait out a 429 by its retry-after seconds, but a spend-cap 429 has no header and won't clear by waiting
5. Move off claude-sonnet-4-5-20250929 before 2026-11-30. Retired ids fail, they don't redirect
6. Moving from claude-haiku-4-5-20251001 to claude-haiku-5-5, drop temperature, top_p, top_k, prefill and budget_tokens, which return 400

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