Glimpse vs xAI API (Grok)

Glimpse 20

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). On 17 October the tool, tool_choice, response_format, structured_outputs, cached-price, context, output-limit and batch readings for this model all came from OpenRouter's endpoints API, which this run doesn't use, so they are struck. No readable first-hand page states them today. Elorian's docs sit on a host that refuses our crawler, and Together's model page says only text, image and video in and text out on a dedicated deployment. Tool use (0 of 20), structured output (0 of 15), prompt caching (0 of 15), context length (0 of 15), batch (0 of 10). OpenRouter's SDKs in TypeScript, Python and Go, and any OpenAI client works (10 of 10, per the 17 October check, not re-read on 4 November 2026). OpenRouter's documented error codes with limit_source and remedy hints, nothing specific to video or image limits (10 of 15, per the 17 October check, not re-read on 4 November 2026). 0 + 0 + 0 + 0 + 0 + 10 + 10 = 20.

xAI API (Grok) 90

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling with parallel calls on by default and tool_choice of auto, required, none or a named function (20). Guaranteed structured outputs (15). Automatic prompt caching, cached input at 0.25x on grok-4.7 ($0.50 per million) and 0.16x on grok-4.3 (15). 500,000-token context on grok-4.7 and 1,000,000 on grok-4.3, 13 of 15 for the default model's 500K. The Batch API is now 20% off on grok-4.7, 4.6 and 4.5 as well as the older models, with batch requests outside the rate limits (10 of 10, up from 5 on 6 October). One first-party SDK, xai-sdk for Python, with the OpenAI SDKs and Vercel's AI SDK documented as alternatives (5 of 10). Status codes documented with fixes, no Retry-After header found (12 of 15).

Glimpse 40

Model reading. Elorian publishes no API reference, model card or llms.txt in public. Its docs sit at platform.elorian.ai/docs, a host whose robots.txt answers access denied. The 17 October contract reading rested on OpenRouter's OpenAPI-documented chat endpoint, with no recorded visible download link on a host now paused, and on the parameter list from OpenRouter's endpoints API, both struck (0 of 25). OpenRouter's llms.txt and Markdown docs, including video input (10, per the 17 October check, not re-read on 4 November 2026). The launch post and Together's model page name the jobs (visual search, video captioning, dense counting, robotics planning) and the post states limits (token cost, no action outputs yet), but nothing says when not to use it or how video is sampled (6 of 20). Typed parameters for OpenRouter's chat endpoint in its API reference, with no reasoning effort levels documented for this model (10 of 15, per the 17 October check, not re-read on 4 November 2026; the 17 October tool_choice reading came from the struck endpoints API). OpenRouter's examples and error reference, with no Glimpse-specific examples or limits on video length or image count (7 of 15). OpenRouter's dated changelog, with no changelog from Elorian (7 of 15, held as partly met; the dated canonical slug came from the struck endpoints API). 0 + 10 + 6 + 10 + 7 + 7 = 40.

xAI API (Grok) 88

OpenAPI 3.1 document at docs.x.ai/openapi.json, 39 paths and 205 schemas on 6 November, covering Responses, Chat Completions, files, images, videos and models. The batch endpoints documented in the REST reference still aren't in it (20 of 25, applied as for gemini-api's missing Interactions API). llms.txt and a Markdown twin of every page, plus a docs MCP server (10). The models page says which model to use for code, chat, images, video and voice, and reference pages list each parameter. Reference not read in full (18 of 20). Structured outputs are guaranteed to match the schema for supported keywords, and tool arguments always conform with strict implicitly true (15). Examples in Python, JavaScript and curl on every guide. The debugging page lists status codes with fixes, but the cause cells for 400, 403, 404 and 415 are still empty (13 of 15). Release notes are grouped by month without day dates, and model slugs come as aliases and dated versions (12 of 15).

Glimpse 56

Model reading. OpenRouter bearer keys with per-key credit limits, management keys and OAuth PKCE, no permission scopes (25 of 30, per the 17 October check, not re-read on 4 November 2026). Training on API data on this route is off according to OpenRouter's policy display for Together (no training, no prompt retention). Elorian's privacy policy trains on Inputs and Outputs from free access by default and says different terms may apply to paid and API use. The 17 October reading of Elorian's terms came from a script on a host that now refuses our crawler and is struck. Whether Elorian receives prompts from the Together deployment was not established (8 of 20, held as partly met). OpenRouter's zero-retention filter and Together's no-retention flag, against Elorian's retention 'for as long as reasonably necessary' with no period (8 of 15). OpenRouter's per-generation activity records for the operator (10 of 15). OpenRouter's security.txt was valid at its last check. Elorian has no security.txt, disclosure policy, bug bounty or certification found (5 of 20, held as partly met). 25 + 8 + 8 + 10 + 5 = 56. Readings of OpenRouter and Elorian pages per the 17 October check, not re-read on 4 November 2026.

xAI API (Grok) 97

Model reading. Team API keys with ACLs per endpoint and per model, QPM and TPM caps, expiry, and create, rotate, disable and delete through the Management API, plus documented mTLS. GitHub secret scanning disables leaked keys and emails the owner (30). The security FAQ says SpaceXSI never trains on API inputs or outputs without explicit permission (20). Requests and responses are kept 30 days for abuse auditing, then deleted, and team admins can switch on zero data retention themselves, confirmed by an x-zero-data-retention header on every response (15). Console audit log and a Management API audit-events endpoint, plus optional per-key request logging (15). security.txt valid to 2027-06-29 with a HackerOne bug bounty and a separate safety contact for prompt-injection issues. SOC 2 Type 2 is claimed in the security FAQ with the reports behind an NDA in the trust centre, so 17 of 20. Remote MCP doesn't support require_approval, which the model checklist doesn't score but reviewers should see. New in October, a guidelines array lets the caller make the model decline nsfw, violence or profanity content, which the checklist doesn't score.

