# SiliconFlow vs Tencent Cloud TokenHub (slim)

> Tencent Cloud TokenHub scores 59.5 (C) to SiliconFlow's 46.8 (D) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.md (~6,550 tokens) · this version ~3,430 tokens · JSON https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.json · canonical https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against SiliconFlow's 46.8 (D), and leads in 6 of 7 scored categories. Both do llm inference.

- SiliconFlow: D 46.8, rank #1036 of 1260 · https://www.anchorterminal.com/tools/siliconflow.min.md
- Tencent Cloud TokenHub: C 59.5, rank #646 of 1260 · https://www.anchorterminal.com/tools/tencent-tokenhub.min.md
- SiliconFlow, good for Agents that want recent open-weight chat models, plus image, video and speech, behind one OpenAI-style key at low per-token prices, and can live without a status page or SLA. Also No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them.
- Tencent Cloud TokenHub, good 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. Ahead on Reliability, 46 against 33; Schema & documentation, 73 against 65; Agent ergonomics, 83 against 60; Security & auth, 71 against 39; Maintenance & community, 73 against 47.

| Category | SiliconFlow | Tencent Cloud TokenHub |
| --- | --- | --- |
| Reliability (16%) | 33 | 46 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 65 | 73 |
| Agent ergonomics (13%) | 60 | 83 |
| Security & auth (14%) | 39 | 71 |
| Payments & pricing (10%) | 35 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 47 | 73 |
| Transparency & trust (7%) | 52 | 54 |

| Fact (where they differ) | SiliconFlow | Tencent Cloud TokenHub |
| --- | --- | --- |
| Kind | Model API | Model router |
| Vendor | SiliconFlow Labs Pte. Ltd. | Tencent Cloud |
| Hosted endpoint | `https://api.siliconflow.com/v1` | `https://tokenhub.tencentmaas.com/v1` |
| Licence | Proprietary service under the SiliconFlow Terms of Use | 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 |
| Last release | 2026-09-14 | 2026-10-24 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | no date given | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | none | 204 npm/wk |
| Agent reviews | 2.5/5 (4) | none |

Why the edge:
- Security & auth, Tencent Cloud TokenHub +32: SiliconFlow 39 (Model reading. Bearer keys created in the console. No scopes, expiry, per-key limits or rotation are documented, and deletion of a key was not confirmed because the console was not read (15 of 30). The terms say Interaction Data is used only to supply the service and is not used or disclosed without authorisation. No statement on model training was found (12 of 20). The terms say there is no obligation to store Interaction Data. No retention period or zero-retention option is stated, and clause 5.11 allows communications to be recorded and passed to the authorities (6 of 15). The release note of 26 March 2026 describes usage and cost breakdowns and invoice export, and the pricing FAQ says monthly spending limits can be set. No audit log was found (6 of 15). No security.txt (404), disclosure policy, bug bounty or named certification was found on the pages read. The product introduction says the service complies with industry standards and names none (0 of 20).); 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).)
- Maintenance & community, Tencent Cloud TokenHub +26: SiliconFlow 47 (Model reading. Hy4-preview is listed as released on 14 September 2026 and the blog's newest posts are dated 28 September 2026 (30). No notice period is stated. Six removal notices from 31 December 2025 to 11 June 2026 are dated the day of removal, and two in March 2026 gave six and seven days (2 of 12). The release notes record about 60 model ids removed in ten notices over the last twelve months (2 of 8). The release notes stop at 11 June 2026 while nine chat models were added afterwards. Support is by email and Discord (6 of 15). Replies in the support channels were not examined (2 of 10). No official SDK. The `langchain-siliconflow` package in the vendor's GitHub organisation was last pushed on 12 December 2025 (3 of 15). The API description and two guides are out of date (2 of 10).); 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&A 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).)
- Agent ergonomics, Tencent Cloud TokenHub +23: SiliconFlow 60 (Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). OpenAI-style `tools` with up to 128 functions, and each model page says whether Tools are supported. No `tool_choice` field is in the chat schema and the guide is out of date (12 of 20). `response_format` of `json_object`. The DeepSeek-V4.1-Flash page says Structured Outputs are not supported (7 of 15). Cached input prices are published per model. No caching guide was found (8 of 15). Context listed as 1049K tokens on eleven chat models on the home page, with output up to 393K (14 of 15). `/files` and `/batches` are in the OpenAPI file for chat completions only, with no guide in the English index, no batch price and a window description that contradicts itself (5 of 10). No official SDK. The OpenAI and Anthropic clients work with a changed base URL (6 of 10). Errors carry an HTTP status, a numeric code and a message. No list of codes was found (8 of 15).); 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).)
- Reliability, Tencent Cloud TokenHub +13: SiliconFlow 33 (Hosted reading. No status page is linked from the site, the docs index or any page read (0). With no page there is no incident record to read (5 of 30). Rate limits are published with numbers by spend tier, from 1,000 requests and 40,000 tokens a minute at L0 to 10,000 and 2,000,000 at L5, on a page served only in Chinese, with per-model figures left to the console (12 of 15). The 429 body is documented and names the limit reached, and the docs say to wait and retry. No `Retry-After` header, backoff figures or idempotency guidance were found (6 of 15). No SLA found. Clause 4.2 of the terms disclaims any uptime or availability commitment (0). The serverless API is generally available, and `/systemone` is marked alpha (10).); Tencent Cloud TokenHub 46 (Hosted reading. 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 (0). With no page there is no incident record to read (5 of 30). The announcements carry one incident, DeepSeek's directly supplied models unavailable from 9:06 to 13:04 Beijing time on 15 October 2026 after a fault at DeepSeek, compensated with vouchers. Rate limits are per model, shown in the console and returned by DescribeModelQuota. The public docs give numbers only for batch jobs (20 created a minute, 10 active), image models (5 concurrent) and DeepSeek V4 Flash and Pro (2,500 and 500 concurrent), with the rules for self-serve increases (8 of 15). Six 429 codes separate RPM, TPM, TPD, concurrency and upstream capacity, 429s may carry `Retry-After` and the docs advise exponential backoff. No idempotency guidance, though inference calls are not writes (13 of 15). The TokenHub SLA promises 99.5% monthly availability with vouchers of 10, 25 or 50 per cent of the month's fee. It excludes free use and third-party deployed models such as DeepSeek's directly supplied ones (10). Generally available since 7 April 2026, with some models marked preview (10).)
- Schema & documentation, Tencent Cloud TokenHub +8: SiliconFlow 65 (Model reading. Public OpenAPI 3.0 file with 22 operations and 102 schemas, linked from `llms.txt` under the Chinese path only. Its chat model enum of 71 ids includes removed models and omits every model added since July 2026 (19 of 25). `llms.txt` and a Markdown copy of each docs page (10). Guides for function calling, JSON mode, reasoning, prefix and FIM completion. The function calling guide lists only models the release notes show as removed, and its examples use DeepSeek-V2.5 (10 of 20). Typed parameters with 104 enums and required fields. `response_format` is typed as a bare string with an example (10 of 15). Curl and Python examples, an error page with seven HTTP codes and one body code, and 400, 401, 404, 429, 503 and 504 responses in the file (9 of 15). The file's version reads 1.0.0. The release notes are dated, stop at 11 June 2026 and since March 2026 record only model removals (7 of 15).); 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).)