DeepInfra vs Tencent Cloud TokenHub

DeepInfra 70

Hosted reading. Own status page at status.deepinfra.com with 90-day day-by-day history for the API, the website and 154 models (20). The API component shows 100 per cent over 88.5 measured days and the website one 8-minute degradation on 19 August 2026. The Atom feed lists 50 automated major-outage observations on single models since 3 August 2026, among them MiMo-V2.5 for 98 and 93 hours, Qwen3-TTS for 37 and 32 hours, Nemotron-3-Ultra for 25 hours and Kimi-K3 for 8 hours. None is a written incident. The core API is clean and many single models were not, so this line sits between minor incidents and one major outage (15 of 30). 200 concurrent requests per model, published (15). 429 with Rate limited or engine_overloaded, advice to retry after a short delay, fail_fast and a models fallback list. No Retry-After header or backoff figures were found (10 of 15). No SLA found. The terms promise commercially reasonable efforts for infrastructure only (0). Generally available (10).

Tencent Cloud TokenHub 46

Hosted reading. No public status page was found. status.cloud.tencent.com did not answer and the Tencent Cloud health dashboard documentation answered with a bot check (0). With no page there is no incident record to read (5 of 30). The announcements carry one incident, DeepSeek's directly supplied models unavailable from 9:06 to 13:04 Beijing time on 15 October 2026 after a fault at DeepSeek, compensated with vouchers. Rate limits are per model, shown in the console and returned by DescribeModelQuota. The public docs give numbers only for batch jobs (20 created a minute, 10 active), image models (5 concurrent) and DeepSeek V4 Flash and Pro (2,500 and 500 concurrent), with the rules for self-serve increases (8 of 15). Six 429 codes separate RPM, TPM, TPD, concurrency and upstream capacity, 429s may carry Retry-After and the docs advise exponential backoff. No idempotency guidance, though inference calls are not writes (13 of 15). The TokenHub SLA promises 99.5% monthly availability with vouchers of 10, 25 or 50 per cent of the month's fee. It excludes free use and third-party deployed models such as DeepSeek's directly supplied ones (10). Generally available since 7 April 2026, with some models marked preview (10).

DeepInfra 20

No machine payment protocol (0). Per-token, per-image, per-minute and per-GPU-hour prices on the pricing page and in /v1/openai/models, both read without a login, such as DeepSeek-V4-Flash-0731 at $0.06 in and $0.18 out per 1M tokens (20). No free tier. The pricing page says an account must add a card or prepay (0). A person signs up in a browser, and the key API needs an existing key (0).

Tencent Cloud TokenHub 35

No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by thcli auth login, but only from that account (0).

DeepInfra 68

Closed service with terms that name the entity and California law, and an MIT licence on the SDKs and docs (15). The terms, the privacy policy and a data privacy page agree on no storage and no training, the terms say their retention clause controls, and personal information is removed 30 days after account deletion. A DPA exists only when executed, and the entity is written Deep Infra Inc. in the terms and DeepInfra, Inc. in the privacy policy (21 of 30). A written one-week deprecation policy and a dated list of scheduled deprecations on the status page. No record of past removals was found (14 of 20). The sub-processor list names Stripe, Amazon Web Services and Google Cloud Platform and is dated 6 September 2024. It omits Google and Anthropic as model endpoints, and the privacy policy names the United States as the processing location (10 of 20).

Tencent Cloud TokenHub 54

Closed service under the TokenHub Terms of Service (effective 14 September 2026), the SLA (23 April 2026), a special note on third-party deployed models and the Tencent Cloud Service Agreement, naming Tencent Cloud Computing (Beijing) Co., Ltd. The CLI is Apache-2.0 (18 of 30). The terms and the FAQ agree that inputs are processed on the customer's instructions and not used for training, and clause 2.14 limits retention to what the service needs without periods. The TokenHub privacy policy on privacy.qq.com renders only with JavaScript and was not read (15 of 30). Dated retirement notices, shutdown dates in the model list, a pre-offline status in /v1/models and a DiscontinuedAt field in the control API. Clause 6.3 refunds paid, unused tokens when a third-party model is removed. No minimum notice period is written (13 of 20). Clause 2.13 places processing generally in mainland China for the China site and in Singapore for the international site, and the third-party model list names DeepSeek's Hangzhou company with a link to its terms. No subprocessor list was found (13 of 20).

DeepInfra 65

