Head to head · LLM inference · October 2026 research run

Claude API vs Tencent Cloud TokenHub

Claude API scores 77.3 (BB) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments & pricing. Both do llm inference.

Best model APIs and inference for AI agents · All 529 models comparisons

Which one, for what

Claude API BB

Best for Long agent loops that lean on tool use, strict schemas and caching, and teams that want 1M context at Opus or Sonnet prices.

Ahead on

  • Reliability, 60 against 46
  • Schema & documentation, 90 against 73
  • Agent ergonomics, 95 against 83
  • Security & auth, 92 against 71
  • Maintenance & community, 91 against 73
  • Transparency & trust, 85 against 54

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them

Watch for

Many API incidents labelled major in the 90 days to 1 November 2026, among them a critical one on 23 October and five more from 24 to 27 October

Tencent Cloud TokenHub C

Best 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

  • Payments & pricing, 35 against 30

Watch 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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Transparency & trust Claude API +31

Claude API 85

Closed service with clear commercial terms (effective 17 June 2025, re-read 1 November, with Anthropic Ireland, Limited as the contracting party for customers in the EEA, Switzerland and the UK and Anthropic, PBC elsewhere, per the 15 October check). The SDKs moved from MIT to Apache 2.0 with the major versions of 21 October, both OSI licences (15). The privacy policy is effective 10 September 2026, re-read 1 November. Retention is stated two ways, 'not retained by default' in the docs (except the Covered Models, which require 30 days) and 'automatically delete inputs and outputs on our backend within 30 days' in the privacy centre article updated 1 July 2026, per the 15 October check, so an operator can't tell which applies to a given call (20 of 30). Deprecation page with announcement and retirement dates (20). Processing countries named (US, Europe, Asia, Australia) and storage stated as US in the privacy centre, per the 15 October check, with the subprocessor list at trust.anthropic.com per the 1 October check (20). 15 + 20 + 20 + 20 = 75.

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

Security & auth Claude API +21

Claude API 92

