# MiniMax API vs Tencent Cloud TokenHub (slim)

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

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

Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against MiniMax API's 55.3 (C), and leads in 4 of 7 scored categories. MiniMax API leads on reliability, schema & documentation and transparency & trust. Both do llm inference.

- MiniMax API: C 55.3, rank #800 of 1260 · https://www.anchorterminal.com/tools/minimax-api.min.md
- Tencent Cloud TokenHub: C 59.5, rank #646 of 1260 · https://www.anchorterminal.com/tools/tencent-tokenhub.min.md
- MiniMax API, good for Cheap long-context agent and coding calls through an Anthropic-compatible client, on data you can share with the vendor. Ahead on Reliability, 75 against 46; Schema & documentation, 82 against 73; Transparency & trust, 65 against 54. Also No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them.
- Tencent Cloud TokenHub, good for Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing. Ahead on Agent ergonomics, 83 against 59; Security & auth, 71 against 30; Payments & pricing, 35 against 20; Maintenance & community, 73 against 45.

| Category | MiniMax API | Tencent Cloud TokenHub |
| --- | --- | --- |
| Reliability (16%) | 75 | 46 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 82 | 73 |
| Agent ergonomics (13%) | 59 | 83 |
| Security & auth (14%) | 30 | 71 |
| Payments & pricing (10%) | 20 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 45 | 73 |
| Transparency & trust (7%) | 65 | 54 |

| Fact (where they differ) | MiniMax API | Tencent Cloud TokenHub |
| --- | --- | --- |
| Kind | Model API | Model router |
| Vendor | MiniMax | Tencent Cloud |
| Hosted endpoint | `https://api.minimax.io` | `https://tokenhub.tencentmaas.com/v1` |
| Licence | Proprietary API under MiniMax's platform terms. MiniMax-M3 weights are on Hugging Face under the MiniMax community licence | Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0 |
| Last release | 2026-10-19 | 2026-10-24 |
| Popularity | 493 stars | 204 npm/wk |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Security & auth, Tencent Cloud TokenHub +41: MiniMax API 30 (Model reading (credential, training, retention, operator visibility, programme). One bearer key per account on the pay-as-you-go side and a separate Subscription Key for M Plan, with no scopes found. MiniMax says it may disable keys that leak publicly (20 of 30). The terms, effective 30 March 2026, say MiniMax may use input and generated content to provide, maintain, develop and improve its services, and no opt-out was found. The privacy policy says only that personal data isn't used for training to profile or target consumers (0 of 20). Data is kept as long as necessary for its purpose, with no period stated and no zero-retention route (5 of 15). A usage page and balance alerts, no audit log found (5 of 15). No security.txt on platform.minimax.io or api.minimax.io, and no bug bounty or certification found (0 of 20). Total 30.); 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).)
- Reliability, MiniMax API +29: MiniMax API 75 (Atlassian Statuspage at status.minimax.io with a Large Language Models component (20). Its history feed holds the last 25 incidents, 13 to 19 October 2026. 23 are 'Elevated errors on Large Language Models', each resolved within 1 to 41 minutes, and none lasted an hour. That is minor only on what we could read, though frequent, and the earlier part of the 90 days wasn't readable because robots.txt disallows the incidents API (20). The rate-limits page publishes 200 requests and 10,000,000 tokens a minute for M3.1 Flash and M3 (15). The Anthropic-format OpenAPI file documents 429 for rate limits and 529 as an overload that can be retried, and the error-code page says to retry later on 1002, with no Retry-After header or backoff schedule found (10). No SLA found (0). M3.1 Flash and M3 are generally available, and the Preview name was retired on launch day (10). Total 75.); 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).)
- Maintenance & community, Tencent Cloud TokenHub +28: MiniMax API 45 (Model reading. MiniMax-M3.1-Flash shipped on 19 October 2026, dated on the model release page (30). No stated notice policy. The M2.5 and M2.7 families closed to new users on 19 October and retire on 18 November, 30 days later, and from 19 October M Plan and Token Plan requests to them are served by M3.1 Flash under the old names. We couldn't find when that notice was first posted (3 of 12). Churn is high. M2.5 (February 2026) and M2.7 (March 2026) retire within nine months of release, M2.1 and M2 are already retired, and the model list calls M2.5 and M2.7 retired while the notice on the same page gives 18 November (2 of 8). A dated release page, support email addresses on the contact and model pages, a Discord server and GitHub issues on the model repositories. We didn't test whether they answer (10 of 15). No official SDK (0 of 15, 0 of 10). Total 45.); Tencent Cloud TokenHub 73 (Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q&A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and `tencent-tokenhub-cli` 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10).)
- Agent ergonomics, Tencent Cloud TokenHub +24: MiniMax API 59 (Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use on all three formats, with `tool_choice` on the Anthropic format only (17 of 20). No JSON Schema output mode documented on any format (0 of 15). Caching is automatic, with cache reads at a tenth of the input price on M3.1 Flash and a token-count endpoint for sizing a request (15). 1,000,000-token context and up to 524,288 output tokens (15). No batch API found (0). No official SDK. The docs point to the Anthropic and OpenAI SDKs and the AI SDK (0). Typed error bodies with a request id on the Anthropic format and a code table, though `stop_sequences` is ignored without an error (12 of 15). M3.1 Flash can't turn thinking off and defaults to the deepest `effort`, which costs output tokens unless the caller lowers it. Total 59.); 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).)
- Payments & pricing, Tencent Cloud TokenHub +15: MiniMax API 20 (No x402, MPP or L402 (0). Per-token prices for M3.1 Flash and M3 are published without a login (20). No free tier found for the text models (0). A person signs up in a browser and tops up a balance or buys an M Plan before the first call (0). Total 20.); 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).)
- Transparency & trust, MiniMax API +11: MiniMax API 65 (Closed service with clear terms under Singapore law and SIAC arbitration. MiniMax-M3's weights are on Hugging Face under the MiniMax community licence, which isn't an OSI licence and doesn't change the hosted service (15). The terms and privacy policy, both dated 30 March 2026, agree on the contracting entity, that inputs and outputs are processed and may be used to improve services, and that data sits in a United States data centre, but give no retention period and no DPA was read (10 of 30). A dated retirement notice for M2.5 and M2.7 and a retired-models table, undercut by the table contradicting the notice and API release notes a year stale (12 of 20). Data location stated as the United States and an EU representative named, with third parties named only by category (10 of 20). MiniMax publishes an EU AI Act training-data summary for M3. Total 47.); 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).)