{ "data": { "a": { "slug": "cohere-chat", "name": "Cohere Chat API (Command models)", "vendor": "Cohere", "vendorUrl": "https://cohere.com", "kind": "model", "category": "inference", "summary": "Cohere's Chat API generates text with the Command family of models over REST (v2 chat), with tool use, structured outputs, citations and streaming. SDKs cover Python, TypeScript, Java and Go.", "url": "https://www.anchorterminal.com/tools/cohere-chat", "markdownUrl": "https://www.anchorterminal.com/tools/cohere-chat.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cohere-chat.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cohere-chat.json", "dns": "cohere-chat.grade.anchorterminal.com", "repo": "https://github.com/cohere-ai/cohere-python", "license": "Proprietary service under Cohere's Commercial SaaS Agreement. The SDKs are MIT", "transports": [ "http" ], "remoteUrl": "https://api.cohere.com/v2/chat", "packages": [ { "registry": "pypi", "name": "cohere" }, { "registry": "npm", "name": "cohere-ai" }, { "registry": "go", "name": "github.com/cohere-ai/cohere-go/v2" } ], "auth": "api-key", "authNotes": "Bearer API key from the dashboard, self-serve. A trial key is created at sign-up. A production key needs a team Owner to complete the Go to Production form and accept the SaaS agreement. Team roles are Owner and User. No key scopes or expiry were found in the docs.", "pricing": "freemium", "pricingNotes": "Trial keys are free with no card, limited to 20 chat requests a minute and 1,000 calls a month, and not for commercial use. Production keys bill per input and output token, monthly or at $250 outstanding. Current Command prices are in a script-drawn tab of cohere.com/pricing that we could not read. Production keys stay at trial limits on Command A+, Reasoning, Translate and Vision (checked 2026-10-09).", "priceSummary": "from $2.50 / 1M in", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.cohere.com/docs/chat-api", "rateLimitsUrl": "https://docs.cohere.com/docs/rate-limits", "llmsTxt": "https://docs.cohere.com/llms.txt", "openapi": "https://raw.githubusercontent.com/cohere-ai/cohere-developer-experience/main/cohere-openapi.yaml", "capabilities": [ "inference.llm", "inference.open-weights" ], "tags": [ "official", "hosted", "model", "free-tier", "no-card", "openapi", "llms-txt", "openai-compatible", "python", "typescript", "java", "go", "status-page", "soc2", "bug-bounty" ], "lastRelease": "2026-09-09", "graded": true, "anchor": { "graded": true, "score": 64.7, "grade": "B", "agentReady": false, "rank": 377, "ranked": true, "rankOf": 1260, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 72, "payments": 30, "reliability": 64, "schema": 84, "security": 57, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "A public OpenAPI file, Markdown twins of every docs page and SDKs in four languages make the Chat API easy for an agent to read. Production keys do not cover the four newest Command models, whose limits are set by sales, and the SaaS agreement lets Cohere share API data with third parties.", "bestFor": "Teams that want Command models for RAG with citations, tool use and multilingual work, and that may later move to a private deployment or Model Vault.", "strengths": [ "Public OpenAPI 3.1 file in the docs repository, last changed 29 September 2026, and a Markdown twin of every docs page", "A trial key is created at sign-up with no card, limited to 20 chat requests a minute and 1,000 calls a month", "Official SDKs for Python, TypeScript, Java and Go, each with a release on 26 August 2026", "JSON Schema structured outputs, `strict_tools` (beta), citations, reasoning budgets and safety modes on the v2 chat request", "The trust centre lists SOC 2 Type II, ISO 27001, ISO 42001 and a bug bounty, with nine sub-processors, all in the US" ], "weaknesses": [ "Production keys work like trial keys on Command A+, Reasoning, Translate and Vision. The docs send production use of those models to sales or to Model Vault", "Prices for current Command models sit in a script-drawn tab of the pricing page that we could not read. Only legacy prices appear in the page text", "The SaaS agreement of 8 April 2025 grants Cohere an irrevocable right to use API data to improve its services and to share it with third parties", "No Retry-After header, backoff guidance or idempotency key was found in the reviewed documentation", "The SaaS agreement forbids use of the services for benchmarking or competitive analysis. Recorded as a fact, and it matters before any probe is run" ], "agentNotes": [ "Call `POST https://api.cohere.com/v2/chat` with `Authorization: bearer \u003ckey\u003e`. `model` and `messages` are the only required fields", "Use `command-a-03-2025`, `command-r-08-2024`, `command-r-plus-08-2024` or `command-r7b-12-2024` for production traffic. Newer variants stay at trial limits on a production key", "Keep a trial key under 20 chat requests a minute and 1,000 calls a month, and do not use it for commercial work", "Set `response_format` with a `json_schema` for structured output, and tell the model to produce JSON when using `json_object` without a schema", "Ask the account Owner to turn off training under Data Controls in the dashboard before sending confidential prompts" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.7 } ], "editorialScores": { "ergonomics": 72, "maintenance": 72, "payments": 30, "reliability": 64, "schema": 84, "security": 57, "transparency": 65 }, "provenanceScore": 84, "checked": { "categories": { "ergonomics": "2026-10-09", "maintenance": "2026-10-09", "payments": "2026-10-09", "reliability": "2026-10-09", "schema": "2026-10-09", "security": "2026-10-09", "transparency": "2026-10-09" }, "last": "2026-10-09", "lastMoved": "2026-10-28", "oldest": "2026-10-09", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install cohere # or: npm i cohere-ai", "http": "curl --request POST \\\n --url https://api.cohere.ai/v2/chat \\\n --header 'accept: application/json' \\\n --header 'content-type: application/json' \\\n --header \"Authorization: bearer $CO_API_KEY\" \\\n --data '{\"model\":\"command-a-plus-05-2026\",\"messages\":[{\"role\":\"user\",\"content\":\"Hello\"}]}'" }, "letme": { "capability": "https://letme.dev/inference.llm", "tool": "https://letme.dev/cohere-chat" }, "sameCompany": [ "cohere-embed", "cohere-transcribe-03-2026", "cohere-north" ], "area": "models", "provenance": { "legalEntity": "Cohere Inc.", "domain": "cohere.com", "domainRegistered": "2000-03-07", "endpointOnVendorDomain": true, "terms": "https://cohere.com/saas-agreement", "privacy": "https://cohere.com/privacy", "statusPage": "https://status.cohere.com", "changelog": "https://docs.cohere.com/v2/changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Commercial SaaS Agreement (last updated 8 April 2025) names Cohere Inc., 171 John Street, Suite 200, Toronto, Ontario, and is governed by Ontario law.", "The privacy policy (last updated 1 May 2026) says it does not apply to customer inputs and outputs under an enterprise agreement, which the agreement and a DPA govern. The DPA is sent on request.", "The OpenAPI file names https://api.cohere.com as the server and the chat guide's examples call https://api.cohere.ai. Both are Cohere's.", "cohere.com/.well-known/security.txt answers 404. The trust centre holds a responsible disclosure policy for the bug bounty.", "status.cohere.ai redirects to status.cohere.com, whose robots.txt answers 404, so the host publishes no rules.", "RDAP for cohere.com gives a registration date of 2000-03-07." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cohere-chat.json", "live": { "slug": "cohere-chat", "probe": { "target": "https://api.cohere.com/v2/chat", "method": "get", "lastAt": "2026-11-02T00:56:00.077086163Z", "lastOk": true, "lastStatus": 401, "lastMs": 141, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 148, "p95ms24h": 209, "samples24h": 249, "samples30d": 5858, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "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": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 10, "ok": 10 } ] }, "vendorStatus": { "page": "https://status.cohere.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-02T01:00:36.586870533Z" }, "versions": [ { "registry": "github", "name": "cohere-ai/cohere-python", "version": "7.3.0", "released": "2026-10-21", "seenAt": "2026-11-01T16:50:53.722562268Z" }, { "registry": "npm", "name": "cohere-ai", "version": "8.3.0", "seenAt": "2026-11-01T16:50:52.825767745Z" }, { "registry": "pypi", "name": "cohere", "version": "7.3.0", "released": "2026-10-21", "seenAt": "2026-11-01T16:50:52.57331459Z" } ], "githubStars": 407, "npmWeekly": 713532, "pypiWeekly": 2552567, "securityTxt": { "url": "https://cohere.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:42:13.164872664Z" }, "llmsTxt": { "url": "https://docs.cohere.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:13:25.337668768Z" }, "domain": { "domain": "cohere.com", "registered": "2000-03-07", "source": "https://rdap.verisign.com/com/v1/domain/cohere.com", "checkedAt": "2026-11-01T14:17:56.515021491Z" }, "pages": [ { "url": "https://docs.cohere.com/v2/changelog", "kind": "changelog", "status": 304, "checkedAt": "2026-11-01T06:41:13.465203117Z", "changedAt": "2026-10-28T04:14:34.456971164Z", "fingerprint": "fe9495804422" }, { "url": "https://docs.cohere.com/docs/deprecations", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-01T06:41:11.448293312Z", "changedAt": "2026-10-28T04:14:32.397653406Z", "fingerprint": "518b789d6a3b" }, { "url": "https://cohere.com/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-01T06:37:55.557184682Z", "changedAt": "2026-10-28T04:11:04.49728025Z", "fingerprint": "2a3d703857f8" }, { "url": "https://cohere.com/saas-agreement", "kind": "terms", "status": 304, "checkedAt": "2026-11-01T06:37:57.563579709Z", "changedAt": "2026-10-28T04:11:07.209530426Z", "fingerprint": "0bbdb0cc2fee" } ], "models": { "command-r-plus-08-2024": { "openrouterId": "cohere/command-r-plus-08-2024", "tools": true, "structuredOutputs": true, "jsonMode": true, "reasoning": false, "input": [ "text" ], "promptCaching": false, "contextTokens": 128000, "maxOutput": 4000, "checkedAt": "2026-11-01T23:49:20.31928442Z" } }, "github": { "repo": "cohere-ai/cohere-python", "checkedAt": "2026-10-26T07:19:41.547198192Z", "stars": 406, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-21T15:03:34Z", "openIssues": 2, "openPRs": 19, "issuesOpened90d": 10, "issuesClosed90d": 8, "prsMerged90d": 6, "ci": { "branch": "main", "runs": 44, "success": 36, "failure": 8, "other": 0, "latest": "success", "latestAt": "2026-10-21T14:30:24Z" }, "replies": { "sampled": 25, "unanswered": 2, "medianDays": 6.9 } }, "updatedAt": "2026-11-02T01:00:36.586870533Z" } }, "answer": "Cohere Chat API (Command models) scores 64.7 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 3 of 7 scored categories. Tencent Cloud TokenHub leads on agent ergonomics, security \u0026 auth and 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": 21, "category": "transparency", "leads": "cohere-chat", "name": "Transparency \u0026 trust", "reasons": { "a": "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).", "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": 75, "b": 54 } }, { "by": 18, "category": "reliability", "leads": "cohere-chat", "name": "Reliability", "reasons": { "a": "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).", "b": "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)." }, "scores": { "a": 64, "b": 46 } }, { "by": 14, "category": "security", "leads": "tencent-tokenhub", "name": "Security \u0026 auth", "reasons": { "a": "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).", "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": 57, "b": 71 } }, { "by": 11, "category": "schema", "leads": "cohere-chat", "name": "Schema \u0026 documentation", "reasons": { "a": "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).", "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": 84, "b": 73 } }, { "by": 11, "category": "ergonomics", "leads": "tencent-tokenhub", "name": "Agent ergonomics", "reasons": { "a": "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).", "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": 72, "b": 83 } }, { "by": 5, "category": "payments", "leads": "tencent-tokenhub", "name": "Payments \u0026 pricing", "reasons": { "a": "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).", "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": 30, "b": 35 } } ], "facts": [ { "a": "Model API", "b": "Model router", "name": "Kind" }, { "a": "Cohere", "b": "Tencent Cloud", "name": "Vendor" }, { "a": "https://api.cohere.com/v2/chat", "b": "https://tokenhub.tencentmaas.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Cohere's Commercial SaaS Agreement. The SDKs are MIT", "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": "2026-09-09", "b": "2026-10-24", "name": "Last release" }, { "a": "2025-04-08", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-05-01", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "204 npm/wk", "name": "Popularity" }, { "a": "3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Cohere Chat API (Command models) scores 64.7 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 3 of 7 scored categories. Tencent Cloud TokenHub leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, Cohere Chat API (Command models) or Tencent Cloud TokenHub?" }, { "answer": "Both need an API key.", "question": "Do Cohere Chat API (Command models) and Tencent Cloud TokenHub need an API key?" }, { "answer": "Yes. Cohere Chat API (Command models) has a hosted endpoint at https://api.cohere.com/v2/chat and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.", "question": "Can an agent call Cohere Chat API (Command models) and Tencent Cloud TokenHub without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 64 against 46", "Schema \u0026 documentation, 84 against 73", "Transparency \u0026 trust, 75 against 54" ], "also": [ "Free to start without a card", "No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them" ], "goodFor": "Teams that want Command models for RAG with citations, tool use and multilingual work, and that may later move to a private deployment or Model Vault.", "slug": "cohere-chat", "watchFor": "Production keys work like trial keys on Command A+, Reasoning, Translate and Vision. The docs send production use of those models to sales or to Model Vault" }, { "aheadOn": [ "Agent ergonomics, 83 against 72", "Security \u0026 auth, 71 against 57", "Payments \u0026 pricing, 35 against 30" ], "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": { "cohere-chat": [ { "causes": [ "method" ], "date": "2026-10-28", "delta": 0, "from": 64.7, "fromGrade": "B", "to": 64.7, "toGrade": "B" } ], "tencent-tokenhub": null }, "job": { "capability": "inference.llm", "name": "LLM inference" }, "others": [ { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-cohere-chat.json", "title": "Claude API vs Cohere Chat API (Command models)", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-cohere-chat" }, { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.json", "title": "Claude API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-cohere-chat.json", "title": "Antseed vs Cohere Chat API (Command models)", "url": "https://www.anchorterminal.com/compare/antseed-vs-cohere-chat" }, { "json": "https://www.anchorterminal.com/compare/blockrun-ai-vs-cohere-chat.json", "title": "BlockRun.AI vs Cohere Chat API (Command models)", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-cohere-chat" }, { "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-cohere-chat.json", "title": "Cerebras Inference vs Cohere Chat API (Command models)", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-cohere-chat" }, { "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-cohere-chat.json", "title": "Cloudflare AI Gateway vs Cohere Chat API (Command models)", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-cohere-chat" }, { "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-cohere-chat.json", "title": "Cloudflare Workers AI vs Cohere Chat API (Command models)", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-cohere-chat" }, { "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-deepinfra.json", "title": "Cohere Chat API (Command models) vs DeepInfra", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-deepinfra" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-deepseek-api.json", "title": "Cohere Chat API (Command models) vs DeepSeek API", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-deepseek-api" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-elorian-glimpse.json", "title": "Cohere Chat API (Command models) vs Glimpse", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-fireworks-inference.json", "title": "Cohere Chat API (Command models) vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-fireworks-inference" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-gemini-api.json", "title": "Cohere Chat API (Command models) vs Gemini Developer API", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-gemini-api" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-groq.json", "title": "Cohere Chat API (Command models) vs GroqCloud", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-groq" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-jais-3.json", "title": "Cohere Chat API (Command models) vs Jais 3", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-jais-3" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-meta-model-api.json", "title": "Cohere Chat API (Command models) vs Meta Model API", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-meta-model-api" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-minimax-api.json", "title": "Cohere Chat API (Command models) vs MiniMax API", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-minimax-api" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-mistral-api.json", "title": "Cohere Chat API (Command models) vs Mistral AI API", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-mistral-api" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-muse-spark-open.json", "title": "Cohere Chat API (Command models) vs Muse Spark Open", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-muse-spark-open" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-nemotron-3-5-super-vl.json", "title": "Cohere Chat API (Command models) vs Nemotron 3.5 Super VL", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-nemotron-3-5-super-vl" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-novita-ai.json", "title": "Cohere Chat API (Command models) vs Novita AI", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-novita-ai" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-openai-api.json", "title": "Cohere Chat API (Command models) vs OpenAI API", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-openai-api" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-openrouter.json", "title": "Cohere Chat API (Command models) vs OpenRouter", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-openrouter" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-prism-inference.json", "title": "Cohere Chat API (Command models) vs Prism Inference", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-prism-inference" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-ramp-router.json", "title": "Cohere Chat API (Command models) vs Router.com (Ramp Router)", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-ramp-router" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-reflection-beam.json", "title": "Cohere Chat API (Command models) vs Beam 1.0", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-reflection-beam" }, { "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-sambanova.json", "title": "Cohere Chat API (Command models) vs SambaCloud", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-sambanova" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-siliconflow.json", "title": "Cohere Chat API (Command models) vs SiliconFlow", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-siliconflow" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-simplismart.json", "title": "Cohere Chat API (Command models) vs Simplismart", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-stepfun-api.json", "title": "Cohere Chat API (Command models) vs StepFun API", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-stepfun-api" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-together-inference.json", "title": "Cohere Chat API (Command models) vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-vercel-ai-gateway.json", "title": "Cohere Chat API (Command models) vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-vercel-ai-gateway" }, { "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-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-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-tencent-tokenhub.json", "title": "Fireworks AI Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.json", "title": "Gemini Developer API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.json", "title": "GroqCloud vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.json", "title": "Jais 3 vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.json", "title": "Meta Model API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.json", "title": "MiniMax API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.json", "title": "Mistral AI API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.json", "title": "Muse Spark Open vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.json", "title": "Novita AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.json", "title": "OpenAI API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.json", "title": "OpenRouter vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.json", "title": "Beam 1.0 vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.json", "title": "SambaCloud vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.json", "title": "SiliconFlow vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.json", "title": "Simplismart vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.json", "title": "StepFun API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.json", "title": "Tencent Cloud TokenHub vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub.json", "title": "Nemotron 3.5 Super VL vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.json", "title": "Prism Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.json", "title": "Antseed vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.json", "title": "Router.com (Ramp Router) vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.json", "title": "RouterPlus vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.json", "title": "Tencent Cloud TokenHub vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway" } ], "panel": null, "scores": [ { "by": 18, "cohere-chat": 64, "edge": "cohere-chat", "key": "reliability", "name": "Reliability", "tencent-tokenhub": 46, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 11, "cohere-chat": 84, "edge": "cohere-chat", "key": "schema", "name": "Schema \u0026 documentation", "tencent-tokenhub": 73, "weight": 13 }, { "by": 11, "cohere-chat": 72, "edge": "tencent-tokenhub", "key": "ergonomics", "name": "Agent ergonomics", "tencent-tokenhub": 83, "weight": 13 }, { "by": 14, "cohere-chat": 57, "edge": "tencent-tokenhub", "key": "security", "name": "Security \u0026 auth", "tencent-tokenhub": 71, "weight": 14 }, { "by": 5, "cohere-chat": 30, "edge": "tencent-tokenhub", "key": "payments", "name": "Payments \u0026 pricing", "tencent-tokenhub": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 1, "cohere-chat": 72, "edge": "tencent-tokenhub", "key": "maintenance", "name": "Maintenance \u0026 community", "tencent-tokenhub": 73, "weight": 7 }, { "by": 21, "cohere-chat": 75, "edge": "cohere-chat", "key": "transparency", "name": "Transparency \u0026 trust", "tencent-tokenhub": 54, "weight": 7 } ], "summary": "Cohere Chat API (Command models) scores 64.7 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 3 of 7 scored categories. Tencent Cloud TokenHub leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing. Both do llm inference.", "tasks": null, "tutorials": [], "verdicts": { "cohere-chat": "A public OpenAPI file, Markdown twins of every docs page and SDKs in four languages make the Chat API easy for an agent to read. Production keys do not cover the four newest Command models, whose limits are set by sales, and the SaaS agreement lets Cohere share API data with third parties.", "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/cohere-chat-vs-tencent-tokenhub", "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.min.md" }, "markdown": "Cohere Chat API (Command models) scores 64.7 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 3 of 7 scored categories. Tencent Cloud TokenHub leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing. Both do llm inference.\n\n- Cohere Chat API (Command models): grade B, 64.7/100, rank #377 of 1260. Markdown https://www.anchorterminal.com/tools/cohere-chat.md · JSON https://www.anchorterminal.com/api/v1/tools/cohere-chat.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### Cohere Chat API (Command models) (B)\n\nGood for: Teams that want Command models for RAG with citations, tool use and multilingual work, and that may later move to a private deployment or Model Vault.\n\nAhead on:\n- Reliability, 64 against 46\n- Schema \u0026 documentation, 84 against 73\n- Transparency \u0026 trust, 75 against 54\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them\n\nWatch for: Production keys work like trial keys on Command A+, Reasoning, Translate and Vision. The docs send production use of those models to sales or to Model Vault\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- Agent ergonomics, 83 against 72\n- Security \u0026 auth, 71 against 57\n- Payments \u0026 pricing, 35 against 30\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### Transparency \u0026 trust: Cohere Chat API (Command models) +21\n\n- 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).\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### Reliability: Cohere Chat API (Command models) +18\n\n- 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).\n- 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).\n\n### Security \u0026 auth: Tencent Cloud TokenHub +14\n\n- 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).\n- Tencent Cloud TokenHub (71): Router, read on the model lines. Bearer keys can be limited to chosen models and inference services, up to 200 source IP ranges and daily, monthly or total token quotas, can be disabled or deleted, and can be created in code through CreateApiKey with signed Tencent Cloud credentials. Keys are long-lived with no expiry setting or built-in rotation (26 of 30). Clause 2.17 of the terms says inputs are not used to train Tencent Cloud's own models, and the FAQ says data is not used for training. Inputs to third-party deployed models (DeepSeek's directly supplied ones) go to DeepSeek under its terms (14 of 20). Clause 2.14 keeps data only as long as the service needs, with no periods stated. When a customer asks for generated content without AI labels, Tencent Cloud keeps logs of who received it for at least six months. No zero-retention option was found (7 of 15). Per-call audit logs (request ID, key, client IP, status, tokens, latency) and optional full call logs go to the customer's CLS, billed separately, with usage by key and a monitoring dashboard (14 of 15). No security.txt on cloud.tencent.com, www.tencent.com or tokenhub.tencentmaas.com (404). Tencent's bug bounty through TSRC lists Tencent Cloud in scope. No certification for TokenHub was checked (10 of 20).\n\n### Schema \u0026 documentation: Cohere Chat API (Command models) +11\n\n- 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).\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### Agent ergonomics: Tencent Cloud TokenHub +11\n\n- 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).\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### Payments \u0026 pricing: Tencent Cloud TokenHub +5\n\n- 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).\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 | Cohere Chat API (Command models) | Tencent Cloud TokenHub | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 64 | 46 | Cohere Chat API (Command models) +18 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 73 | Cohere Chat API (Command models) +11 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 83 | Tencent Cloud TokenHub +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 57 | 71 | Tencent Cloud TokenHub +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 35 | Tencent Cloud TokenHub +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 72 | 73 | Tencent Cloud TokenHub +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 54 | Cohere Chat API (Command models) +21 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **64.7 · B** | **59.5 · C** | |\n\n## Facts side by side\n\n| Fact | Cohere Chat API (Command models) | Tencent Cloud TokenHub |\n| --- | --- | --- |\n| Kind | Model API | Model router |\n| Vendor | Cohere | Tencent Cloud |\n| Hosted endpoint | `https://api.cohere.com/v2/chat` | `https://tokenhub.tencentmaas.com/v1` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under Cohere's Commercial SaaS Agreement. The SDKs are MIT | 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 | 2026-09-09 | 2026-10-24 |\n| Terms last updated | 2025-04-08 | couldn't be read |\n| Privacy policy last updated | 2026-05-01 | couldn't be read |\n| Customer content may train models | yes | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | none | 204 npm/wk |\n| Agent reviews | 3/5 (4) | none |\n\n## How the scores have moved\n\n### Cohere Chat API (Command models)\n\n- no change on 28 October 2026: checklist\n\n### Tencent Cloud TokenHub\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Cohere Chat API (Command models).** A public OpenAPI file, Markdown twins of every docs page and SDKs in four languages make the Chat API easy for an agent to read. Production keys do not cover the four newest Command models, whose limits are set by sales, and the SaaS agreement lets Cohere share API data with third parties.\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### Cohere Chat API (Command models)\n\n1. Call `POST https://api.cohere.com/v2/chat` with `Authorization: bearer \u003ckey\u003e`. `model` and `messages` are the only required fields\n2. Use `command-a-03-2025`, `command-r-08-2024`, `command-r-plus-08-2024` or `command-r7b-12-2024` for production traffic. Newer variants stay at trial limits on a production key\n3. Keep a trial key under 20 chat requests a minute and 1,000 calls a month, and do not use it for commercial work\n4. Set `response_format` with a `json_schema` for structured output, and tell the model to produce JSON when using `json_object` without a schema\n5. Ask the account Owner to turn off training under Data Controls in the dashboard before sending confidential prompts\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, Cohere Chat API (Command models) or Tencent Cloud TokenHub?\n\nCohere Chat API (Command models) scores 64.7 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 3 of 7 scored categories. Tencent Cloud TokenHub leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing.\n\n### Do Cohere Chat API (Command models) and Tencent Cloud TokenHub need an API key?\n\nBoth need an API key.\n\n### Can an agent call Cohere Chat API (Command models) and Tencent Cloud TokenHub without installing anything?\n\nYes. Cohere Chat API (Command models) has a hosted endpoint at https://api.cohere.com/v2/chat 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/cohere-chat-vs-tencent-tokenhub.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cohere-chat\", \"b\": \"tencent-tokenhub\"}`. From a terminal: `anchor compare cohere-chat tencent-tokenhub`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cohere-chat.json and https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n\n## Other comparisons with Cohere Chat API (Command models) or Tencent Cloud TokenHub\n\n- [Claude API vs Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/anthropic-api-vs-cohere-chat.md)\n- [Claude API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.md)\n- [Antseed vs Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/antseed-vs-cohere-chat.md)\n- [BlockRun.AI vs Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/blockrun-ai-vs-cohere-chat.md)\n- [BlockRun.AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.md)\n- [Cerebras Inference vs Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/cerebras-inference-vs-cohere-chat.md)\n- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.md)\n- [Cloudflare AI Gateway vs Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-cohere-chat.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 Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-cohere-chat.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 DeepInfra](https://www.anchorterminal.com/compare/cohere-chat-vs-deepinfra.md)\n- [Cohere Chat API (Command models) vs DeepSeek API](https://www.anchorterminal.com/compare/cohere-chat-vs-deepseek-api.md)\n- [Cohere Chat API (Command models) vs Glimpse](https://www.anchorterminal.com/compare/cohere-chat-vs-elorian-glimpse.md)\n- [Cohere Chat API (Command models) vs Fireworks AI Inference](https://www.anchorterminal.com/compare/cohere-chat-vs-fireworks-inference.md)\n- [Cohere Chat API (Command models) vs Gemini Developer API](https://www.anchorterminal.com/compare/cohere-chat-vs-gemini-api.md)\n- [Cohere Chat API (Command models) vs GroqCloud](https://www.anchorterminal.com/compare/cohere-chat-vs-groq.md)\n- [Cohere Chat API (Command models) vs Jais 3](https://www.anchorterminal.com/compare/cohere-chat-vs-jais-3.md)\n- [Cohere Chat API (Command models) vs Meta Model API](https://www.anchorterminal.com/compare/cohere-chat-vs-meta-model-api.md)\n- [Cohere Chat API (Command models) vs MiniMax API](https://www.anchorterminal.com/compare/cohere-chat-vs-minimax-api.md)\n- [Cohere Chat API (Command models) vs Mistral AI API](https://www.anchorterminal.com/compare/cohere-chat-vs-mistral-api.md)\n- [Cohere Chat API (Command models) vs Muse Spark Open](https://www.anchorterminal.com/compare/cohere-chat-vs-muse-spark-open.md)\n- [Cohere Chat API (Command models) vs Nemotron 3.5 Super VL](https://www.anchorterminal.com/compare/cohere-chat-vs-nemotron-3-5-super-vl.md)\n- [Cohere Chat API (Command models) vs Novita AI](https://www.anchorterminal.com/compare/cohere-chat-vs-novita-ai.md)\n- [Cohere Chat API (Command models) vs OpenAI API](https://www.anchorterminal.com/compare/cohere-chat-vs-openai-api.md)\n- [Cohere Chat API (Command models) vs OpenRouter](https://www.anchorterminal.com/compare/cohere-chat-vs-openrouter.md)\n- [Cohere Chat API (Command models) vs Prism Inference](https://www.anchorterminal.com/compare/cohere-chat-vs-prism-inference.md)\n- [Cohere Chat API (Command models) vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/cohere-chat-vs-ramp-router.md)\n- [Cohere Chat API (Command models) vs Beam 1.0](https://www.anchorterminal.com/compare/cohere-chat-vs-reflection-beam.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 SambaCloud](https://www.anchorterminal.com/compare/cohere-chat-vs-sambanova.md)\n- [Cohere Chat API (Command models) vs SiliconFlow](https://www.anchorterminal.com/compare/cohere-chat-vs-siliconflow.md)\n- [Cohere Chat API (Command models) vs Simplismart](https://www.anchorterminal.com/compare/cohere-chat-vs-simplismart.md)\n- [Cohere Chat API (Command models) vs StepFun API](https://www.anchorterminal.com/compare/cohere-chat-vs-stepfun-api.md)\n- [Cohere Chat API (Command models) vs Together AI Inference](https://www.anchorterminal.com/compare/cohere-chat-vs-together-inference.md)\n- [Cohere Chat API (Command models) vs Vercel AI Gateway](https://www.anchorterminal.com/compare/cohere-chat-vs-vercel-ai-gateway.md)\n- [DeepInfra vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.md)\n- [DeepSeek API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.md)\n- [Glimpse vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.md)\n- [Fireworks AI Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.md)\n- [Gemini Developer API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.md)\n- [GroqCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.md)\n- [Jais 3 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.md)\n- [Meta Model API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.md)\n- [MiniMax API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.md)\n- [Mistral AI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.md)\n- [Muse Spark Open vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.md)\n- [Novita AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.md)\n- [OpenAI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.md)\n- [OpenRouter vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.md)\n- [Beam 1.0 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.md)\n- [SambaCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.md)\n- [SiliconFlow vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.md)\n- [Simplismart vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.md)\n- [StepFun API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Together AI Inference](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.md)\n- [Nemotron 3.5 Super VL vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub.md)\n- [Prism Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.md)\n- [Antseed vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.md)\n- [Router.com (Ramp Router) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.md)\n- [RouterPlus vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Vercel AI Gateway](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-02", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Cohere Chat API (Command models) vs Tencent Cloud TokenHub", "url": "" } ], "description": "Cohere Chat scores 64.7 (B) to Tencent Cloud TokenHub's 59.5 (C) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Cohere Chat API (Command models) B 64.7", "Tencent Cloud TokenHub C 59.5", "scores" ], "h1": "Cohere Chat API (Command models) vs Tencent Cloud TokenHub", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/cohere-chat-vs-tencent-tokenhub", "published": "2026-10-01", "section": "tools", "title": "Cohere Chat vs Tencent Cloud TokenHub for AI agents (2026)", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub" }, "tokens": { "markdown": 7200, "slim": 3880 }, "version": 1 }