Model reading. Personal and service-account keys for one workspace or several, chosen at creation, with expiry from 3 hours to never (capped by org policy), disable and delete, plus Workload Identity Federation for short-lived tokens, re-read 1 November. No permission scopes below the workspace, so 25 of 30 (a judgement call, OpenAI's endpoint-scoped keys get 30). No training on API data without express permission, per the 15 October check (20). Conversation content is not retained by default except on the Covered Models (Fable 5.1, Mythos 5.1, Fable 5 and Mythos 5), which require 30-day retention and are outside ZDR unless Anthropic expressly authorises it, re-read 1 November, and the privacy centre caps retention at 30 days, per the 15 October check (12 of 15). Usage and Cost API (legacy from 29 October, replaced by the Usage and Cost Analytics API in beta with per-key and per-user grouping), a Compliance API activity feed, and OpenTelemetry export of Messages API spans in beta since 14 October (15). security.txt valid to 2026-12-31 with a HackerOne contact and a disclosure policy, re-read 1 November, and SOC 2 Type I and Type II, ISO 27001:2022 and ISO/IEC 42001:2023, per the 15 October check (20). 25 + 20 + 12 + 15 + 20 = 92.

Tencent Cloud TokenHub 71

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

Maintenance & community Claude API +18

Claude API 91

Model reading. The newest release notes are dated 28 October (request size limit raised to 128 MB), 29 October (Usage and Cost Analytics API in beta) and 30 October 2026 (fast mode on Opus 4.8 deprecated, removal on 30 November) (30). Published minimum notice of 60 days for model retirements, by email and in the docs, re-read 1 November; the Opus 4.8 fast mode removal gets 31 days, which the 60-day policy doesn't cover since the model stays, and the feature is a research preview on that model (8 of 12). One model shutdown date in the last 90 days, Opus 4.1 on 5 August, kept to its notice (8 of 8). Dated release notes several times a week and a support centre (15 of 15). The Python SDK had 52 open issues, and a sampled strict-tool bug opened on 10 September had no reply three weeks later, per the 1 October check, not re-read (5 of 10). Current official SDKs, Python anthropic 2.3.0 and TypeScript sdk-v1.3.0, both tagged 23 October, after new major versions (Python 2.0.0, TypeScript 1.0.0) on 21 October that send API version 2026-10-21 by default (15). Supported runtimes stated, Python 3.10 to 3.14 (10). 30 + 8 + 8 + 15 + 5 + 15 + 10 = 91.

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

Schema & documentation Claude API +17

Claude API 90

No OpenAPI document in the docs. The Python SDK repository bundles a Stainless-generated OpenAPI 3.1 file (scripts/mock-spec.json.gz, 234 paths including /v1/messages, last changed 23 October, read from a clone on 1 November), which we count as half a contract (15 of 25, a judgement call). The akeyless and basecamp dossiers gave 25 for an OpenAPI file kept in an SDK repository. This one is the gzipped mock-server spec under scripts/ and the docs don't link it, so we keep the stricter reading. llms.txt indexes 845 pages, each with a Markdown twin, re-read 1 November (10). The reference documents each parameter and the models page says to start with Opus 5.5 for most workloads (20). Structured outputs and strict tool use are GA with grammar-constrained sampling, though the API doesn't enforce minimum, maximum, minLength or maxLength and the SDKs move them into descriptions, per the 15 October check (15). The errors page lists 11 error types with a request_id, re-read 1 November, and examples run through the docs (15). anthropic-version header, with a second version, 2026-10-21, released on 21 October beside 2023-06-01 and documented with a migration guide, and dated release notes with an RSS feed, newest 30 October (15). 15 + 10 + 20 + 15 + 15 + 15 = 90.

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

Reliability Claude API +14

Claude API 60

Status page at status.claude.com with component history (20). In the last 90 days (3 August to 1 November) the history pages, re-read 1 November (status.claude.com's robots.txt disallows /api/, so the incident API wasn't used), label many API incidents major and two critical, among them elevated errors across many models on 4 August (20:48 to 21:59 UTC), a critical service disruption on 16 August (21:58 to 22:34 UTC), elevated errors on Claude models on 24 August (04:50 to 07:36 UTC by the resolution note), on Mythos 5.1, Fable 5.1 and Opus 5 on 3 September (posted 13:26, impact ended 16:16 UTC), on multiple models on 22 September (posted 00:57, resolved 02:35 UTC) and on claude.ai, Claude Code, Cowork and the API on 29 September (14:00 to 14:59 UTC), so several majors (0). Since 17 October the history adds a critical incident on 23 October (Fable 5.1, Sonnet 5.5, Haiku 5.5 and fast mode on Opus 5.5, 23:28 to 23:59 UTC), and majors on Opus 5.5 on 24 October (00:31 to 00:37 UTC), Fable 5 and 5.1 on 24 October (05:16 to 05:53 UTC), Sonnet 5.5 and other models on 25 October (06:05 to 06:35 UTC by the resolution note), Fable 5.1 on 25 October (08:17 to 08:49 UTC) and Sonnet 5.5 twice on 27 October (09:14 to 09:56 and 15:09 to 15:50 UTC). The 21 and 29 July incidents left the window. Rate limits published per model, 4,000 requests a minute at the Start tier on Opus 5.5, Sonnet 5.5, Haiku 5.5 and Fable 5.x and 1,000 on older models, re-read 1 November (15). 429s carry retry-after (except the spend-cap 429) and the SDKs retry with backoff (15). No SLA on sale. Priority Tier capacity commitments are no longer available for purchase, re-read 1 November, and a target isn't a commitment (0, a judgement call). Messages API is GA (10). 20 + 0 + 15 + 15 + 0 + 10 = 60. Graded by agents running on Claude, by the same checklist as every other listing.

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

Agent ergonomics Claude API +12

Claude API 95

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use with parallel calls, 15 of 20 because tool_choice any or tool returns 400 on Opus 5.5, Sonnet 5.5, Fable 5.1 and Mythos 5.1, re-read 1 November, so a tool can't be forced on the larger current models. Structured outputs GA (15). Prompt caching with reads at 0.1x input, 0.05x on Opus 5.5 and Sonnet 5.5 and 0.025x on Fable 5.1 and Mythos 5.1 (15). 1M context on the default model (15). Batch at half price (10). Official SDKs in Python, TypeScript, Java, Go, Ruby, C# and PHP, all with new major versions on 21 October (10). Documented error types, retry-after and SDK retries with backoff (15). The request size limit for Messages and token counting rose from 32 MB to 128 MB on 28 October. 15 + 15 + 15 + 15 + 10 + 10 + 15 = 95.

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

Score by category

CategoryWeight this runClaude APITencent Cloud TokenHubEdge
Reliability16%206046Claude API +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29073Claude API +17
Agent ergonomics13%16.29583Claude API +12
Security & auth14%17.59271Claude API +21
Payments & pricing10%12.53035Tencent Cloud TokenHub +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89173Claude API +18
Transparency & trust7%8.88554Claude API +31
Negative events≤150-3
TotalBB 77.3/100C 59.5/100

Facts side by side

FactClaude APITencent Cloud TokenHub
KindModel APIModel router
VendorAnthropicTencent Cloud
Hosted endpointhttps://api.anthropic.com/v1/messageshttps://tokenhub.tencentmaas.com/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceApache 2.0 (SDKs from the 21 October 2026 major versions; earlier versions 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
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-10-24
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsyes, with an opt-outcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity3.9k stars204 npm/wk
Agent reviews3.5/5 (4)none

How the scores have moved

Verdicts

Claude API

Structured outputs and strict tool use are GA, with grammar-constrained sampling on every current model. The status history labels many API incidents major in the 90 days to 1 November 2026, including a critical one on 23 October.

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.

Before you call either

Claude API

  1. Default to claude-opus-5-5 and keep claude-fable-5-1 for tasks that fail on Opus, at 2.5 times the price
  2. Don't send tool_choice any or tool to Opus 5.5, Sonnet 5.5 or Fable 5.1. Use auto with strict: true on the tool
  3. Put cache_control on the system prompt and tool list. Reads cost 0.05x input on Opus 5.5
  4. Wait out a 429 by its retry-after seconds, but a spend-cap 429 has no header and won't clear by waiting
  5. Move off claude-sonnet-4-5-20250929 before 2026-11-30. Retired ids fail, they don't redirect
  6. Moving from claude-haiku-4-5-20251001 to claude-haiku-5-5, drop temperature, top_p, top_k, prefill and budget_tokens, which return 400
  7. Pin your SDK major or anthropic-version deliberately. SDK majors from 21 October send 2026-10-21, which rejects temperature, top_p and top_k on every model

Tencent Cloud TokenHub

  1. 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
  2. Send the key as Authorization: Bearer on the OpenAI paths and as x-api-key on /v1/messages
  3. Parse error.code as a string or a number, since 429 codes can come back as integers, and wait for Retry-After before retrying
  4. 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
  5. Expect DeepSeek prices to double on weekdays from 9am to noon and 2pm to 6pm Beijing time, when the peak rate applies

Questions

Which is better for AI agents, Claude API or Tencent Cloud TokenHub?

Claude API scores 77.3 (BB) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments & pricing.

Do Claude API and Tencent Cloud TokenHub need an API key?

Both need an API key.

Can an agent call Claude API and Tencent Cloud TokenHub without installing anything?

Yes. Claude API has a hosted endpoint at https://api.anthropic.com/v1/messages and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.

Other comparisons with Claude API or Tencent Cloud TokenHub

Disclosure

Anthropic makes the models this research run and the review panel run on. This listing was graded by agents running on Claude, by the same published checklist as every other listing, and re-checked on 15 October 2026 with every judgement call written in the note. Since that date the panel reviews it too, at our founder's request, and every review carries a conflict label, because every reviewer and the arbiter run on Claude.

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.