Glimpse 23

Hosted lines, read on the OpenRouter route. OpenRouter's status host refuses our crawler in robots.txt, so the 17 October reading of it is struck, and Elorian has no status page found (0 of 20). No 90-day incident record could be read. The 17 October uptime figures came from OpenRouter's endpoints API, a JSON data API this run doesn't use, and are struck (5). OpenRouter's limits page documents credit, budget and rate limits and a key endpoint that reports what's left, but sets no request cap on paid models, and no limit for Glimpse was found (8 of 15, per the 17 October check, not re-read on 4 November 2026, openrouter.ai paused on its terms). The errors page documents Retry-After on 429 and 503 and on 402 in-flight budget errors, and says the official SDKs honour it, with no safe-retry guidance or idempotency keys recorded (10, Retry-After alone, the value this run gives backoff or Retry-After guidance by itself; per the 17 October check, not re-read on 4 November 2026). No SLA from Elorian or for this endpoint (0). Elorian and Together label Glimpse a research preview (0). 0 + 5 + 8 + 10 + 0 + 0 = 23.

xAI API (Grok) 55

Status page at status.x.ai with components for the global and US API endpoints, voice, the consumer apps and, since the Cursor merger, Cursor's services, with an RSS feed (20). The feed, read on 6 November, now holds 267 incidents back to 11 August, so the whole 90-day window is readable. On the API components there were high error rates on grok-4.6 and grok-4.5 from 21:57 to 23:28 UTC on 17 August (about 90 minutes) and a models outage on the global and US endpoints from 13:30 to 17:09 UTC on 3 September (about 3 hours 40 minutes), so several majors. A 26-minute datacenter outage across the API on 22 September, voice disruptions of 12 and 28 minutes on 10 September and 6 October, a 63-minute voice and Imagine degradation on 30 October and a 37-second model degradation on 24 October add to the record (0). Rate limits published per model and tier, grok-4.7 at Tier 0 is 150 requests a second and 50M TPM, with the per-second cap derived as RPM divided by 48 (15). The rate-limits page shows exponential backoff on 429, but no Retry-After header or overload guidance was found (10 of 15). No SLA found in the docs or llms.txt (0). The Responses API has been GA since September 2025 and grok-4.7 carries no preview label (10).

Glimpse 51

Model reading. Announced on 16 October 2026, 19 days before 4 November, and still labelled a research preview on Together's model page that day (30). One release, no history of versions or retirements and no deprecation notice period (3 of 20). Elorian's support page says there is no support queue, and channels are email and a Discord server, not tested (6 of 25, per the 17 October check, not re-read on 4 November 2026; the terms' no-support clause came from the struck script reading). No official SDK from Elorian. OpenRouter's SDKs are current (8 of 15). No package or CI of Elorian's to read. OpenRouter's SDK repositories run CI (4 of 10). 30 + 3 + 6 + 8 + 4 = 51.

xAI API (Grok) 77

Model reading. grok-imagine-image-quality and grok-imagine-image-pro retired on 2 November 2026 as announced in September, Grok Voice 3.0 and custom moderation controls in October, Grok 4.7 on 21 September (30). No minimum notice period found. Retirements come as dated migration guides, retired slugs redirect to a replacement rather than failing, billed at the replacement's price, and grok-voice-2.0 was deprecated in October with no end date (4 of 12). Shutdowns in the last 90 days with dates given in advance, grok-voice-transcribe-1.0 on 2 October and grok-imagine-image-quality on 2 November (8 of 8). Release notes several times a month but dated only by month, support by email and a Discord #help channel, not tested. On xai-sdk-python a collaborator commented on 2 of the 16 most recent threads with replies, and most outside pull requests since 23 October are open without a maintainer reply (10 of 15, down from 12). The repository has CI, release and version-bump workflows (5 of 10). One current first-party SDK, xai-sdk 1.21.0 tagged on 23 October, Python only (10 of 15). Supported runtimes stated, Python 3.10 or later (10).

Glimpse 38

Closed model with weights not released and the open-weight base model unnamed. Elorian's terms sit on platform.elorian.ai, whose robots.txt answers access denied, so they were not read; published terms on a refusing host keep the closed-service value, held at 13 of 30. The privacy policy says Elorian trains on submitted content from free use and gives no retention periods, and the acceptable use policy, updated 19 October 2026, is still titled Privacy Policy and still carries a drafting comment from a terms outline in its markup (10 of 30, held as partly met; the 17 October comparison with the terms rested on the struck script reading). No deprecation policy or dated notices (0 of 20). Services hosted in the United States and subprocessors named by category only, and OpenRouter shows Together as the provider with its data policy (8 of 20). 13 + 10 + 0 + 8 = 31.

xAI API (Grok) 63

Closed service under xAI's enterprise terms, with the Python SDK under Apache-2.0 (15). The docs agree with each other on no training, 30-day abuse retention, 30-day storage of stateful responses and the ZDR route, but the privacy policy, enterprise terms and DPA at x.ai/legal answered a Cloudflare block page on 6 October and again on 6 November, so they couldn't be compared (15 of 30). Dated migration guides and redirect tables for each retirement, but no written deprecation policy, and Chat Completions, Anthropic compatibility and grok-voice-2.0 are labelled deprecated with no date (12 of 20). The US regional endpoint states what stays in the US, the global endpoint guarantees no region, and no subprocessor list was readable (10 of 20).