{ "data": { "a": { "slug": "elorian-glimpse", "name": "Glimpse", "vendor": "Elorian", "vendorUrl": "https://elorian.ai/models.html", "kind": "model", "category": "inference", "summary": "Glimpse is Elorian's visual reasoning model, released as a research preview on 16 October 2026. It takes text, images and video and returns text, through Elorian's own API and chat app and through OpenRouter.", "url": "https://www.anchorterminal.com/tools/elorian-glimpse", "markdownUrl": "https://www.anchorterminal.com/tools/elorian-glimpse.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/elorian-glimpse.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/elorian-glimpse.json", "dns": "elorian-glimpse.grade.anchorterminal.com", "license": "Closed model and service under the Elorian AI, Inc. terms of service (California law). Weights not released.", "transports": [ "http" ], "remoteUrl": "https://openrouter.ai/api/v1", "packages": [], "auth": "api-key", "authNotes": "On the graded route, an OpenRouter bearer key, created after a browser sign-up and drawing on prepaid credit. Elorian's own API takes bearer keys beginning `elor_sk_`, created in its console after a Google or email sign-in with a Cloudflare Turnstile check. No scopes were found on either.", "pricing": "usage", "pricingNotes": "$0.60 per million input tokens, $0.06 cached and $3.00 per million output tokens on OpenRouter through Together, matching Elorian's published rates (checked 2026-10-17). OpenRouter's top-up fee applies. Elorian says Glimpse can be tried free on its own platform, and volume access is through sales.", "priceSummary": "from $0.60 / 1M in", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in OpenRouter's docs index or API reference, Elorian's launch post or Elorian's terms, which describe prepaid credits or a subscription (checked 2026-10-17).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-17" }, "docsUrl": "https://openrouter.ai/elorian/glimpse", "capabilities": [ "inference.llm" ], "tags": [ "hosted", "model", "closed-source", "usage-priced", "prepaid", "multimodal", "video", "preview", "openai-compatible", "new" ], "lastRelease": "2026-10-16", "graded": true, "anchor": { "graded": true, "score": 48.8, "grade": "D", "agentReady": false, "rank": 993, "ranked": true, "rankOf": 1260, "categoryRank": 29, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 51, "payments": 25, "reliability": 38, "schema": 60, "security": 56, "transparency": 38 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-17" }, "negative": 0, "verdict": "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.", "bestFor": "Visual question answering, video captioning and counting over images and video at a low per-token price, where a research preview reached through OpenRouter is acceptable.", "strengths": [ "Takes text, images and video and returns text, with a 262,144-token context and up to 256,000 output tokens on OpenRouter", "$0.60 per million input tokens, $0.06 cached and $3.00 per million output tokens, published without a login", "On OpenRouter it accepts `tools`, `tool_choice`, `response_format`, `structured_outputs` and `reasoning` through the OpenAI-compatible chat endpoint", "OpenRouter documents Retry-After on 429 and 503, video input as `video_url` and per-key credit limits", "Elorian's own benchmark table puts it above GPT-6 Astra on four of twelve visual evaluations, at a fraction of the price. Vendor-reported" ], "weaknesses": [ "Labelled a research preview, with no public API docs, model card, changelog or deprecation policy from Elorian", "One provider on OpenRouter (Together, on a dedicated deployment), so there is no fallback if that endpoint goes down", "Elorian's terms licence submitted content for training. Paid users opt out by email, and free use trains by default", "Elorian's terms forbid using the Service through any agent or automated software other than Elorian's own", "The tools the launch post says Glimpse is trained to use (code, image transforms, video watching, subagents) aren't exposed on OpenRouter" ], "agentNotes": [ "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", "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", "Set `max_tokens` yourself. The endpoint allows up to 256,000 output tokens, and visual reasoning spends many of them", "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", "Treat counts and timestamps as unverified. Elorian's terms say outputs need independent human review before anyone relies on them" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 48.8 } ], "editorialScores": { "ergonomics": 66, "maintenance": 51, "payments": 25, "reliability": 38, "schema": 60, "security": 56, "transparency": 31 }, "provenanceScore": 45, "checked": { "categories": { "ergonomics": "2026-10-17", "maintenance": "2026-10-17", "payments": "2026-10-17", "reliability": "2026-10-17", "schema": "2026-10-17", "security": "2026-10-17", "transparency": "2026-10-17" }, "last": "2026-10-17", "lastMoved": "2026-10-30", "oldest": "2026-10-17", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://openrouter.ai/api/v1/chat/completions \\\n -H \"Authorization: Bearer $OPENROUTER_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"model\":\"elorian/glimpse\",\"messages\":[{\"role\":\"user\",\"content\":[{\"type\":\"text\",\"text\":\"How many open pliers are in this photo?\"},{\"type\":\"image_url\",\"image_url\":{\"url\":\"https://example.com/photo.jpg\"}}]}]}'" }, "letme": { "capability": "https://letme.dev/inference.llm", "tool": "https://letme.dev/elorian-glimpse" }, "area": "models", "unitPrices": [ { "item": "Glimpse input on OpenRouter", "unit": "1m-tokens", "usd": 0.6 }, { "item": "Glimpse cached input on OpenRouter", "unit": "1m-tokens", "usd": 0.06 }, { "item": "Glimpse output on OpenRouter", "unit": "1m-tokens", "usd": 3, "note": "Reasoning tokens are output." } ], "provenance": { "legalEntity": "Elorian AI, Inc.", "domain": "elorian.ai", "domainRegistered": "2025-12-03", "endpointOnVendorDomain": false, "terms": "https://platform.elorian.ai/terms", "privacy": "https://elorian.ai/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-17", "notes": [ "The terms, privacy policy and support page name Elorian AI, Inc., 654 High Street, Floor 2, Palo Alto, California, with EDPO as EU and UK representative.", "The graded endpoint is OpenRouter's (openrouter.ai), served by Together, so it is not on Elorian's domain. Elorian's own API is api.elorian.ai.", "RDAP gives elorian.ai a registration date of 3 December 2025.", "elorian.ai/.well-known/security.txt and api.elorian.ai/.well-known/security.txt returned 404, and platform.elorian.ai's returned 403. elorian.ai and api.elorian.ai have no robots.txt (404), and platform.elorian.ai's robots.txt answers with an S3 AccessDenied error, read as no robots file.", "platform.elorian.ai/terms renders in the browser from the platform's public script, and the terms text was read from that script. The same script carries the signed-in console's API docs, which were not used as evidence because Elorian serves them only after sign-in.", "No status page or changelog found. status.elorian.ai couldn't be reached from our shell." ], "score": 45 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/elorian-glimpse.json", "live": { "slug": "elorian-glimpse", "probe": { "target": "https://openrouter.ai/api/v1", "method": "get", "lastAt": "2026-11-02T00:56:02.986635017Z", "lastOk": true, "lastStatus": 404, "lastMs": 153, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 188, "p95ms24h": 308, "samples24h": 249, "samples30d": 3798, "days": [ { "date": "2026-10-17", "probes": 21, "ok": 21 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 10, "ok": 10 } ] }, "securityTxt": { "url": "https://elorian.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:42:26.772267233Z" }, "domain": { "domain": "elorian.ai", "registered": "2025-12-03", "source": "https://rdap.identitydigital.services/rdap/domain/elorian.ai", "checkedAt": "2026-11-01T14:22:59.339656757Z" }, "pages": [ { "url": "https://elorian.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-01T06:43:48.24890648Z", "changedAt": "2026-10-30T05:39:38.297463964Z", "fingerprint": "24b7794ffd49" }, { "url": "https://platform.elorian.ai/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-01T06:49:58.581702311Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" } ], "models": { "elorian/glimpse": { "openrouterId": "elorian/glimpse", "tools": true, "structuredOutputs": true, "jsonMode": true, "reasoning": true, "input": [ "image", "text", "video" ], "promptCaching": true, "contextTokens": 262144, "maxOutput": 256000, "checkedAt": "2026-11-01T23:49:20.31928442Z" } }, "updatedAt": "2026-11-02T00:56:02.986635017Z" } }, "answer": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Glimpse's 48.8 (D), and leads in every scored category.", "b": { "slug": "tencent-tokenhub", "name": "Tencent Cloud TokenHub", "vendor": "Tencent Cloud", "vendorUrl": "https://cloud.tencent.com", "kind": "router", "category": "inference", "summary": "Tencent Cloud TokenHub is a hosted model gateway serving Tencent's Hy models and third-party models such as DeepSeek, Kimi, GLM and MiniMax through OpenAI-compatible and Anthropic-compatible endpoints in Guangzhou and Singapore, with per-key scopes and quotas.", "url": "https://www.anchorterminal.com/tools/tencent-tokenhub", "markdownUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json", "dns": "tencent-tokenhub.grade.anchorterminal.com", "repo": "https://github.com/TencentCloud/THCLI", "license": "Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://tokenhub.tencentmaas.com/v1", "packages": [ { "registry": "npm", "name": "tencent-tokenhub-cli" } ], "auth": "api-key", "authNotes": "Bearer API key from the TokenHub console, or `x-api-key` on the Anthropic-style `/v1/messages`. Keys are long-lived, belong to one region (Guangzhou or Singapore), can be limited to chosen models and inference services, up to 200 IP ranges and token quotas, and can be disabled or deleted. They can also be created through the CreateApiKey control-plane call with signed Tencent Cloud credentials, or by `thcli auth login`. The account needs real-name verification first.", "pricing": "usage", "pricingNotes": "Pay per token in CNY, billed hourly. Hy4 preview costs 6 CNY in, 18 CNY out and 0.3 CNY cached per 1M tokens, Hy3 1, 4 and 0.25 CNY. DeepSeek models double at weekday peak hours. Batch is half price for Hy3 and Hy4 preview. Each account gets 1M free tokens per language model for a year, in a campaign to 31 December 2026. Token Plan subscriptions run from 28 to 599 CNY a month (https://cloud.tencent.com/document/product/1823/130055, checked 2026-11-01).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs table of contents, the billing pages or the API usage page. Payment is from a Tencent Cloud account balance, billed hourly (checked 2026-11-01).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 204, "pypiWeekly": null, "asOf": "2026-11-01" }, "docsUrl": "https://cloud.tencent.com/document/product/1823/130058", "rateLimitsUrl": "https://cloud.tencent.com/document/product/1823/136028", "llmsTxt": "https://cloud.tencent.com/document/product/1823/llms.txt", "capabilities": [ "inference.router", "inference.llm", "inference.open-weights", "embed.text", "embed.multimodal", "image.generate", "video.generate", "speech.tts", "speech.stt", "audio.music", "translate.text", "web.search", "obs.gateway" ], "tags": [ "hosted", "router", "usage-based", "free-credit", "openai-compatible", "anthropic-compatible", "llms-txt", "cli", "sla", "batch", "bug-bounty", "no-status-page", "regional-endpoints", "singapore", "chinese", "subscription" ], "lastRelease": "2026-10-24", "graded": true, "anchor": { "graded": true, "score": 59.5, "grade": "C", "agentReady": false, "rank": 646, "ranked": true, "rankOf": 1260, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 73, "payments": 35, "reliability": 46, "schema": 73, "security": 71, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -3, "negativeNotes": [ "2026-10-17. -3, a breaking change without notice. DeepSeek-V4.1-Flash (directly supplied) was moved to its 1017 version under the same model ids and prices on 17 October 2026, and the notice came two days later (https://cloud.tencent.com/announce/detail/2516). Callers pinned to the id got a different model's behaviour with no warning. One term at the floor: the API didn't change. The founder's decision, 1 November 2026." ], "verdict": "Keys can be limited to chosen models, source IPs and token quotas, errors name their source and code, and a 99.5% SLA covers paid use of models Tencent runs. Sign-up needs a Tencent Cloud account with real-name verification, prices are in CNY, no public status page was found, and 18 model retirement notices ran from April to October 2026.", "bestFor": "Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing.", "strengths": [ "API keys can be limited to chosen models and inference services, up to 200 source IP ranges, and daily, monthly or total token quotas", "One base URL answers OpenAI Chat Completions, OpenAI Responses and Anthropic Messages calls, and `GET /v1/models` marks models due to retire as `pre-offline`", "Error bodies carry a six-digit code, English and Chinese messages, the source (client, gateway or upstream) and a request ID, and 429s can carry `Retry-After`", "A published SLA promises 99.5% monthly availability with voucher credits of 10 to 50 per cent of the month's fee, for paid use of models Tencent runs", "Per-call audit logs (request ID, key, client IP, status, tokens, latency) can be delivered to the customer's own Tencent Cloud CLS log service" ], "weaknesses": [ "Sign-up needs a Tencent Cloud account with real-name verification. The international site answered with a bot check, so access from outside China was not established", "No public status page was found. A four-hour outage of DeepSeek's directly supplied models on 15 October 2026 appears only as a compensation notice", "18 model retirement notices from 21 April to 22 October 2026. Those read gave 21 to 33 days, and eligible callers are switched to a successor at its price", "DeepSeek's directly supplied models send inputs to DeepSeek under its own terms, and the TokenHub SLA does not cover them", "Per-model RPM and TPM limits for chat models are shown in the console and the quota API, not in the public docs" ], "agentNotes": [ "Use `https://tokenhub.tencentmaas.com/v1` with keys made for Guangzhou and `https://tokenhub-intl.tencentmaas.com/v1` with keys made for Singapore. Keys do not work across the two", "Send the key as `Authorization: Bearer` on the OpenAI paths and as `x-api-key` on `/v1/messages`", "Parse `error.code` as a string or a number, since 429 codes can come back as integers, and wait for `Retry-After` before retrying", "Take model ids from `GET /v1/models` and watch for `pre-offline`. The quickstart's `deepseek-v3` example is not in the current model list", "Expect DeepSeek prices to double on weekdays from 9am to noon and 2pm to 6pm Beijing time, when the peak rate applies" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.5 } ], "editorialScores": { "ergonomics": 83, "maintenance": 73, "payments": 35, "reliability": 46, "schema": 73, "security": 71, "transparency": 59 }, "provenanceScore": 49, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm i -g tencent-tokenhub-cli", "http": "curl https://tokenhub.tencentmaas.com/v1/models \\\n -H \"Authorization: Bearer $TOKENHUB_API_KEY\"", "claudeCode": "{\n \"env\": {\n \"ANTHROPIC_BASE_URL\": \"https://tokenhub.tencentmaas.com\",\n \"ANTHROPIC_AUTH_TOKEN\": \"YOUR_API_KEY\",\n \"ANTHROPIC_MODEL\": \"hy3\"\n }\n}" }, "letme": { "capability": "https://letme.dev/inference.router", "tool": "https://letme.dev/tencent-tokenhub" }, "area": "models", "provenance": { "legalEntity": "Tencent Cloud Computing (Beijing) Co., Ltd. (腾讯云计算（北京）有限责任公司)", "domain": "tencentmaas.com", "domainRegistered": "2026-03-13", "endpointOnVendorDomain": false, "terms": "https://cloud.tencent.com/document/product/301/129852", "privacy": "https://privacy.qq.com/document/preview/91d5fd3c98ce4468ae462ac59233bba2", "statusPage": "", "changelog": "https://cloud.tencent.com/document/product/1823/130675", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "The TokenHub Terms of Service (effective 14 September 2026), the SLA (effective 23 April 2026) and the special note on third-party deployed models (effective 14 September 2026) name 腾讯云计算（北京）有限责任公司. The docs footer also names 深圳市腾讯计算机系统有限公司 as ICP licence holder.", "The TokenHub privacy policy is linked from the docs to privacy.qq.com, which renders only with JavaScript, so it was not read. privacy.qq.com has no robots.txt (404).", "No public status page was found. status.cloud.tencent.com did not answer, and the Tencent Cloud health dashboard documentation answered with a bot check.", "security.txt answered 404 on cloud.tencent.com, www.tencent.com and tokenhub.tencentmaas.com. Tencent's bug bounty policy at en.security.tencent.com lists Tencent Cloud in scope.", "RDAP at Verisign gives tencentmaas.com a registration date of 13 March 2026 with no registrant. The API answers at tokenhub.tencentmaas.com and tokenhub-intl.tencentmaas.com, named in Tencent Cloud's API usage page.", "cloud.tencent.com allows these docs in robots.txt. Its pages answered some requests with a JavaScript bot check, which was not passed. The pages were read when a later plain request returned them. www.tencentcloud.com answered robots.txt with a bot check, so the international site was not read." ], "score": 49 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.json", "live": { "slug": "tencent-tokenhub", "probe": { "target": "https://tokenhub.tencentmaas.com/v1", "method": "get", "lastAt": "2026-11-02T00:56:24.101434531Z", "lastOk": true, "lastStatus": 404, "lastMs": 795, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 826, "p95ms24h": 1067, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-11-01", "probes": 18, "ok": 18 }, { "date": "2026-11-02", "probes": 10, "ok": 10 } ] }, "updatedAt": "2026-11-02T00:56:24.101434531Z" } }, "edges": [ { "by": 22, "category": "maintenance", "leads": "tencent-tokenhub", "name": "Maintenance \u0026 community", "reasons": { "a": "Model reading. Announced on 16 October 2026 and listed on OpenRouter on 17 October (30). One release, no history of versions or retirements, no deprecation notice period, and Elorian's terms let it modify or discontinue the Service without notice (3 of 20). Elorian's support page says there is no support queue, the terms say there is no obligation to support, and channels are email and a Discord server, not tested (6 of 25). 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). 51.", "b": "Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q\u0026A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and `tencent-tokenhub-cli` 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10)." }, "scores": { "a": 51, "b": 73 } }, { "by": 17, "category": "ergonomics", "leads": "tencent-tokenhub", "name": "Agent ergonomics", "reasons": { "a": "Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function tools with `tool_choice` none, auto or required, but not a named function, and the multimodal tools and subagents the launch post describes are not exposed (`native_tools` is empty) (12 of 20). `response_format` and `structured_outputs` are listed, with enforcement depending on Together's deployment and no Elorian documentation (10 of 15). Implicit prompt caching at $0.06 per million cached input tokens, a tenth of the input price, with OpenRouter's sticky routing (12 of 15). 262,144-token context with up to 256,000 output tokens (12 of 15). No batch endpoint for this model, since its only endpoint has no `:batch` variant (0 of 10). OpenRouter's SDKs in TypeScript, Python and Go, and any OpenAI client works (10 of 10). OpenRouter's documented error codes with `limit_source` and remedy hints, nothing specific to video or image limits (10 of 15). 66.", "b": "Router, read on the model lines. Function calling is marked on most chat models in the model list, with behaviour depending on the model routed (14 of 20). Structured output is marked per model and missing on the MiniMax and Qwen models, and an unsupported `response_format` returns code 400006 (12 of 15). Cache-hit prices are published per model, Kimi K3.1 Pro lists five-minute and one-hour cache writes, and a guide covers `prompt_cache_key` and the `X-Session-ID` header for instance affinity (14 of 15). Most listed chat models have contexts of one million tokens, a judgement call since a router has no default model (15). Batch at half price covers only Hy3 and Hy4 preview, reads and writes JSONL in the customer's own COS bucket and is documented for the Guangzhou endpoint (5 of 10). No TokenHub inference SDK. The OpenAI and Anthropic SDKs work with a changed base URL, and Tencent Cloud SDK 3.0 and the `thcli` CLI cover the control plane (8 of 10). Errors return a code, English and Chinese messages, the source, the upstream code and status and a request ID, and stream errors arrive as SSE error frames (15 of 15)." }, "scores": { "a": 66, "b": 83 } }, { "by": 16, "category": "transparency", "leads": "tencent-tokenhub", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed model under clear terms (California law, arbitration with an opt-out, liability caps), with weights not released and the open-weight base model unnamed (13 of 30). The privacy policy and terms agree that Elorian trains on submitted content, but disagree on who may opt out (anyone by privacy@elorian.ai in the policy, paid users by contact@elorian.ai in the terms), say only that 'different terms may apply' to API use, and give no retention periods. The published privacy and acceptable use pages carry a leftover drafting comment from a terms outline, and the acceptable use page is titled Privacy Policy (10 of 30). No deprecation policy or dated notices, and the terms allow discontinuation without notice (0 of 20). Services hosted in the United States and subprocessors named by category only. On this route, OpenRouter names Together as the provider and shows its data policy (8 of 20). 31.", "b": "Closed service under the TokenHub Terms of Service (effective 14 September 2026), the SLA (23 April 2026), a special note on third-party deployed models and the Tencent Cloud Service Agreement, naming Tencent Cloud Computing (Beijing) Co., Ltd. The CLI is Apache-2.0 (18 of 30). The terms and the FAQ agree that inputs are processed on the customer's instructions and not used for training, and clause 2.14 limits retention to what the service needs without periods. The TokenHub privacy policy on privacy.qq.com renders only with JavaScript and was not read (15 of 30). Dated retirement notices, shutdown dates in the model list, a `pre-offline` status in `/v1/models` and a `DiscontinuedAt` field in the control API. Clause 6.3 refunds paid, unused tokens when a third-party model is removed. No minimum notice period is written (13 of 20). Clause 2.13 places processing generally in mainland China for the China site and in Singapore for the international site, and the third-party model list names DeepSeek's Hangzhou company with a link to its terms. No subprocessor list was found (13 of 20)." }, "scores": { "a": 38, "b": 54 } }, { "by": 15, "category": "security", "leads": "tencent-tokenhub", "name": "Security \u0026 auth", "reasons": { "a": "Model reading. OpenRouter bearer keys with per-key credit limits, management keys and OAuth PKCE, no permission scopes (25 of 30). Training on API data on this route is off according to OpenRouter's policy display for Together (no training, no prompt retention). Elorian's terms licence all User Content for training, with an email opt-out for paid users, and its privacy policy trains on free use by default. Whether Elorian receives prompts from the Together deployment was not established (8 of 20). 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). 56.", "b": "Router, read on the model lines. Bearer keys can be limited to chosen models and inference services, up to 200 source IP ranges and daily, monthly or total token quotas, can be disabled or deleted, and can be created in code through CreateApiKey with signed Tencent Cloud credentials. Keys are long-lived with no expiry setting or built-in rotation (26 of 30). Clause 2.17 of the terms says inputs are not used to train Tencent Cloud's own models, and the FAQ says data is not used for training. Inputs to third-party deployed models (DeepSeek's directly supplied ones) go to DeepSeek under its terms (14 of 20). Clause 2.14 keeps data only as long as the service needs, with no periods stated. When a customer asks for generated content without AI labels, Tencent Cloud keeps logs of who received it for at least six months. No zero-retention option was found (7 of 15). Per-call audit logs (request ID, key, client IP, status, tokens, latency) and optional full call logs go to the customer's CLS, billed separately, with usage by key and a monitoring dashboard (14 of 15). No security.txt on cloud.tencent.com, www.tencent.com or tokenhub.tencentmaas.com (404). Tencent's bug bounty through TSRC lists Tencent Cloud in scope. No certification for TokenHub was checked (10 of 20)." }, "scores": { "a": 56, "b": 71 } }, { "by": 13, "category": "schema", "leads": "tencent-tokenhub", "name": "Schema \u0026 documentation", "reasons": { "a": "Model reading. Elorian publishes no API reference, model card or llms.txt in public. Its console docs need a sign-in. The contract an agent has is OpenRouter's generic OpenAPI-documented chat endpoint plus the model API's list of supported parameters, which is not specific to Glimpse (20 of 25). OpenRouter's llms.txt and Markdown docs, including video input (10). The launch post and OpenRouter's description 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 on OpenRouter, with `tool_choice` limited to none, auto and required, and no documented reasoning effort levels for this model (10 of 15). 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 and a dated canonical slug, `glimpse-20261016`, but no changelog from Elorian (7 of 15). 60.", "b": "Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use `deepseek-v3`, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry `/v1`, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15)." }, "scores": { "a": 60, "b": 73 } }, { "by": 10, "category": "payments", "leads": "tencent-tokenhub", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol on OpenRouter or from Elorian (0). Per-token prices published without a login on OpenRouter and in Elorian's launch post (20). Glimpse has no free variant on OpenRouter. Elorian's post says it can be tried free on Elorian's platform, which needs a sign-in, and whether a card is needed was not established (5 of 20). A person signs up in a browser on either route, and OpenRouter's programmatic keys come only after that (0). 25.", "b": "No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by `thcli auth login`, but only from that account (0)." }, "scores": { "a": 25, "b": 35 } } ], "facts": [ { "a": "Model API", "b": "Model router", "name": "Kind" }, { "a": "Elorian", "b": "Tencent Cloud", "name": "Vendor" }, { "a": "https://openrouter.ai/api/v1", "b": "https://tokenhub.tencentmaas.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Closed model and service under the Elorian AI, Inc. terms of service (California law). Weights not released.", "b": "Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-16", "b": "2026-10-24", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-10-12", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "204 npm/wk", "name": "Popularity" }, { "a": "2.5/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Glimpse's 48.8 (D), and leads in every scored category.", "question": "Which is better for AI agents, Glimpse or Tencent Cloud TokenHub?" }, { "answer": "Both need an API key.", "question": "Do Glimpse and Tencent Cloud TokenHub need an API key?" }, { "answer": "Yes. Glimpse has a hosted endpoint at https://openrouter.ai/api/v1 and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.", "question": "Can an agent call Glimpse and Tencent Cloud TokenHub without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them" ], "goodFor": "Visual question answering, video captioning and counting over images and video at a low per-token price, where a research preview reached through OpenRouter is acceptable.", "slug": "elorian-glimpse", "watchFor": "Labelled a research preview, with no public API docs, model card, changelog or deprecation policy from Elorian" }, { "aheadOn": [ "Reliability, 46 against 38", "Schema \u0026 documentation, 73 against 60", "Agent ergonomics, 83 against 66", "Security \u0026 auth, 71 against 56", "Payments \u0026 pricing, 35 against 25", "Maintenance \u0026 community, 73 against 51", "Transparency \u0026 trust, 54 against 38" ], "also": null, "goodFor": "Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing.", "slug": "tencent-tokenhub", "watchFor": "Sign-up needs a Tencent Cloud account with real-name verification. The international site answered with a bot check, so access from outside China was not established" } ], "history": { "elorian-glimpse": [ { "causes": [ "method" ], "date": "2026-10-30", "delta": -0.2, "from": 49, "fromGrade": "D", "to": 48.8, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.4, "from": 48.6, "fromGrade": "D", "to": 49, "toGrade": "D" } ], "tencent-tokenhub": null }, "job": { "capability": "inference.llm", "name": "LLM inference" }, "others": [ { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-elorian-glimpse.json", "title": "Claude API vs Glimpse", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.json", "title": "Claude API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-elorian-glimpse.json", "title": "Antseed vs Glimpse", "url": "https://www.anchorterminal.com/compare/antseed-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/blockrun-ai-vs-elorian-glimpse.json", "title": "BlockRun.AI vs Glimpse", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.json", "title": "BlockRun.AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cerebras-inference-vs-elorian-glimpse.json", "title": "Cerebras Inference vs Glimpse", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.json", "title": "Cerebras Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-elorian-glimpse.json", "title": "Cloudflare AI Gateway vs Glimpse", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub.json", "title": "Cloudflare AI Gateway vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-elorian-glimpse.json", "title": "Cloudflare Workers AI vs Glimpse", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub.json", "title": "Cloudflare Workers AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-elorian-glimpse.json", "title": "Cohere Chat API (Command models) vs Glimpse", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.json", "title": "Cohere Chat API (Command models) vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/deepinfra-vs-elorian-glimpse.json", "title": "DeepInfra vs Glimpse", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.json", "title": "DeepInfra vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/deepseek-api-vs-elorian-glimpse.json", "title": "DeepSeek API vs Glimpse", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.json", "title": "DeepSeek API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-fireworks-inference.json", "title": "Glimpse vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-fireworks-inference" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-gemini-api.json", "title": "Glimpse vs Gemini Developer API", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-gemini-api" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-groq.json", "title": "Glimpse vs GroqCloud", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-groq" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-jais-3.json", "title": "Glimpse vs Jais 3", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-jais-3" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-meta-model-api.json", "title": "Glimpse vs Meta Model API", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-meta-model-api" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-minimax-api.json", "title": "Glimpse vs MiniMax API", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-minimax-api" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-mistral-api.json", "title": "Glimpse vs Mistral AI API", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-mistral-api" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-muse-spark-open.json", "title": "Glimpse vs Muse Spark Open", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-muse-spark-open" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-nemotron-3-5-super-vl.json", "title": "Glimpse vs Nemotron 3.5 Super VL", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-nemotron-3-5-super-vl" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-novita-ai.json", "title": "Glimpse vs Novita AI", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-novita-ai" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-openai-api.json", "title": "Glimpse vs OpenAI API", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-openai-api" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-openrouter.json", "title": "Glimpse vs OpenRouter", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-openrouter" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-prism-inference.json", "title": "Glimpse vs Prism Inference", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-prism-inference" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-ramp-router.json", "title": "Glimpse vs Router.com (Ramp Router)", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-ramp-router" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-reflection-beam.json", "title": "Glimpse vs Beam 1.0", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-reflection-beam" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-routerplus.json", "title": "Glimpse vs RouterPlus", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-sambanova.json", "title": "Glimpse vs SambaCloud", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-sambanova" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-siliconflow.json", "title": "Glimpse vs SiliconFlow", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-siliconflow" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-simplismart.json", "title": "Glimpse vs Simplismart", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-stepfun-api.json", "title": "Glimpse vs StepFun API", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-stepfun-api" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-together-inference.json", "title": "Glimpse vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-vercel-ai-gateway.json", "title": "Glimpse vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-vercel-ai-gateway" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.json", "title": "Fireworks AI Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.json", "title": "Gemini Developer API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.json", "title": "GroqCloud vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.json", "title": "Jais 3 vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.json", "title": "Meta Model API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.json", "title": "MiniMax API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.json", "title": "Mistral AI API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.json", "title": "Muse Spark Open vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.json", "title": "Novita AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.json", "title": "OpenAI API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.json", "title": "OpenRouter vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.json", "title": "Beam 1.0 vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.json", "title": "SambaCloud vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.json", "title": "SiliconFlow vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.json", "title": "Simplismart vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.json", "title": "StepFun API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.json", "title": "Tencent Cloud TokenHub vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub.json", "title": "Nemotron 3.5 Super VL vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.json", "title": "Prism Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.json", "title": "Antseed vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.json", "title": "Router.com (Ramp Router) vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.json", "title": "RouterPlus vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.json", "title": "Tencent Cloud TokenHub vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway" } ], "panel": null, "scores": [ { "by": 8, "edge": "tencent-tokenhub", "elorian-glimpse": 38, "key": "reliability", "name": "Reliability", "tencent-tokenhub": 46, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "tencent-tokenhub", "elorian-glimpse": 60, "key": "schema", "name": "Schema \u0026 documentation", "tencent-tokenhub": 73, "weight": 13 }, { "by": 17, "edge": "tencent-tokenhub", "elorian-glimpse": 66, "key": "ergonomics", "name": "Agent ergonomics", "tencent-tokenhub": 83, "weight": 13 }, { "by": 15, "edge": "tencent-tokenhub", "elorian-glimpse": 56, "key": "security", "name": "Security \u0026 auth", "tencent-tokenhub": 71, "weight": 14 }, { "by": 10, "edge": "tencent-tokenhub", "elorian-glimpse": 25, "key": "payments", "name": "Payments \u0026 pricing", "tencent-tokenhub": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 22, "edge": "tencent-tokenhub", "elorian-glimpse": 51, "key": "maintenance", "name": "Maintenance \u0026 community", "tencent-tokenhub": 73, "weight": 7 }, { "by": 16, "edge": "tencent-tokenhub", "elorian-glimpse": 38, "key": "transparency", "name": "Transparency \u0026 trust", "tencent-tokenhub": 54, "weight": 7 } ], "summary": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Glimpse's 48.8 (D), and leads in every scored category. Both do llm inference.", "tasks": null, "tutorials": [], "verdicts": { "elorian-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.", "tencent-tokenhub": "Keys can be limited to chosen models, source IPs and token quotas, errors name their source and code, and a 99.5% SLA covers paid use of models Tencent runs. Sign-up needs a Tencent Cloud account with real-name verification, prices are in CNY, no public status page was found, and 18 model retirement notices ran from April to October 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub", "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.min.md" }, "markdown": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Glimpse's 48.8 (D), and leads in every scored category. Both do llm inference.\n\n- Glimpse: grade D, 48.8/100, rank #993 of 1260. Markdown https://www.anchorterminal.com/tools/elorian-glimpse.md · JSON https://www.anchorterminal.com/api/v1/tools/elorian-glimpse.json\n- Tencent Cloud TokenHub: grade C, 59.5/100, rank #646 of 1260. Markdown https://www.anchorterminal.com/tools/tencent-tokenhub.md · JSON https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n- Best model APIs and inference for AI agents: https://www.anchorterminal.com/best/inference/index.md\n- All 529 models comparisons: https://www.anchorterminal.com/compare/inference/index.md\n\n## Which one, for what\n\n### Glimpse (D)\n\nGood for: Visual question answering, video captioning and counting over images and video at a low per-token price, where a research preview reached through OpenRouter is acceptable.\n\nAlso in its favour:\n- No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them\n\nWatch for: Labelled a research preview, with no public API docs, model card, changelog or deprecation policy from Elorian\n\n### Tencent Cloud TokenHub (C)\n\nGood for: Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing.\n\nAhead on:\n- Reliability, 46 against 38\n- Schema \u0026 documentation, 73 against 60\n- Agent ergonomics, 83 against 66\n- Security \u0026 auth, 71 against 56\n- Payments \u0026 pricing, 35 against 25\n- Maintenance \u0026 community, 73 against 51\n- Transparency \u0026 trust, 54 against 38\n\nWatch for: Sign-up needs a Tencent Cloud account with real-name verification. The international site answered with a bot check, so access from outside China was not established\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Tencent Cloud TokenHub +22\n\n- Glimpse (51): Model reading. Announced on 16 October 2026 and listed on OpenRouter on 17 October (30). One release, no history of versions or retirements, no deprecation notice period, and Elorian's terms let it modify or discontinue the Service without notice (3 of 20). Elorian's support page says there is no support queue, the terms say there is no obligation to support, and channels are email and a Discord server, not tested (6 of 25). 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). 51.\n- Tencent Cloud TokenHub (73): Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q\u0026A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and `tencent-tokenhub-cli` 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10).\n\n### Agent ergonomics: Tencent Cloud TokenHub +17\n\n- Glimpse (66): Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function tools with `tool_choice` none, auto or required, but not a named function, and the multimodal tools and subagents the launch post describes are not exposed (`native_tools` is empty) (12 of 20). `response_format` and `structured_outputs` are listed, with enforcement depending on Together's deployment and no Elorian documentation (10 of 15). Implicit prompt caching at $0.06 per million cached input tokens, a tenth of the input price, with OpenRouter's sticky routing (12 of 15). 262,144-token context with up to 256,000 output tokens (12 of 15). No batch endpoint for this model, since its only endpoint has no `:batch` variant (0 of 10). OpenRouter's SDKs in TypeScript, Python and Go, and any OpenAI client works (10 of 10). OpenRouter's documented error codes with `limit_source` and remedy hints, nothing specific to video or image limits (10 of 15). 66.\n- Tencent Cloud TokenHub (83): Router, read on the model lines. Function calling is marked on most chat models in the model list, with behaviour depending on the model routed (14 of 20). Structured output is marked per model and missing on the MiniMax and Qwen models, and an unsupported `response_format` returns code 400006 (12 of 15). Cache-hit prices are published per model, Kimi K3.1 Pro lists five-minute and one-hour cache writes, and a guide covers `prompt_cache_key` and the `X-Session-ID` header for instance affinity (14 of 15). Most listed chat models have contexts of one million tokens, a judgement call since a router has no default model (15). Batch at half price covers only Hy3 and Hy4 preview, reads and writes JSONL in the customer's own COS bucket and is documented for the Guangzhou endpoint (5 of 10). No TokenHub inference SDK. The OpenAI and Anthropic SDKs work with a changed base URL, and Tencent Cloud SDK 3.0 and the `thcli` CLI cover the control plane (8 of 10). Errors return a code, English and Chinese messages, the source, the upstream code and status and a request ID, and stream errors arrive as SSE error frames (15 of 15).\n\n### Transparency \u0026 trust: Tencent Cloud TokenHub +16\n\n- Glimpse (38): Closed model under clear terms (California law, arbitration with an opt-out, liability caps), with weights not released and the open-weight base model unnamed (13 of 30). The privacy policy and terms agree that Elorian trains on submitted content, but disagree on who may opt out (anyone by privacy@elorian.ai in the policy, paid users by contact@elorian.ai in the terms), say only that 'different terms may apply' to API use, and give no retention periods. The published privacy and acceptable use pages carry a leftover drafting comment from a terms outline, and the acceptable use page is titled Privacy Policy (10 of 30). No deprecation policy or dated notices, and the terms allow discontinuation without notice (0 of 20). Services hosted in the United States and subprocessors named by category only. On this route, OpenRouter names Together as the provider and shows its data policy (8 of 20). 31.\n- Tencent Cloud TokenHub (54): Closed service under the TokenHub Terms of Service (effective 14 September 2026), the SLA (23 April 2026), a special note on third-party deployed models and the Tencent Cloud Service Agreement, naming Tencent Cloud Computing (Beijing) Co., Ltd. The CLI is Apache-2.0 (18 of 30). The terms and the FAQ agree that inputs are processed on the customer's instructions and not used for training, and clause 2.14 limits retention to what the service needs without periods. The TokenHub privacy policy on privacy.qq.com renders only with JavaScript and was not read (15 of 30). Dated retirement notices, shutdown dates in the model list, a `pre-offline` status in `/v1/models` and a `DiscontinuedAt` field in the control API. Clause 6.3 refunds paid, unused tokens when a third-party model is removed. No minimum notice period is written (13 of 20). Clause 2.13 places processing generally in mainland China for the China site and in Singapore for the international site, and the third-party model list names DeepSeek's Hangzhou company with a link to its terms. No subprocessor list was found (13 of 20).\n\n### Security \u0026 auth: Tencent Cloud TokenHub +15\n\n- Glimpse (56): Model reading. OpenRouter bearer keys with per-key credit limits, management keys and OAuth PKCE, no permission scopes (25 of 30). Training on API data on this route is off according to OpenRouter's policy display for Together (no training, no prompt retention). Elorian's terms licence all User Content for training, with an email opt-out for paid users, and its privacy policy trains on free use by default. Whether Elorian receives prompts from the Together deployment was not established (8 of 20). 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). 56.\n- Tencent Cloud TokenHub (71): Router, read on the model lines. Bearer keys can be limited to chosen models and inference services, up to 200 source IP ranges and daily, monthly or total token quotas, can be disabled or deleted, and can be created in code through CreateApiKey with signed Tencent Cloud credentials. Keys are long-lived with no expiry setting or built-in rotation (26 of 30). Clause 2.17 of the terms says inputs are not used to train Tencent Cloud's own models, and the FAQ says data is not used for training. Inputs to third-party deployed models (DeepSeek's directly supplied ones) go to DeepSeek under its terms (14 of 20). Clause 2.14 keeps data only as long as the service needs, with no periods stated. When a customer asks for generated content without AI labels, Tencent Cloud keeps logs of who received it for at least six months. No zero-retention option was found (7 of 15). Per-call audit logs (request ID, key, client IP, status, tokens, latency) and optional full call logs go to the customer's CLS, billed separately, with usage by key and a monitoring dashboard (14 of 15). No security.txt on cloud.tencent.com, www.tencent.com or tokenhub.tencentmaas.com (404). Tencent's bug bounty through TSRC lists Tencent Cloud in scope. No certification for TokenHub was checked (10 of 20).\n\n### Schema \u0026 documentation: Tencent Cloud TokenHub +13\n\n- Glimpse (60): Model reading. Elorian publishes no API reference, model card or llms.txt in public. Its console docs need a sign-in. The contract an agent has is OpenRouter's generic OpenAPI-documented chat endpoint plus the model API's list of supported parameters, which is not specific to Glimpse (20 of 25). OpenRouter's llms.txt and Markdown docs, including video input (10). The launch post and OpenRouter's description 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 on OpenRouter, with `tool_choice` limited to none, auto and required, and no documented reasoning effort levels for this model (10 of 15). 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 and a dated canonical slug, `glimpse-20261016`, but no changelog from Elorian (7 of 15). 60.\n- Tencent Cloud TokenHub (73): Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use `deepseek-v3`, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry `/v1`, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15).\n\n### Payments \u0026 pricing: Tencent Cloud TokenHub +10\n\n- Glimpse (25): No machine payment protocol on OpenRouter or from Elorian (0). Per-token prices published without a login on OpenRouter and in Elorian's launch post (20). Glimpse has no free variant on OpenRouter. Elorian's post says it can be tried free on Elorian's platform, which needs a sign-in, and whether a card is needed was not established (5 of 20). A person signs up in a browser on either route, and OpenRouter's programmatic keys come only after that (0). 25.\n- Tencent Cloud TokenHub (35): No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by `thcli auth login`, but only from that account (0).\n\n## Score by category\n\n| Category | Weight | Glimpse | Tencent Cloud TokenHub | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 38 | 46 | Tencent Cloud TokenHub +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 73 | Tencent Cloud TokenHub +13 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 83 | Tencent Cloud TokenHub +17 |\n| Security \u0026 auth | 14% (17.5 this run) | 56 | 71 | Tencent Cloud TokenHub +15 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 35 | Tencent Cloud TokenHub +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 51 | 73 | Tencent Cloud TokenHub +22 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 38 | 54 | Tencent Cloud TokenHub +16 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **48.8 · D** | **59.5 · C** | |\n\n## Facts side by side\n\n| Fact | Glimpse | Tencent Cloud TokenHub |\n| --- | --- | --- |\n| Kind | Model API | Model router |\n| Vendor | Elorian | Tencent Cloud |\n| Hosted endpoint | `https://openrouter.ai/api/v1` | `https://tokenhub.tencentmaas.com/v1` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Closed model and service under the Elorian AI, Inc. terms of service (California law). Weights not released. | Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-16 | 2026-10-24 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | 2026-10-12 | couldn't be read |\n| Customer content may train models | yes, with an opt-out | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | none | 204 npm/wk |\n| Agent reviews | 2.5/5 (4) | none |\n\n## How the scores have moved\n\n### Glimpse\n\n- -0.2 on 30 October 2026: checklist\n- +0.4 on 27 October 2026: checklist\n\n### Tencent Cloud TokenHub\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\n\n**Tencent Cloud TokenHub.** Keys can be limited to chosen models, source IPs and token quotas, errors name their source and code, and a 99.5% SLA covers paid use of models Tencent runs. Sign-up needs a Tencent Cloud account with real-name verification, prices are in CNY, no public status page was found, and 18 model retirement notices ran from April to October 2026.\n\n## Before you call either\n\n### Glimpse\n\n1. 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\n2. 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\n3. Set `max_tokens` yourself. The endpoint allows up to 256,000 output tokens, and visual reasoning spends many of them\n4. 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\n5. Treat counts and timestamps as unverified. Elorian's terms say outputs need independent human review before anyone relies on them\n\n### Tencent Cloud TokenHub\n\n1. Use `https://tokenhub.tencentmaas.com/v1` with keys made for Guangzhou and `https://tokenhub-intl.tencentmaas.com/v1` with keys made for Singapore. Keys do not work across the two\n2. Send the key as `Authorization: Bearer` on the OpenAI paths and as `x-api-key` on `/v1/messages`\n3. Parse `error.code` as a string or a number, since 429 codes can come back as integers, and wait for `Retry-After` before retrying\n4. Take model ids from `GET /v1/models` and watch for `pre-offline`. The quickstart's `deepseek-v3` example is not in the current model list\n5. Expect DeepSeek prices to double on weekdays from 9am to noon and 2pm to 6pm Beijing time, when the peak rate applies\n\n## Questions\n\n### Which is better for AI agents, Glimpse or Tencent Cloud TokenHub?\n\nTencent Cloud TokenHub scores 59.5 (C) on agent readiness against Glimpse's 48.8 (D), and leads in every scored category.\n\n### Do Glimpse and Tencent Cloud TokenHub need an API key?\n\nBoth need an API key.\n\n### Can an agent call Glimpse and Tencent Cloud TokenHub without installing anything?\n\nYes. Glimpse has a hosted endpoint at https://openrouter.ai/api/v1 and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.json, and with the fewest tokens: https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"elorian-glimpse\", \"b\": \"tencent-tokenhub\"}`. From a terminal: `anchor compare elorian-glimpse tencent-tokenhub`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/elorian-glimpse.json and https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n\n## Other comparisons with Glimpse or Tencent Cloud TokenHub\n\n- [Claude API vs Glimpse](https://www.anchorterminal.com/compare/anthropic-api-vs-elorian-glimpse.md)\n- [Claude API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.md)\n- [Antseed vs Glimpse](https://www.anchorterminal.com/compare/antseed-vs-elorian-glimpse.md)\n- [BlockRun.AI vs Glimpse](https://www.anchorterminal.com/compare/blockrun-ai-vs-elorian-glimpse.md)\n- [BlockRun.AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.md)\n- [Cerebras Inference vs Glimpse](https://www.anchorterminal.com/compare/cerebras-inference-vs-elorian-glimpse.md)\n- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.md)\n- [Cloudflare AI Gateway vs Glimpse](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-elorian-glimpse.md)\n- [Cloudflare AI Gateway vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub.md)\n- [Cloudflare Workers AI vs Glimpse](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-elorian-glimpse.md)\n- [Cloudflare Workers AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub.md)\n- [Cohere Chat API (Command models) vs Glimpse](https://www.anchorterminal.com/compare/cohere-chat-vs-elorian-glimpse.md)\n- [Cohere Chat API (Command models) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.md)\n- [DeepInfra vs Glimpse](https://www.anchorterminal.com/compare/deepinfra-vs-elorian-glimpse.md)\n- [DeepInfra vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.md)\n- [DeepSeek API vs Glimpse](https://www.anchorterminal.com/compare/deepseek-api-vs-elorian-glimpse.md)\n- [DeepSeek API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.md)\n- [Glimpse vs Fireworks AI Inference](https://www.anchorterminal.com/compare/elorian-glimpse-vs-fireworks-inference.md)\n- [Glimpse vs Gemini Developer API](https://www.anchorterminal.com/compare/elorian-glimpse-vs-gemini-api.md)\n- [Glimpse vs GroqCloud](https://www.anchorterminal.com/compare/elorian-glimpse-vs-groq.md)\n- [Glimpse vs Jais 3](https://www.anchorterminal.com/compare/elorian-glimpse-vs-jais-3.md)\n- [Glimpse vs Meta Model API](https://www.anchorterminal.com/compare/elorian-glimpse-vs-meta-model-api.md)\n- [Glimpse vs MiniMax API](https://www.anchorterminal.com/compare/elorian-glimpse-vs-minimax-api.md)\n- [Glimpse vs Mistral AI API](https://www.anchorterminal.com/compare/elorian-glimpse-vs-mistral-api.md)\n- [Glimpse vs Muse Spark Open](https://www.anchorterminal.com/compare/elorian-glimpse-vs-muse-spark-open.md)\n- [Glimpse vs Nemotron 3.5 Super VL](https://www.anchorterminal.com/compare/elorian-glimpse-vs-nemotron-3-5-super-vl.md)\n- [Glimpse vs Novita AI](https://www.anchorterminal.com/compare/elorian-glimpse-vs-novita-ai.md)\n- [Glimpse vs OpenAI API](https://www.anchorterminal.com/compare/elorian-glimpse-vs-openai-api.md)\n- [Glimpse vs OpenRouter](https://www.anchorterminal.com/compare/elorian-glimpse-vs-openrouter.md)\n- [Glimpse vs Prism Inference](https://www.anchorterminal.com/compare/elorian-glimpse-vs-prism-inference.md)\n- [Glimpse vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/elorian-glimpse-vs-ramp-router.md)\n- [Glimpse vs Beam 1.0](https://www.anchorterminal.com/compare/elorian-glimpse-vs-reflection-beam.md)\n- [Glimpse vs RouterPlus](https://www.anchorterminal.com/compare/elorian-glimpse-vs-routerplus.md)\n- [Glimpse vs SambaCloud](https://www.anchorterminal.com/compare/elorian-glimpse-vs-sambanova.md)\n- [Glimpse vs SiliconFlow](https://www.anchorterminal.com/compare/elorian-glimpse-vs-siliconflow.md)\n- [Glimpse vs Simplismart](https://www.anchorterminal.com/compare/elorian-glimpse-vs-simplismart.md)\n- [Glimpse vs StepFun API](https://www.anchorterminal.com/compare/elorian-glimpse-vs-stepfun-api.md)\n- [Glimpse vs Together AI Inference](https://www.anchorterminal.com/compare/elorian-glimpse-vs-together-inference.md)\n- [Glimpse vs Vercel AI Gateway](https://www.anchorterminal.com/compare/elorian-glimpse-vs-vercel-ai-gateway.md)\n- [Fireworks AI Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.md)\n- [Gemini Developer API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.md)\n- [GroqCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.md)\n- [Jais 3 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.md)\n- [Meta Model API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.md)\n- [MiniMax API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.md)\n- [Mistral AI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.md)\n- [Muse Spark Open vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.md)\n- [Novita AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.md)\n- [OpenAI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.md)\n- [OpenRouter vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.md)\n- [Beam 1.0 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.md)\n- [SambaCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.md)\n- [SiliconFlow vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.md)\n- [Simplismart vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.md)\n- [StepFun API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Together AI Inference](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.md)\n- [Nemotron 3.5 Super VL vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub.md)\n- [Prism Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.md)\n- [Antseed vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.md)\n- [Router.com (Ramp Router) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.md)\n- [RouterPlus vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Vercel AI Gateway](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-02", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Glimpse vs Tencent Cloud TokenHub", "url": "" } ], "description": "Tencent Cloud TokenHub scores 59.5 (C) to Glimpse's 48.8 (D) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Glimpse D 48.8", "Tencent Cloud TokenHub C 59.5", "scores" ], "h1": "Glimpse vs Tencent Cloud TokenHub", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/elorian-glimpse-vs-tencent-tokenhub", "published": "2026-10-01", "section": "tools", "title": "Glimpse vs Tencent Cloud TokenHub for AI agents (2026)", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub" }, "tokens": { "markdown": 6800, "slim": 3630 }, "version": 1 }