Cohere Chat API (Command models) vs Tencent Cloud TokenHub

Cohere Chat API (Command models) 75

Closed service under a published SaaS agreement, MIT SDKs, and the docs say Command A+ weights are on Hugging Face under Apache 2.0, which we did not open (15 of 30). The Enterprise Data Commitments (5 December 2025) and the privacy policy (1 May 2026) agree on 30-day retention and a training opt-out. The SaaS agreement (8 April 2025) does not mention the opt-out and grants an irrevocable right to use and share API data, and the DPA is sent on request (16 of 30). Deprecations page with dated history back to 2024 and lifecycle terms, no minimum notice (16 of 20). The trust centre names nine sub-processors, all in the US, and Google Cloud US-Central as the data location (18 of 20).

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).

Cohere Chat API (Command models) 64

Hosted lines. status.cohere.com (incident.io) lists each Command model and the endpoints as components with uptime from July to October 2026 (20). Its feed shows three incidents in 90 days. 'Multiple Endpoint Disruptions' on 1 September 2026 touched embeddings, rerank and command-a-reasoning-08-2025, with no duration in the feed, and the other two were docs loading on 5 August and dashboard login on 23 July. Model and endpoint uptime still reads 100 per cent, so we count minor incidents only (20). Chat limits are published per model, 20 requests a minute and 1,000 calls a month on a trial key and 500 a minute on a production key for Command A, R, R+ and R7B, while the four newest variants say contact sales (12 of 15). The errors page documents 429 with sample messages. No Retry-After header, backoff guidance or idempotency key was found (5 of 15). cohere.com/slo is titled Service Level Objective and its text is script-drawn, so it was unread and scores as absent (0). The v2 chat endpoint is the default docs version, but the sample response on the chat guide still carries is_experimental and the newest models are not open to production keys (7 of 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).

Cohere Chat API (Command models) 57

Model reading. Bearer keys of two kinds, trial and production. Team roles are Owner and User, only Owners delete production keys, and a production key is shown in full once. No scopes, expiry or per-model restriction was found (18 of 30). Paying customers can switch training off under Data Controls, which implies it is on until they do, trial keys fall under the website terms, and the SaaS agreement grants an irrevocable right to use API data to improve the services and share it with third parties (8 of 20). Logged prompts and generations are deleted after 30 days unless flagged, and zero data retention needs approval (12 of 15). The dashboard shows usage history, and no customer audit log was found (2 of 15). The trust centre lists SOC 2 Type II, ISO 27001, ISO 42001, UK Cyber Essentials, penetration tests on request and a responsible disclosure policy with a bug bounty. cohere.com/.well-known/security.txt answers 404 (17 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).

Cohere Chat API (Command models) 84

Model reading. Public OpenAPI 3.1 file cohere-openapi.yaml in cohere-ai/cohere-developer-experience, 43 operations, last changed 29 September 2026 (25). docs.cohere.com/llms.txt and a Markdown twin of every page by adding .md, though the llms.txt files list no pages (8 of 10). The v2 chat operation describes each of its 21 request fields with defaults and limits, and says less about when to prefer one option (16 of 20). Enums on tool_choice, safety_mode and thinking.type, numeric bounds on temperature, k, p and priority, with penalties bounded only in prose (12 of 15). Eight request examples on the operation and an errors page with sample messages for each status code, with error bodies carrying a message and no machine code (12 of 15). v1 and v2 live side by side in the path and the changelog is dated, but the OpenAPI file is version 1.0 throughout and its changes are committed as 'Add spec changes' with no per-change note (11 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).

Cohere Chat API (Command models) 72

Model reading. Function calling with tool_choice REQUIRED or NONE and strict_tools, which the reference marks beta (17 of 20). response_format takes json_object or a JSON Schema, with limits documented and no support in RAG mode (13 of 15). The usage object reports cached_tokens, and no guide or price for prompt caching was found (5 of 15). Context is 256,000 tokens on Command A and Command A Reasoning and 128,000 on Command A+ (10 of 15). /v2/batches runs a batch from an uploaded dataset, with no price or discount found (6 of 10). Official SDKs for Python, TypeScript, Java and Go (10). Error messages are specific and readable, with no stable error codes (11 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).

Cohere Chat API (Command models) 30

No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (0). The docs say Command models are billed per input and output token, and the pricing page's Generative models tab is script-drawn, so current prices were unread. The page text shows only legacy prices, such as $2.50 and $10.00 per million tokens for Command R+ 08-2024. Half marks, and the gap is ours to state (10 of 20). A trial key is created at sign-up and is free with no card (20). Sign-up is in a browser, and a production key needs an Owner to complete a Go to Production form (0).

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).