{ "data": { "a": { "slug": "routerplus", "name": "RouterPlus", "vendor": "RouterPlus", "vendorUrl": "https://routerplus.com", "kind": "router", "category": "inference", "summary": "RouterPlus is an LLM gateway that puts Claude, GPT and decision models behind one API key and a prepaid balance, with OpenAI-compatible and Anthropic-compatible endpoints at the providers' list prices.", "url": "https://www.anchorterminal.com/tools/routerplus", "markdownUrl": "https://www.anchorterminal.com/tools/routerplus.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/routerplus.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/routerplus.json", "dns": "routerplus.grade.anchorterminal.com", "license": "Closed service. No terms of service for the gateway were found on routerplus.com or app.routerplus.com on 13 October 2026. The only terms on the site govern the capacity request form and name EVO HQ Inc, a Delaware corporation (https://routerplus.com/capacity/terms/).", "transports": [ "http" ], "remoteUrl": "https://api.routerplus.com/v1", "packages": [], "auth": "api-key", "authNotes": "A `tm_vk_` virtual key, sent as `Authorization: Bearer` or `x-api-key` on every route. A person signs up in the browser through Clerk with email verification, and the first key is shown once after sign-in. More keys come from the console or from `POST /api/identity/keys` with a console session. The programmatic signup route `POST /v1/signup` was removed and returns 404 (https://app.routerplus.com/docs/authentication.md, https://app.routerplus.com/docs/api-signup.md).", "pricing": "usage", "pricingNotes": "Provider list prices per 1M tokens with no markup, paid from prepaid credits. Purchases start at $10, and RouterPlus matches the first $100 of purchases for eligible accounts. Signup adds no free credit. Inference through the caller's own provider keys (BYOK) carries no RouterPlus charge and needs no credit. Prices are public at https://app.routerplus.com/api/models.json (https://app.routerplus.com/docs/pricing.md).", "priceSummary": "0% fee", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in https://app.routerplus.com/llms-full.txt, checked 13 October 2026. Calls draw on a prepaid balance bought in the console's Billing page.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-13" }, "docsUrl": "https://app.routerplus.com/docs/overview", "llmsTxt": "https://app.routerplus.com/llms.txt", "capabilities": [ "inference.router", "inference.llm", "inference.decision", "image.generate" ], "tags": [ "hosted", "router", "closed-source", "usage-priced", "prepaid", "llms-txt", "openai-compatible", "anthropic-compatible", "streaming" ], "graded": true, "anchor": { "graded": true, "score": 51.4, "grade": "D", "agentReady": false, "rank": 929, "ranked": true, "rankOf": 1260, "categoryRank": 28, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 44, "payments": 40, "reliability": 45, "schema": 59, "security": 62, "transparency": 41 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-13" }, "negative": -2, "negativeNotes": [ "Misleading claim, seen 13 October 2026. The banner on https://routerplus.com/ reads \"Try RouterPlus with free credits\" and links to the playground, while the quickstart (https://app.routerplus.com/docs/quickstart.md) says \"Signup does not add free credit\" and the playground bills the organisation's credits (https://app.routerplus.com/docs/playground.md). Only an invitation link adds credit. -2." ], "verdict": "The docs are written for agents, every model price is public, and each response carries its own cost. No terms of service, privacy policy, status page or changelog were found. Signup adds no free credit, and the chat catalogue is Claude and GPT only.", "bestFor": "Teams that call Claude and GPT models from one key and want the cost of every call in the response, with their own provider keys where they have them.", "strengths": [ "llms.txt, llms-full.txt and a Markdown copy of every page, with an integration guide written for coding agents", "Every billed response carries `usage.cost` in USD, and `GET /v1/generation` lists each attempt behind a request", "Any chat model answers on both the OpenAI-compatible and Anthropic-compatible surfaces, with the format translated by the gateway", "Typed errors with a stable `error_type`, an origin header, and `retry-after` on rate-limit 429s", "The gateway stores no prompt or completion content for ordinary accounts, and BYOK inference carries no RouterPlus charge" ], "weaknesses": [ "No terms of service, privacy policy, status page, changelog or security.txt found for the gateway", "The chat catalogue on 13 October 2026 was nine Claude and ten GPT models, all marked as retained by the provider with no ZDR", "Signup adds no free credit, purchases start at $10, and keys stay at 20 requests a minute until the first purchase", "No idempotency keys, no batch route and no embeddings, and the `zdr` and `regions` filters remove every marketplace route", "Optimize, the eval-based model search the homepage leads with, is paused" ], "agentNotes": [ "Send `max_tokens` on every request. Without it the balance hold assumes up to 32,768 output tokens and can return `insufficient_quota` on a small balance", "Switch on `error_type`. Retry `rate_limit` after `retry-after`, and stop on `insufficient_quota`, which needs a person to add credit or raise a cap", "Don't add a retry loop on top of the SDK's. There is no idempotency key, so a retry that reaches a provider is billed again", "Copy model ids from `GET /v1/models` or /api/models.json. An unknown id is a 404 and the gateway never substitutes one", "Use `/v1/messages` for Claude when you need `thinking` or server tools, and `/v1/chat/completions` with `response_format` only for GPT ids" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 51.4 } ], "editorialScores": { "ergonomics": 71, "maintenance": 44, "payments": 40, "reliability": 45, "schema": 59, "security": 62, "transparency": 26 }, "provenanceScore": 55, "checked": { "categories": { "ergonomics": "2026-10-13", "maintenance": "2026-10-13", "payments": "2026-10-13", "reliability": "2026-10-13", "schema": "2026-10-13", "security": "2026-10-13", "transparency": "2026-10-13" }, "last": "2026-10-13", "lastMoved": "2026-10-28", "oldest": "2026-10-13", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -N https://api.routerplus.com/v1/chat/completions \\\n -H \"Authorization: Bearer $TM_API_KEY\" \\\n -H \"content-type: application/json\" \\\n -d '{\"model\":\"claude-haiku-4-5\",\"stream\":true,\"max_tokens\":60,\"messages\":[{\"role\":\"user\",\"content\":\"hello\"}]}'" }, "letme": { "capability": "https://letme.dev/inference.router", "tool": "https://letme.dev/routerplus" }, "area": "models", "unitPrices": [ { "item": "Markup on provider token prices", "unit": "pct", "usd": 0, "note": "Pass-through per the pricing docs. Credits are bought in $10 steps or more" }, { "item": "Claude Opus 5.5 input", "unit": "1m-tokens", "usd": 4, "note": "claude-opus-5-5, served by Anthropic's API" }, { "item": "Claude Opus 5.5 output", "unit": "1m-tokens", "usd": 20 }, { "item": "GPT-6.1 Sol input", "unit": "1m-tokens", "usd": 2, "note": "gpt-6.1-sol, served by OpenAI's API, 1,050,000-token context" }, { "item": "GPT-6.1 Sol output", "unit": "1m-tokens", "usd": 10 }, { "item": "Anthropic web search server tool", "unit": "1k-requests", "usd": 10, "note": "$10 per 1,000 searches, Anthropic's price, on top of tokens" } ], "provenance": { "legalEntity": "EVO HQ Inc", "domain": "routerplus.com", "domainRegistered": "2014-04-15", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-13", "notes": [ "EVO HQ Inc, a Delaware corporation, is named only in the terms of the capacity request form at https://routerplus.com/capacity/terms/, which govern form submissions and not the gateway. The footer elsewhere reads © 2026 RouterPlus.", "No terms of service or privacy policy for the gateway were found. /terms, /privacy and /legal/terms answer 404 on both hosts, the signup page links neither, and the footer's Privacy and Security links open an email to founders@evo-hq.com. The docs' data policy page (https://app.routerplus.com/docs/data-policy.md) is the only data statement for the gateway.", "No status page. Model pages such as https://app.routerplus.com/models/claude-haiku-4-5 show per-provider uptime over the last 24 hours, with no incident history. A request to status.routerplus.com failed at our proxy with a 502, so whether it exists is unchecked.", "No changelog found. /changelog and /docs/changelog.md answer 404, and the blog's newest post is dated 13 August 2026.", "routerplus.com/.well-known/security.txt and app.routerplus.com/.well-known/security.txt answer 404.", "RDAP gives 15 April 2014 as the registration date of routerplus.com and 2 October 2026 as its last change, so the registration may predate the current owner." ], "score": 55 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/routerplus.json", "live": { "slug": "routerplus", "probe": { "target": "https://api.routerplus.com/v1", "method": "get", "lastAt": "2026-11-02T00:56:19.222493694Z", "lastOk": true, "lastStatus": 401, "lastMs": 481, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.27, "p50ms24h": 507, "p95ms24h": 613, "samples24h": 249, "samples30d": 4788, "days": [ { "date": "2026-10-13", "probes": 4, "ok": 4 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 252 }, { "date": "2026-10-16", "probes": 252, "ok": 249 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "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": 239 }, { "date": "2026-10-24", "probes": 251, "ok": 230 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 248 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "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 } ], "outages": [ { "start": "2026-10-24T05:05:33.613541379Z", "end": "2026-10-24T07:08:12.366400327Z", "note": "HTTP 522 server error" }, { "start": "2026-10-23T17:39:27.824091162Z", "end": "2026-10-23T17:56:26.642152403Z", "note": "timed out" } ] }, "securityTxt": { "url": "https://routerplus.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:42:08.335532731Z" }, "llmsTxt": { "url": "https://app.routerplus.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:14:55.695006641Z" }, "domain": { "domain": "routerplus.com", "registered": "2014-04-15", "source": "https://rdap.verisign.com/com/v1/domain/routerplus.com", "checkedAt": "2026-11-01T14:22:51.180116459Z" }, "pages": [ { "url": "https://app.routerplus.com/docs/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-11-01T06:36:11.932533411Z", "changedAt": "2026-10-23T01:40:31.995317214Z", "fingerprint": "975a48443c79" } ], "updatedAt": "2026-11-02T00:56:19.222493694Z" } }, "answer": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against RouterPlus's 51.4 (D), and leads in 6 of 7 scored categories. RouterPlus leads on payments \u0026 pricing.", "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": 29, "category": "maintenance", "leads": "tencent-tokenhub", "name": "Maintenance \u0026 community", "reasons": { "a": "Router, read on the model lines. No changelog or release notes found. The catalogue on 13 October 2026 lists claude-haiku-5-5, released 7 October, and openai/gpt-6-luna-decisions, released 6 October, so the model list changed within the last 30 days (30). Models carry a `deprecation_date` that delists them automatically, with no notice period stated (3 of 12). `POST /v1/signup` and the magic-link route were removed and Optimize is paused, none with a date we could find (3 of 8). No public changelog. Support is reached through the console and an email address, and wasn't tested (3 of 15). No public issue tracker for the gateway (0 of 10). No official SDK. The docs rely on the OpenAI and Anthropic SDKs and give client setups (5 of 15). No package or public repository to check (0 of 10).", "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": 44, "b": 73 } }, { "by": 14, "category": "schema", "leads": "tencent-tokenhub", "name": "Schema \u0026 documentation", "reasons": { "a": "Router, scored on the API lines. No OpenAPI or other machine-readable contract for the gateway was found. It follows the OpenAI and Anthropic wire formats, which this checklist doesn't credit to a reseller, the same reading as Antseed (0 of 25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Each route page says what it is for, what isn't available, and which route to use for which model, and the agent integration guide lists what not to build on (18 of 20). Request fields follow the upstream formats, and the wire compatibility page tables which fields pass, translate, drop or fail with a typed 400 (12 of 15). Curl, Python and TypeScript examples on every page, and an error reference with a class, status and remedy for each error (15). Routes are versioned under /v1 and the wire compatibility page says changing it needs a recorded decision, but no changelog or dated release notes were found (4 of 15).", "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": 59, "b": 73 } }, { "by": 13, "category": "transparency", "leads": "tencent-tokenhub", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with no terms of service found. The only terms on the site govern the capacity request form, under EVO HQ Inc (0 of 30). The data policy page is detailed and agrees with the homepage FAQ, lists what is stored and why, and names the hackathon logging exception and each provider's retention flag. There is no privacy policy, no DPA and no retention period for account data such as email addresses (14 of 30). Model retirement by `deprecation_date` is documented with no notice period, and no dated deprecation notices were found (4 of 20). The docs name Clerk, Resend and an AWS bucket, and say RouterPlus's own GPUs run in the United States. The form's terms name Supabase, Cloudflare and Resend. No complete subprocessor list or gateway hosting location was found (8 of 20).", "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": 41, "b": 54 } }, { "by": 12, "category": "ergonomics", "leads": "tencent-tokenhub", "name": "Agent ergonomics", "reasons": { "a": "Router, read on the model lines (tool use, structured output, caching, context, batch, SDKs, errors). Tools pass through on both surfaces, and Anthropic server tools such as web search work for Claude models on `/v1/messages`. Behaviour depends on the model (15 of 20). `response_format` works only for GPT ids, and the docs tell callers to get JSON from Claude through a single tool, so structured output rests on the provider (8 of 15). Cached-input and cache-write prices per model, a session id that keeps provider caches warm, and `cache_control` on the Anthropic surface (13 of 15). The catalogue's largest contexts are 1,050,000 tokens on GPT-6.1 Sol and 1,000,000 on Claude Sonnet 5.5, a judgement call since a router has no default model (15). No batch route (0 of 10). No SDK of its own. The OpenAI and Anthropic SDKs work with a changed base URL, and the docs give setups for ten coding tools (5 of 10). A stable `error_type` in every body and header, an origin header, the limit that refused a request, and `x-tm-dropped-params` naming every dropped field (15).", "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": 71, "b": 83 } }, { "by": 9, "category": "security", "leads": "tencent-tokenhub", "name": "Security \u0026 auth", "reasons": { "a": "Router, read on the model lines. `tm_vk_` keys are stored as SHA-256 hashes, shown once and revocable, and each is bound to a workspace and principal, with per-key RPM and monthly spend caps. Inference keys have no management rights. There are no permission scopes on a key and no SSO or SCIM (24 of 30). The gateway stores no prompt or completion content except for accounts in a hackathon or similar programme (up to 30 days) and Optimize searches, and RouterPlus says it trains on nothing. Every Claude and GPT chat route is marked `prompt_logging: retained` with no ZDR, so retention and training rest on Anthropic's and OpenAI's API terms (12 of 20). Content isn't stored by default, but the `zdr` and `data_collection: deny` filters remove every marketplace route today, so they work only on the caller's own provider keys (10 of 15). `GET /v1/generation` lists every attempt behind a request with provider, tokens and cost, and the console has usage and logs, metadata only (14 of 15). No security.txt, disclosure policy, bug bounty or certification found. The footer's Security link is an email to founders@evo-hq.com (2 of 20).", "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": 62, "b": 71 } }, { "by": 5, "category": "payments", "leads": "routerplus", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol found in llms-full.txt. Calls draw on a prepaid balance (0). Per-token prices for every model are public JSON at /api/models.json with no login (20). Signup adds no free credit, but inference through the caller's own provider keys carries no RouterPlus charge and needs no credit, the reading Cloudflare AI Gateway's dossier took for the same arrangement. We did not sign up to confirm that no card is asked for (20). A person signs up in the browser through Clerk with email verification, and the programmatic signup route was removed (0).", "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": 40, "b": 35 } } ], "facts": [ { "a": "Model router", "b": "Model router", "name": "Kind" }, { "a": "RouterPlus", "b": "Tencent Cloud", "name": "Vendor" }, { "a": "https://api.routerplus.com/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 service. No terms of service for the gateway were found on routerplus.com or app.routerplus.com on 13 October 2026. The only terms on the site govern the capacity request form and name EVO HQ Inc, a Delaware corporation (https://routerplus.com/capacity/terms/).", "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": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-24", "name": "Last release" }, { "a": "no document linked", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no document linked", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not read yet", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "204 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against RouterPlus's 51.4 (D), and leads in 6 of 7 scored categories. RouterPlus leads on payments \u0026 pricing.", "question": "Which is better for AI agents, RouterPlus or Tencent Cloud TokenHub?" }, { "answer": "Both need an API key.", "question": "Do RouterPlus and Tencent Cloud TokenHub need an API key?" }, { "answer": "Yes. RouterPlus has a hosted endpoint at https://api.routerplus.com/v1 and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.", "question": "Can an agent call RouterPlus and Tencent Cloud TokenHub without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 35" ], "also": null, "goodFor": "Teams that call Claude and GPT models from one key and want the cost of every call in the response, with their own provider keys where they have them.", "slug": "routerplus", "watchFor": "No terms of service, privacy policy, status page, changelog or security.txt found for the gateway" }, { "aheadOn": [ "Schema \u0026 documentation, 73 against 59", "Agent ergonomics, 83 against 71", "Security \u0026 auth, 71 against 62", "Maintenance \u0026 community, 73 against 44", "Transparency \u0026 trust, 54 against 41" ], "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": { "routerplus": [ { "causes": [ "method" ], "date": "2026-10-28", "delta": 0.1, "from": 51.3, "fromGrade": "D", "to": 51.4, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 51.2, "fromGrade": "D", "to": 51.3, "toGrade": "D" } ], "tencent-tokenhub": null }, "job": { "capability": "inference.router", "name": "Model routing" }, "others": [ { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-routerplus.json", "title": "Claude API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-routerplus" }, { "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/blockrun-ai-vs-routerplus.json", "title": "BlockRun.AI vs RouterPlus", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-routerplus" }, { "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-routerplus.json", "title": "Cerebras Inference vs RouterPlus", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-routerplus" }, { "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-routerplus.json", "title": "Cloudflare AI Gateway vs RouterPlus", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-routerplus" }, { "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-routerplus.json", "title": "Cloudflare Workers AI vs RouterPlus", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-routerplus" }, { "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-routerplus.json", "title": "Cohere Chat API (Command models) vs RouterPlus", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-routerplus" }, { "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-routerplus.json", "title": "DeepInfra vs RouterPlus", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-routerplus" }, { "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-routerplus.json", "title": "DeepSeek API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-routerplus" }, { "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-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-tencent-tokenhub.json", "title": "Glimpse vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-routerplus.json", "title": "Fireworks AI Inference vs RouterPlus", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-routerplus" }, { "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-routerplus.json", "title": "Gemini Developer API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-routerplus" }, { "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-routerplus.json", "title": "GroqCloud vs RouterPlus", "url": "https://www.anchorterminal.com/compare/groq-vs-routerplus" }, { "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-routerplus.json", "title": "Jais 3 vs RouterPlus", "url": "https://www.anchorterminal.com/compare/jais-3-vs-routerplus" }, { "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-routerplus.json", "title": "Meta Model API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-routerplus" }, { "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-routerplus.json", "title": "MiniMax API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-routerplus" }, { "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-routerplus.json", "title": "Mistral AI API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-routerplus" }, { "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-routerplus.json", "title": "Muse Spark Open vs RouterPlus", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-routerplus" }, { "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/nemotron-3-5-super-vl-vs-routerplus.json", "title": "Nemotron 3.5 Super VL vs RouterPlus", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/novita-ai-vs-routerplus.json", "title": "Novita AI vs RouterPlus", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-routerplus" }, { "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-routerplus.json", "title": "OpenAI API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/openai-api-vs-routerplus" }, { "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-routerplus.json", "title": "OpenRouter vs RouterPlus", "url": "https://www.anchorterminal.com/compare/openrouter-vs-routerplus" }, { "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/prism-inference-vs-routerplus.json", "title": "Prism Inference vs RouterPlus", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/reflection-beam-vs-routerplus.json", "title": "Beam 1.0 vs RouterPlus", "url": "https://www.anchorterminal.com/compare/reflection-beam-vs-routerplus" }, { "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/routerplus-vs-sambanova.json", "title": "RouterPlus vs SambaCloud", "url": "https://www.anchorterminal.com/compare/routerplus-vs-sambanova" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-siliconflow.json", "title": "RouterPlus vs SiliconFlow", "url": "https://www.anchorterminal.com/compare/routerplus-vs-siliconflow" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-simplismart.json", "title": "RouterPlus vs Simplismart", "url": "https://www.anchorterminal.com/compare/routerplus-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-stepfun-api.json", "title": "RouterPlus vs StepFun API", "url": "https://www.anchorterminal.com/compare/routerplus-vs-stepfun-api" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-together-inference.json", "title": "RouterPlus vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/routerplus-vs-together-inference" }, { "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-routerplus.json", "title": "Antseed vs RouterPlus", "url": "https://www.anchorterminal.com/compare/antseed-vs-routerplus" }, { "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-routerplus.json", "title": "Router.com (Ramp Router) vs RouterPlus", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-routerplus" }, { "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-vercel-ai-gateway.json", "title": "RouterPlus vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/routerplus-vs-vercel-ai-gateway" }, { "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": 1, "edge": "tencent-tokenhub", "key": "reliability", "name": "Reliability", "routerplus": 45, "tencent-tokenhub": 46, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 14, "edge": "tencent-tokenhub", "key": "schema", "name": "Schema \u0026 documentation", "routerplus": 59, "tencent-tokenhub": 73, "weight": 13 }, { "by": 12, "edge": "tencent-tokenhub", "key": "ergonomics", "name": "Agent ergonomics", "routerplus": 71, "tencent-tokenhub": 83, "weight": 13 }, { "by": 9, "edge": "tencent-tokenhub", "key": "security", "name": "Security \u0026 auth", "routerplus": 62, "tencent-tokenhub": 71, "weight": 14 }, { "by": 5, "edge": "routerplus", "key": "payments", "name": "Payments \u0026 pricing", "routerplus": 40, "tencent-tokenhub": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 29, "edge": "tencent-tokenhub", "key": "maintenance", "name": "Maintenance \u0026 community", "routerplus": 44, "tencent-tokenhub": 73, "weight": 7 }, { "by": 13, "edge": "tencent-tokenhub", "key": "transparency", "name": "Transparency \u0026 trust", "routerplus": 41, "tencent-tokenhub": 54, "weight": 7 } ], "summary": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against RouterPlus's 51.4 (D), and leads in 6 of 7 scored categories. RouterPlus leads on payments \u0026 pricing. Both do model routing.", "tasks": null, "tutorials": [], "verdicts": { "routerplus": "The docs are written for agents, every model price is public, and each response carries its own cost. No terms of service, privacy policy, status page or changelog were found. Signup adds no free credit, and the chat catalogue is Claude and GPT only.", "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/routerplus-vs-tencent-tokenhub", "json": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.min.md" }, "markdown": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against RouterPlus's 51.4 (D), and leads in 6 of 7 scored categories. RouterPlus leads on payments \u0026 pricing. Both do model routing.\n\n- RouterPlus: grade D, 51.4/100, rank #929 of 1260. Markdown https://www.anchorterminal.com/tools/routerplus.md · JSON https://www.anchorterminal.com/api/v1/tools/routerplus.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### RouterPlus (D)\n\nGood for: Teams that call Claude and GPT models from one key and want the cost of every call in the response, with their own provider keys where they have them.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 35\n\nWatch for: No terms of service, privacy policy, status page, changelog or security.txt found for the gateway\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- Schema \u0026 documentation, 73 against 59\n- Agent ergonomics, 83 against 71\n- Security \u0026 auth, 71 against 62\n- Maintenance \u0026 community, 73 against 44\n- Transparency \u0026 trust, 54 against 41\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 +29\n\n- RouterPlus (44): Router, read on the model lines. No changelog or release notes found. The catalogue on 13 October 2026 lists claude-haiku-5-5, released 7 October, and openai/gpt-6-luna-decisions, released 6 October, so the model list changed within the last 30 days (30). Models carry a `deprecation_date` that delists them automatically, with no notice period stated (3 of 12). `POST /v1/signup` and the magic-link route were removed and Optimize is paused, none with a date we could find (3 of 8). No public changelog. Support is reached through the console and an email address, and wasn't tested (3 of 15). No public issue tracker for the gateway (0 of 10). No official SDK. The docs rely on the OpenAI and Anthropic SDKs and give client setups (5 of 15). No package or public repository to check (0 of 10).\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### Schema \u0026 documentation: Tencent Cloud TokenHub +14\n\n- RouterPlus (59): Router, scored on the API lines. No OpenAPI or other machine-readable contract for the gateway was found. It follows the OpenAI and Anthropic wire formats, which this checklist doesn't credit to a reseller, the same reading as Antseed (0 of 25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Each route page says what it is for, what isn't available, and which route to use for which model, and the agent integration guide lists what not to build on (18 of 20). Request fields follow the upstream formats, and the wire compatibility page tables which fields pass, translate, drop or fail with a typed 400 (12 of 15). Curl, Python and TypeScript examples on every page, and an error reference with a class, status and remedy for each error (15). Routes are versioned under /v1 and the wire compatibility page says changing it needs a recorded decision, but no changelog or dated release notes were found (4 of 15).\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### Transparency \u0026 trust: Tencent Cloud TokenHub +13\n\n- RouterPlus (41): Closed service with no terms of service found. The only terms on the site govern the capacity request form, under EVO HQ Inc (0 of 30). The data policy page is detailed and agrees with the homepage FAQ, lists what is stored and why, and names the hackathon logging exception and each provider's retention flag. There is no privacy policy, no DPA and no retention period for account data such as email addresses (14 of 30). Model retirement by `deprecation_date` is documented with no notice period, and no dated deprecation notices were found (4 of 20). The docs name Clerk, Resend and an AWS bucket, and say RouterPlus's own GPUs run in the United States. The form's terms name Supabase, Cloudflare and Resend. No complete subprocessor list or gateway hosting location was found (8 of 20).\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### Agent ergonomics: Tencent Cloud TokenHub +12\n\n- RouterPlus (71): Router, read on the model lines (tool use, structured output, caching, context, batch, SDKs, errors). Tools pass through on both surfaces, and Anthropic server tools such as web search work for Claude models on `/v1/messages`. Behaviour depends on the model (15 of 20). `response_format` works only for GPT ids, and the docs tell callers to get JSON from Claude through a single tool, so structured output rests on the provider (8 of 15). Cached-input and cache-write prices per model, a session id that keeps provider caches warm, and `cache_control` on the Anthropic surface (13 of 15). The catalogue's largest contexts are 1,050,000 tokens on GPT-6.1 Sol and 1,000,000 on Claude Sonnet 5.5, a judgement call since a router has no default model (15). No batch route (0 of 10). No SDK of its own. The OpenAI and Anthropic SDKs work with a changed base URL, and the docs give setups for ten coding tools (5 of 10). A stable `error_type` in every body and header, an origin header, the limit that refused a request, and `x-tm-dropped-params` naming every dropped field (15).\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### Security \u0026 auth: Tencent Cloud TokenHub +9\n\n- RouterPlus (62): Router, read on the model lines. `tm_vk_` keys are stored as SHA-256 hashes, shown once and revocable, and each is bound to a workspace and principal, with per-key RPM and monthly spend caps. Inference keys have no management rights. There are no permission scopes on a key and no SSO or SCIM (24 of 30). The gateway stores no prompt or completion content except for accounts in a hackathon or similar programme (up to 30 days) and Optimize searches, and RouterPlus says it trains on nothing. Every Claude and GPT chat route is marked `prompt_logging: retained` with no ZDR, so retention and training rest on Anthropic's and OpenAI's API terms (12 of 20). Content isn't stored by default, but the `zdr` and `data_collection: deny` filters remove every marketplace route today, so they work only on the caller's own provider keys (10 of 15). `GET /v1/generation` lists every attempt behind a request with provider, tokens and cost, and the console has usage and logs, metadata only (14 of 15). No security.txt, disclosure policy, bug bounty or certification found. The footer's Security link is an email to founders@evo-hq.com (2 of 20).\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### Payments \u0026 pricing: RouterPlus +5\n\n- RouterPlus (40): No machine payment protocol found in llms-full.txt. Calls draw on a prepaid balance (0). Per-token prices for every model are public JSON at /api/models.json with no login (20). Signup adds no free credit, but inference through the caller's own provider keys carries no RouterPlus charge and needs no credit, the reading Cloudflare AI Gateway's dossier took for the same arrangement. We did not sign up to confirm that no card is asked for (20). A person signs up in the browser through Clerk with email verification, and the programmatic signup route was removed (0).\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 | RouterPlus | Tencent Cloud TokenHub | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 46 | Tencent Cloud TokenHub +1 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 59 | 73 | Tencent Cloud TokenHub +14 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 83 | Tencent Cloud TokenHub +12 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 71 | Tencent Cloud TokenHub +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | RouterPlus +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 44 | 73 | Tencent Cloud TokenHub +29 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 41 | 54 | Tencent Cloud TokenHub +13 |\n| Negative events | ≤15 | -2 | -3 | |\n| **Total** | | **51.4 · D** | **59.5 · C** | |\n\n## Facts side by side\n\n| Fact | RouterPlus | Tencent Cloud TokenHub |\n| --- | --- | --- |\n| Kind | Model router | Model router |\n| Vendor | RouterPlus | Tencent Cloud |\n| Hosted endpoint | `https://api.routerplus.com/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 service. No terms of service for the gateway were found on routerplus.com or app.routerplus.com on 13 October 2026. The only terms on the site govern the capacity request form and name EVO HQ Inc, a Delaware corporation (https://routerplus.com/capacity/terms/). | 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 | yes | yes |\n| Last release | none | 2026-10-24 |\n| Terms last updated | no document linked | couldn't be read |\n| Privacy policy last updated | no document linked | couldn't be read |\n| Customer content may train models | not read yet | couldn't be read |\n| Terms restrict automated access | not read yet | couldn't be read |\n| Terms restrict benchmarking | not read yet | couldn't be read |\n| Terms or service can change without notice | not read yet | couldn't be read |\n| Arbitration or class-action waiver | not read yet | couldn't be read |\n| Popularity | none | 204 npm/wk |\n\n## How the scores have moved\n\n### RouterPlus\n\n- +0.1 on 28 October 2026: checklist\n- +0.1 on 27 October 2026: checklist\n\n### Tencent Cloud TokenHub\n\nNo score change since it was listed.\n\n## Verdicts\n\n**RouterPlus.** The docs are written for agents, every model price is public, and each response carries its own cost. No terms of service, privacy policy, status page or changelog were found. Signup adds no free credit, and the chat catalogue is Claude and GPT only.\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### RouterPlus\n\n1. Send `max_tokens` on every request. Without it the balance hold assumes up to 32,768 output tokens and can return `insufficient_quota` on a small balance\n2. Switch on `error_type`. Retry `rate_limit` after `retry-after`, and stop on `insufficient_quota`, which needs a person to add credit or raise a cap\n3. Don't add a retry loop on top of the SDK's. There is no idempotency key, so a retry that reaches a provider is billed again\n4. Copy model ids from `GET /v1/models` or /api/models.json. An unknown id is a 404 and the gateway never substitutes one\n5. Use `/v1/messages` for Claude when you need `thinking` or server tools, and `/v1/chat/completions` with `response_format` only for GPT ids\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, RouterPlus or Tencent Cloud TokenHub?\n\nTencent Cloud TokenHub scores 59.5 (C) on agent readiness against RouterPlus's 51.4 (D), and leads in 6 of 7 scored categories. RouterPlus leads on payments \u0026 pricing.\n\n### Do RouterPlus and Tencent Cloud TokenHub need an API key?\n\nBoth need an API key.\n\n### Can an agent call RouterPlus and Tencent Cloud TokenHub without installing anything?\n\nYes. RouterPlus has a hosted endpoint at https://api.routerplus.com/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/routerplus-vs-tencent-tokenhub.json, and with the fewest tokens: https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"routerplus\", \"b\": \"tencent-tokenhub\"}`. From a terminal: `anchor compare routerplus tencent-tokenhub`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/routerplus.json and https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n\n## Other comparisons with RouterPlus or Tencent Cloud TokenHub\n\n- [Claude API vs RouterPlus](https://www.anchorterminal.com/compare/anthropic-api-vs-routerplus.md)\n- [Claude API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.md)\n- [BlockRun.AI vs RouterPlus](https://www.anchorterminal.com/compare/blockrun-ai-vs-routerplus.md)\n- [BlockRun.AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.md)\n- [Cerebras Inference vs RouterPlus](https://www.anchorterminal.com/compare/cerebras-inference-vs-routerplus.md)\n- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.md)\n- [Cloudflare AI Gateway vs RouterPlus](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-routerplus.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 RouterPlus](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-routerplus.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 RouterPlus](https://www.anchorterminal.com/compare/cohere-chat-vs-routerplus.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 RouterPlus](https://www.anchorterminal.com/compare/deepinfra-vs-routerplus.md)\n- [DeepInfra vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.md)\n- [DeepSeek API vs RouterPlus](https://www.anchorterminal.com/compare/deepseek-api-vs-routerplus.md)\n- [DeepSeek API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.md)\n- [Glimpse vs RouterPlus](https://www.anchorterminal.com/compare/elorian-glimpse-vs-routerplus.md)\n- [Glimpse vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.md)\n- [Fireworks AI Inference vs RouterPlus](https://www.anchorterminal.com/compare/fireworks-inference-vs-routerplus.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 RouterPlus](https://www.anchorterminal.com/compare/gemini-api-vs-routerplus.md)\n- [Gemini Developer API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.md)\n- [GroqCloud vs RouterPlus](https://www.anchorterminal.com/compare/groq-vs-routerplus.md)\n- [GroqCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.md)\n- [Jais 3 vs RouterPlus](https://www.anchorterminal.com/compare/jais-3-vs-routerplus.md)\n- [Jais 3 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.md)\n- [Meta Model API vs RouterPlus](https://www.anchorterminal.com/compare/meta-model-api-vs-routerplus.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 RouterPlus](https://www.anchorterminal.com/compare/minimax-api-vs-routerplus.md)\n- [MiniMax API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.md)\n- [Mistral AI API vs RouterPlus](https://www.anchorterminal.com/compare/mistral-api-vs-routerplus.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 RouterPlus](https://www.anchorterminal.com/compare/muse-spark-open-vs-routerplus.md)\n- [Muse Spark Open vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.md)\n- [Nemotron 3.5 Super VL vs RouterPlus](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-routerplus.md)\n- [Novita AI vs RouterPlus](https://www.anchorterminal.com/compare/novita-ai-vs-routerplus.md)\n- [Novita AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.md)\n- [OpenAI API vs RouterPlus](https://www.anchorterminal.com/compare/openai-api-vs-routerplus.md)\n- [OpenAI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.md)\n- [OpenRouter vs RouterPlus](https://www.anchorterminal.com/compare/openrouter-vs-routerplus.md)\n- [OpenRouter vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.md)\n- [Prism Inference vs RouterPlus](https://www.anchorterminal.com/compare/prism-inference-vs-routerplus.md)\n- [Beam 1.0 vs RouterPlus](https://www.anchorterminal.com/compare/reflection-beam-vs-routerplus.md)\n- [Beam 1.0 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.md)\n- [RouterPlus vs SambaCloud](https://www.anchorterminal.com/compare/routerplus-vs-sambanova.md)\n- [RouterPlus vs SiliconFlow](https://www.anchorterminal.com/compare/routerplus-vs-siliconflow.md)\n- [RouterPlus vs Simplismart](https://www.anchorterminal.com/compare/routerplus-vs-simplismart.md)\n- [RouterPlus vs StepFun API](https://www.anchorterminal.com/compare/routerplus-vs-stepfun-api.md)\n- [RouterPlus vs Together AI Inference](https://www.anchorterminal.com/compare/routerplus-vs-together-inference.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 RouterPlus](https://www.anchorterminal.com/compare/antseed-vs-routerplus.md)\n- [Antseed vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.md)\n- [Router.com (Ramp Router) vs RouterPlus](https://www.anchorterminal.com/compare/ramp-router-vs-routerplus.md)\n- [Router.com (Ramp Router) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.md)\n- [RouterPlus vs Vercel AI Gateway](https://www.anchorterminal.com/compare/routerplus-vs-vercel-ai-gateway.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": "RouterPlus vs Tencent Cloud TokenHub", "url": "" } ], "description": "Tencent Cloud TokenHub scores 59.5 (C) to RouterPlus's 51.4 (D) for model routing. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "RouterPlus D 51.4", "Tencent Cloud TokenHub C 59.5", "scores" ], "h1": "RouterPlus vs Tencent Cloud TokenHub", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/routerplus-vs-tencent-tokenhub", "published": "2026-10-01", "section": "tools", "title": "RouterPlus vs Tencent Cloud TokenHub for AI agents (2026)", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub" }, "tokens": { "markdown": 6900, "slim": 3830 }, "version": 1 }