Model reading. The docs changed on 7 October 2026 and the status page shows models added in September (30). Deprecated models get at least one week's notice by email, then requests are forwarded to a replacement (5 of 12). Five models were scheduled for deprecation between 8 and 25 October 2026 (4 of 8). No changelog. Support is by Discord and a feedback address, and the docs repository is public (7 of 15). Replies on the SDK repositories were not examined (3 of 10). Python deepinfra 0.3.0 from 12 August 2026 with a changelog. The npm package's newest published version is 2.0.2 from 8 May 2024, while the repository is at 2.1.0 (9 of 15). CI workflows in both SDK repositories (7 of 10).

Tencent Cloud TokenHub 73

Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q&A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and tencent-tokenhub-cli 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10).

DeepInfra 64

Model reading. Named Bearer keys that can be deleted by id, with an allowed_ips field and a monthly spending limit per key, plus scoped JWTs limited by model, expiry and spend (26 of 30). Less 10 because GET /v1/scoped-jwt?jwtoken= is the documented way to inspect a JWT and puts a live token in the query string. Two deprecated routes also carry the API token in the URL path (16 of 30). The terms say Customer Data is not used to train or improve any model. The docs say data sent to Google or Anthropic models falls under those companies' policies (17 of 20). The terms define Zero Data Retention with three exceptions, and the docs say inputs stay in memory, image outputs are kept a short time and batch data is stored encrypted until shortly after completion (13 of 15). Usage per key, request costs and deployment logs are in the API. No account audit log was found (8 of 15). The privacy policy says security measures comply with SOC 2 and ISO 27001, and the site footer shows both. The trust centre answered 403. No security.txt, disclosure policy or bug bounty was found (10 of 20).

Tencent Cloud TokenHub 71

Router, read on the model lines. Bearer keys can be limited to chosen models and inference services, up to 200 source IP ranges and daily, monthly or total token quotas, can be disabled or deleted, and can be created in code through CreateApiKey with signed Tencent Cloud credentials. Keys are long-lived with no expiry setting or built-in rotation (26 of 30). Clause 2.17 of the terms says inputs are not used to train Tencent Cloud's own models, and the FAQ says data is not used for training. Inputs to third-party deployed models (DeepSeek's directly supplied ones) go to DeepSeek under its terms (14 of 20). Clause 2.14 keeps data only as long as the service needs, with no periods stated. When a customer asks for generated content without AI labels, Tencent Cloud keeps logs of who received it for at least six months. No zero-retention option was found (7 of 15). Per-call audit logs (request ID, key, client IP, status, tokens, latency) and optional full call logs go to the customer's CLS, billed separately, with usage by key and a monitoring dashboard (14 of 15). No security.txt on cloud.tencent.com, www.tencent.com or tokenhub.tencentmaas.com (404). Tencent's bug bounty through TSRC lists Tencent Cloud in scope. No certification for TokenHub was checked (10 of 20).

DeepInfra 77

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling with tool_choice of none, auto, required or a named function, and streaming. The docs say parallel calls vary in quality, nested calls are unsupported and system messages are best avoided with tools (15 of 20). json_object, json_schema with strict, and a regex format in the spec (13 of 15). Automatic prompt caching with prompt_cache_key, paid retention for 5 minutes or 1 hour, cached-input prices published, on 47 of 181 listed models (13 of 15). Context of 1,048,576 tokens on DeepSeek V4, Kimi K3 and GLM 5.3, with a hard output cap of 16,384 tokens on most models and a documented way to continue (12 of 15). Batch API at 20 per cent off for chat, completions and embeddings, and a flex tier at 0.8x (10). The OpenAI and Anthropic clients work with a changed base URL. The Python package deepinfra 0.3.0 dates from 12 August 2026, and npm still serves 2.0.2 from May 2024 (7 of 10). 429 carries an engine_overloaded code. Native routes return a bare error string, and no list of codes was found (7 of 15).

Tencent Cloud TokenHub 83

Router, read on the model lines. Function calling is marked on most chat models in the model list, with behaviour depending on the model routed (14 of 20). Structured output is marked per model and missing on the MiniMax and Qwen models, and an unsupported response_format returns code 400006 (12 of 15). Cache-hit prices are published per model, Kimi K3.1 Pro lists five-minute and one-hour cache writes, and a guide covers prompt_cache_key and the X-Session-ID header for instance affinity (14 of 15). Most listed chat models have contexts of one million tokens, a judgement call since a router has no default model (15). Batch at half price covers only Hy3 and Hy4 preview, reads and writes JSONL in the customer's own COS bucket and is documented for the Guangzhou endpoint (5 of 10). No TokenHub inference SDK. The OpenAI and Anthropic SDKs work with a changed base URL, and Tencent Cloud SDK 3.0 and the thcli CLI cover the control plane (8 of 10). Errors return a code, English and Chinese messages, the source, the upstream code and status and a request ID, and stream errors arrive as SSE error frames (15 of 15).