Head to head · LLM inference · October 2026 research run
Amazon Bedrock vs Tencent Cloud TokenHub
Amazon Bedrock scores 81.7 (A) 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 830 models comparisons
Which one, for what
Best for Teams already on AWS who want Claude, GPT-6, Nova, Llama and other models under one IAM, billing and VPC boundary, with regional data controls and an SLA.
Ahead on
- Reliability, 80 against 46
- Schema & documentation, 94 against 73
- Agent ergonomics, 92 against 83
- Security & auth, 98 against 71
- Maintenance & community, 81 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
An AWS account, IAM setup and a Region choice come before the first call, and an agent can't sign up alone
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.
Reliability Amazon Bedrock +34
Amazon Bedrock 80
AWS Health Dashboard with per-service, per-Region feeds and a public history file (20). The history lists Amazon Bedrock as disrupted in ME-CENTRAL-1 (UAE) and ME-SOUTH-1 (Bahrain) since March 2026, where AWS said on 15 September 2026 (still inside the 90-day window on 6 November) that it can't restore resources held only there. No other Bedrock event appears in the history in the 90 days to 6 November; an EU-SOUTH-2 packet-loss event on 4 October named Bedrock AgentCore, not Bedrock. This counts as one major event (10). StatusGator's third-party mirror shows 'Increased Error Rates' warnings on 24, 26 and 27 August and 10 September that we couldn't find in AWS's own history, so we didn't score them. Per-model token quotas with default values in the AWS General Reference, such as 30,000,000 tokens a minute for Opus 5.5 global inference (15). The error guide gives exponential backoff with jitter for 429, 503 and 529 and says to honour Retry-After, and the SDKs retry ModelNotReadyException up to five times (15). SLA of 99.9 per cent a month per Region for the model APIs, last updated 4 October 2023 (10). Converse and the current Claude, GPT-6 and Nova 2 Lite models are GA (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).
Transparency & trust Amazon Bedrock +31
Amazon Bedrock 85
Closed service under the AWS Customer Agreement and Service Terms, with the SDKs and Smithy models under Apache-2.0 (18, as for S3). The data retention, abuse detection and security pages agree that Bedrock stores nothing by default, name the models that retain traffic and for how long, and say retained data isn't shared with providers. The retention page's default mode says AWS 'may retain the data for safety and abuse-prevention purposes' without a period, and a legacy provider_data_share mode is kept though sharing isn't supported (25 of 30). A written lifecycle policy with Legacy and EOL dates per model, but the legacy table's 34-day Legacy periods for five Claude models in some Regions contradict its own 6-month floor (15 of 20, down from 18). AWS's sub-processor list, per the 4 October S3 check, and per-Region, geographic and global inference options, with global routing able to process data in any commercial Region (18 of 20).
Tencent Cloud TokenHub 54
Closed service under the TokenHub Terms of Service (effective 14 September 2026), the SLA (23 April 2026), a special note on third-party deployed models and the Tencent Cloud Service Agreement, naming Tencent Cloud Computing (Beijing) Co., Ltd. The CLI is Apache-2.0 (18 of 30). The terms and the FAQ agree that inputs are processed on the customer's instructions and not used for training, and clause 2.14 limits retention to what the service needs without periods. The TokenHub privacy policy on privacy.qq.com renders only with JavaScript and was not read (15 of 30). Dated retirement notices, shutdown dates in the model list, a pre-offline status in /v1/models and a DiscontinuedAt field in the control API. Clause 6.3 refunds paid, unused tokens when a third-party model is removed. No minimum notice period is written (13 of 20). Clause 2.13 places processing generally in mainland China for the China site and in Singapore for the international site, and the third-party model list names DeepSeek's Hangzhou company with a link to its terms. No subprocessor list was found (13 of 20).
Security & auth Amazon Bedrock +27
Amazon Bedrock 98
Model reading. IAM with SigV4, roles and STS session credentials, policies down to a model or inference-profile ARN, short-term API keys that expire within 12 hours, long-term keys with expiry and reset, and condition keys that can deny bearer tokens altogether (30). The security page says customer data isn't shared with model providers or used to improve the base models (20). The abuse detection page says Bedrock stores no inputs or outputs by default, and a per-Region none mode blocks models that require retention, but Claude Fable 5 and 5.1 keep all traffic up to 30 days and GPT-6 and GPT-5.x keep flagged traffic up to 30 days (13 of 15, a judgement call; Anthropic's own API got 12 for the same Fable exception without an account-level block). CloudTrail logs API calls, and model invocation logging can send prompts and responses to S3 or CloudWatch Logs (15). Bedrock is in ISO, SOC and CSA STAR Level 2 scope, HIPAA eligible and FedRAMP High in GovCloud (US-West) per its security page, with a vulnerability disclosure programme on HackerOne, and the aws.amazon.com security.txt, expired on 6 October, was renewed with Expires 2027-10-16 when read on 6 November (20). Up from 96 on 6 October for that reason.
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).
Schema & documentation Amazon Bedrock +21
Amazon Bedrock 94
Model reading. No OpenAPI, but the bedrock-runtime and bedrock Smithy models are public in aws/api-models-aws with types, required members and enums, counted as for S3 (25). llms.txt for the user guide with about 2,000 lines, each page with a Markdown twin (10). Model cards state context, output limits, endpoints and supported functions per model, and the guide now recommends bedrock-runtime for new work, but support for each API, endpoint and feature changes model by model (16 of 20). Structured outputs compile JSON Schema to a grammar, with minimum, maximum and string lengths supported, though some inference profiles don't support it, such as Haiku 4.5 through the India profile (13 of 15). Every operation lists typed errors with HTTP codes and links to a troubleshooting page with causes and fixes, and examples run through the guide (15). API version 2023-09-30 and a dated document history with an RSS feed, newest entry 30 October 2026, with structured outputs for Claude on both endpoints added on 18 October (15).
Tencent Cloud TokenHub 73
Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use deepseek-v3, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry /v1, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15).
Agent ergonomics Amazon Bedrock +9
Amazon Bedrock 92
Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Converse takes tools with toolChoice auto, any or a named tool and strict: true, but forced choice depends on the model behind it (17 of 20). Structured outputs on supported models only (13 of 15). Explicit and implicit prompt caching, cache reads at $0.20 per million on Opus 5.5, 0.05x input, with 5-minute and 1-hour TTLs (15). 1M-token context on Opus 5.5, Sonnet 5.5 and Nova 2 Lite, a judgement call since Bedrock has no default model (15). Batch at half price on supported models, but the pricing page shows none for Opus 5.5 or Sonnet 5.5, while Flex is half price on Nova (7 of 10). AWS SDKs in every major language plus token generators for Python, JavaScript and Java (10). Typed errors with recovery advice per code (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).
Maintenance & community Amazon Bedrock +8
Amazon Bedrock 81
Model reading. The last model or API change is 30 October 2026 (OpenAI model API support and cross-Region inference in GovCloud), after structured outputs for Claude on both endpoints on 18 October (30). Models launched since 7 September 2026 get a 6-month or 45-day Legacy period, but the legacy page, which promises at least 6 months in Legacy, lists Claude 3 Haiku, 3 Sonnet, 3.5 Sonnet, 3.5 Sonnet v2 and 3.7 Sonnet as Legacy from 10 or 13 October with end of life on 13 November in several Regions, about 34 days (6 of 12, down from 10). Six models reached end of life in the 90 days to 6 November on five dates, Command R and R+ on 19 August, Claude 3 Haiku on 10 September, Nova Sonic on 14 September, Nova Canvas and Nova Reel on 30 September and Claude Sonnet 4 on 14 October (3 of 8, down from 4). Dated document history several times a month, What's New and re:Post, with direct support on a paid plan (12 of 15). SDK issue replies not sampled (5 of 10). Current official SDKs, boto3 1.43.125 on 5 November and @aws-sdk/client-bedrock-runtime 3.1163.0 (15). Supported runtimes stated, Python 3.10 or later and Node 20 or later (10). Down from 86 on 6 October.
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).
Score by category
| Category | Weight this run | Amazon Bedrock | Tencent Cloud TokenHub | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 80 | 46 | Amazon Bedrock +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 94 | 73 | Amazon Bedrock +21 |
| Agent ergonomics | 13%16.2 | 92 | 83 | Amazon Bedrock +9 |
| Security & auth | 14%17.5 | 98 | 71 | Amazon Bedrock +27 |
| Payments & pricing | 10%12.5 | 30 | 35 | Tencent Cloud TokenHub +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 81 | 73 | Amazon Bedrock +8 |
| Transparency & trust | 7%8.8 | 85 | 54 | Amazon Bedrock +31 |
| Negative events | ≤15 | 0 | -3 | |
| Total | A 81.7/100 | C 59.5/100 |
Facts side by side
| Fact | Amazon Bedrock | Tencent Cloud TokenHub |
|---|---|---|
| Kind | Model API | Model router |
| Vendor | Amazon Web Services | Tencent Cloud |
| Hosted endpoint | https://bedrock-runtime.us-east-1.amazonaws.com | https://tokenhub.tencentmaas.com/v1 |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under the AWS Customer Agreement and Service Terms. Third-party models carry their providers' licence terms. The AWS SDKs and the Smithy service models are Apache-2.0 | 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 documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-10-24 |
| Terms last updated | 2026-10-01 | couldn't be read |
| Privacy policy last updated | 2026-05-18 | couldn't be read |
| Customer content may train models | yes, with an opt-out | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 21.8M npm/wk | 204 npm/wk |
Verdicts
Amazon Bedrock
Bedrock reaches Claude, GPT-6, Nova, Llama and other families through one IAM-controlled API, with a 99.9 per cent SLA and a per-Region zero-retention switch. Setup needs an AWS account, IAM permissions and a Region, capabilities vary by model, and some Regions gave five older Claude models about 34 days of notice.
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
Amazon Bedrock
- Use the geographic or global inference ID from the model card, such as
global.anthropic.claude-opus-5-5. Global routing is cheaper but can process data in any commercial Region - Set
data_retention_modetononein each Region before sending sensitive data. Models that need retention then return ValidationException - Back off with jitter on 429 ThrottlingException, 503 and 529
overloaded_error, and honourRetry-Afterwhen it's sent - Generate short-term API keys from an IAM role for production. Long-term keys create an IAM user and AWS marks them exploration only
- Call ListFoundationModels in your Region and read
modelLifecyclebefore pinning a model ID. Claude 3.x IDs in several Regions stop working on 13 November 2026 and requests don't redirect
Tencent Cloud TokenHub
- Use
https://tokenhub.tencentmaas.com/v1with keys made for Guangzhou andhttps://tokenhub-intl.tencentmaas.com/v1with keys made for Singapore. Keys do not work across the two - Send the key as
Authorization: Beareron the OpenAI paths and asx-api-keyon/v1/messages - Parse
error.codeas a string or a number, since 429 codes can come back as integers, and wait forRetry-Afterbefore retrying - Take model ids from
GET /v1/modelsand watch forpre-offline. The quickstart'sdeepseek-v3example 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
Questions
Which is better for AI agents, Amazon Bedrock or Tencent Cloud TokenHub?
Amazon Bedrock scores 81.7 (A) 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 Amazon Bedrock and Tencent Cloud TokenHub need an API key?
Amazon Bedrock takes an API key or an OAuth sign-in. Tencent Cloud TokenHub needs an API key.
Can an agent call Amazon Bedrock and Tencent Cloud TokenHub without installing anything?
Yes. Amazon Bedrock has a hosted endpoint at https://bedrock-runtime.us-east-1.amazonaws.com and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.
Other comparisons with Amazon Bedrock or Tencent Cloud TokenHub
- Amazon Bedrock vs Claude API
- Amazon Bedrock vs Antseed
- Amazon Bedrock vs Azure OpenAI in Foundry Models
- Amazon Bedrock vs BlockRun.AI
- Amazon Bedrock vs Cerebras Inference
- Amazon Bedrock vs Cloudflare AI Gateway
- Amazon Bedrock vs Cloudflare Workers AI
- Amazon Bedrock vs Cohere Chat API (Command models)
- Amazon Bedrock vs DeepInfra
- Amazon Bedrock vs DeepSeek API
- Amazon Bedrock vs Eden AI
- Amazon Bedrock vs Glimpse
- Amazon Bedrock vs Fireworks AI Inference
- Amazon Bedrock vs Gemini Developer API
- Amazon Bedrock vs GroqCloud
- Amazon Bedrock vs Hugging Face Inference Providers
- Amazon Bedrock vs Inkling 2 Small
- Amazon Bedrock vs Jais 3
- Amazon Bedrock vs Meta Model API
- Amazon Bedrock vs MiniMax API
- Amazon Bedrock vs Mistral AI API
- Amazon Bedrock vs Muse Spark Open
- Amazon Bedrock vs Nemotron 3.5 Super VL
- Amazon Bedrock vs Novita AI
- Amazon Bedrock vs OpenAI API
- Amazon Bedrock vs OpenRouter
- Amazon Bedrock vs Prism Inference
- Amazon Bedrock vs Router.com (Ramp Router)
- Amazon Bedrock vs Beam 1.0
- Amazon Bedrock vs RouterPlus
- Amazon Bedrock vs SambaCloud
- Amazon Bedrock vs SiliconFlow
- Amazon Bedrock vs Simplismart
- Amazon Bedrock vs StepFun API
- Amazon Bedrock vs SWE-2 Flash
- Amazon Bedrock vs Together AI Inference
- Amazon Bedrock vs Vercel AI Gateway
- Amazon Bedrock vs Vertex AI (Gemini Enterprise Agent Platform)
- Amazon Bedrock vs xAI API (Grok)
- Claude API vs Tencent Cloud TokenHub
- Azure OpenAI in Foundry Models vs Tencent Cloud TokenHub
- BlockRun.AI vs Tencent Cloud TokenHub
- Cerebras Inference vs Tencent Cloud TokenHub
- Cloudflare AI Gateway vs Tencent Cloud TokenHub
- Cloudflare Workers AI vs Tencent Cloud TokenHub
- Cohere Chat API (Command models) vs Tencent Cloud TokenHub
- DeepInfra vs Tencent Cloud TokenHub
- DeepSeek API vs Tencent Cloud TokenHub
- Glimpse vs Tencent Cloud TokenHub
- Fireworks AI Inference vs Tencent Cloud TokenHub
- Gemini Developer API vs Tencent Cloud TokenHub
- GroqCloud vs Tencent Cloud TokenHub
- Inkling 2 Small vs Tencent Cloud TokenHub
- Jais 3 vs Tencent Cloud TokenHub
- Meta Model API vs Tencent Cloud TokenHub
- MiniMax API vs Tencent Cloud TokenHub
- Mistral AI API vs Tencent Cloud TokenHub
- Muse Spark Open vs Tencent Cloud TokenHub
- Novita AI vs Tencent Cloud TokenHub
- OpenAI API vs Tencent Cloud TokenHub
- OpenRouter vs Tencent Cloud TokenHub
- Beam 1.0 vs Tencent Cloud TokenHub
- SambaCloud vs Tencent Cloud TokenHub
- SiliconFlow vs Tencent Cloud TokenHub
- Simplismart vs Tencent Cloud TokenHub
- StepFun API vs Tencent Cloud TokenHub
- SWE-2 Flash vs Tencent Cloud TokenHub
- Tencent Cloud TokenHub vs Together AI Inference
- Tencent Cloud TokenHub vs Vertex AI (Gemini Enterprise Agent Platform)
- Tencent Cloud TokenHub vs xAI API (Grok)
- Antseed vs Tencent Cloud TokenHub
- Eden AI vs Tencent Cloud TokenHub
- Hugging Face Inference Providers vs Tencent Cloud TokenHub
- LiteLLM vs Tencent Cloud TokenHub
- Router.com (Ramp Router) vs Tencent Cloud TokenHub
- RouterPlus vs Tencent Cloud TokenHub
- Tencent Cloud TokenHub vs Vercel AI Gateway
- Nemotron 3.5 Super VL vs Tencent Cloud TokenHub
- Prism Inference vs Tencent Cloud TokenHub
Machine-readable
- This page as Markdown
/compare/amazon-bedrock-vs-tencent-tokenhub.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-bedrock.json·/api/v1/tools/tencent-tokenhub.json - From a terminal
anchor compare amazon-bedrock tencent-tokenhub(the CLI) - Over MCP
compare_tools {"a": "amazon-bedrock", "b": "tencent-tokenhub"}at/mcp, no key