{ "data": { "a": { "slug": "amazon-bedrock", "name": "Amazon Bedrock", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/bedrock/", "kind": "model", "category": "inference", "summary": "AWS's managed API for foundation models from Anthropic, OpenAI, Amazon, Meta, Mistral, DeepSeek, Qwen, xAI and others, called through the Converse API or OpenAI- and Anthropic-compatible endpoints under one AWS account.", "url": "https://www.anchorterminal.com/tools/amazon-bedrock", "markdownUrl": "https://www.anchorterminal.com/tools/amazon-bedrock.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/amazon-bedrock.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/amazon-bedrock.json", "dns": "amazon-bedrock.grade.anchorterminal.com", "repo": "https://github.com/aws/api-models-aws", "license": "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", "transports": [ "http" ], "remoteUrl": "https://bedrock-runtime.us-east-1.amazonaws.com", "packages": [ { "registry": "pypi", "name": "boto3" }, { "registry": "npm", "name": "@aws-sdk/client-bedrock-runtime" } ], "auth": "mixed", "authNotes": "AWS Signature Version 4 with IAM users, roles or short-lived STS credentials, and IAM policies that can name single model or inference-profile ARNs. Bedrock API keys go in an `Authorization: Bearer` header. Short-term keys last up to 12 hours and inherit the caller's IAM permissions; long-term keys create an IAM user and are marked for exploration only. Endpoints are regional, `bedrock-runtime.\u003cregion\u003e.amazonaws.com` and `bedrock-mantle.\u003cregion\u003e.api.aws`.", "pricing": "usage", "pricingNotes": "Per-token prices per model and Region, with Standard, Priority, Flex and Reserved tiers. Claude Opus 5.5 costs $4/$20 per million tokens through global cross-Region inference and $4.40/$22 through geographic or in-Region inference, cache reads $0.20. Cache reads on Claude Sonnet 5.5 were cut by half from 7 October 2026. Batch is half price on supported models but was not shown for Opus 5.5 or Sonnet 5.5. New AWS accounts get up to $200 in Free Tier credits (https://aws.amazon.com/bedrock/pricing/, rates per AWS's price feed of 30 September 2026; the page's tables are drawn by script and were not readable on 6 November).", "priceSummary": "from $0.30 / 1M in", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page or in the user guide's llms.txt (checked 2026-11-06). Access needs an AWS account.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 21825916, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.aws.amazon.com/bedrock/latest/userguide/what-is-bedrock.html", "rateLimitsUrl": "https://docs.aws.amazon.com/general/latest/gr/bedrock.html", "llmsTxt": "https://docs.aws.amazon.com/bedrock/latest/userguide/llms.txt", "capabilities": [ "inference.llm", "inference.open-weights" ], "tags": [ "official", "hosted", "model", "open-weights", "enterprise", "usage-priced", "llms-txt", "python", "typescript", "status-page" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 81.7, "grade": "A", "agentReady": true, "rank": 8, "ranked": true, "rankOf": 1486, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 92, "maintenance": 81, "payments": 30, "reliability": 80, "schema": 94, "security": 98, "transparency": 85 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "One API and one bill for Anthropic, OpenAI, Amazon, Meta, Mistral, DeepSeek, Qwen, xAI and other model families", "IAM policies can limit a caller to named model ARNs, and short-term API keys expire within 12 hours", "A `none` data retention mode per Region blocks any model that would store prompts", "Published SLA of 99.9 per cent a month per Region with service credits", "Per-model token quotas published with default values, for example 30,000,000 tokens a minute for Opus 5.5 global inference" ], "weaknesses": [ "An AWS account, IAM setup and a Region choice come before the first call, and an agent can't sign up alone", "Batch inference isn't shown for Claude Opus 5.5 or Sonnet 5.5, and since 26 October batch completion isn't guaranteed", "Claude Fable 5 and 5.1 retain all traffic up to 30 days, and AWS may review flagged prompts", "Five older Claude models went Legacy on 10 or 13 October 2026 with end of life on 13 November in some Regions, against the 6-month floor the policy states", "The Middle East (UAE) and (Bahrain) Regions have been disrupted since March 2026, and AWS says some data there can't be restored" ], "agentNotes": [ "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_mode` to `none` in 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 honour `Retry-After` when 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 `modelLifecycle` before pinning a model ID. Claude 3.x IDs in several Regions stop working on 13 November 2026 and requests don't redirect" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "A", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 81.7 } ], "editorialScores": { "ergonomics": 92, "maintenance": 81, "payments": 30, "reliability": 80, "schema": 94, "security": 98, "transparency": 76 }, "provenanceScore": 94, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install boto3 # or: npm i @aws-sdk/client-bedrock-runtime", "http": "curl -X POST \"https://bedrock-runtime.us-east-1.amazonaws.com/model/us.anthropic.claude-sonnet-4-6/converse\" \\\n -H \"Content-Type: application/json\" \\\n -H \"Authorization: Bearer $AWS_BEARER_TOKEN_BEDROCK\" \\\n -d '{\"messages\": [{\"role\": \"user\", \"content\": [{\"text\": \"Hello\"}]}]}'" }, "letme": { "capability": "https://letme.dev/inference.llm", "tool": "https://letme.dev/amazon-bedrock" }, "sameCompany": [ "amazon-nova-embeddings", "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "amazon-nova-sonic", "agentcore-memory", "agentcore-identity", "aws-secrets-manager", "agentcore-web-search", "aws-mcp-servers", "amazon-ses", "amazon-location", "amazon-translate", "amazon-ads-api", "amazon-creators-api" ], "area": "models", "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "amazon.com", "domainRegistered": "1994-11-01", "domainNote": "The endpoints are on amazonaws.com and api.aws, both AWS domains. The security.txt on aws.amazon.com had expired on 2026-09-24 and was renewed, with Expires 2027-10-16, when read on 2026-11-06.", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/bedrock/latest/userguide/doc-history.html", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "AWS's public history feed (historyevents.json) lists Amazon Bedrock as disrupted in the ME-CENTRAL-1 and ME-SOUTH-1 Regions since March 2026, with a last update on 15 September 2026, and no Bedrock event in other Regions in the 90 days to 6 November 2026. An EU-SOUTH-2 packet-loss event on 4 October 2026 named Bedrock AgentCore, not Bedrock.", "The pricing page fills its tables by script. Prices here come from AWS's public price feed of 30 September 2026; the bedrockfoundationmodels feed read on 6 November (published 12 October) carries only rate codes." ], "score": 94 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/amazon-bedrock.json", "live": { "slug": "amazon-bedrock", "probe": { "target": "https://bedrock-runtime.us-east-1.amazonaws.com", "method": "get", "lastAt": "2026-11-07T18:20:09.570975096Z", "lastOk": true, "lastStatus": 404, "lastMs": 339, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 269, "p95ms24h": 352, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "versions": [ { "registry": "npm", "name": "@aws-sdk/client-bedrock-runtime", "version": "3.1164.0", "seenAt": "2026-11-06T23:05:19.602032841Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.126", "released": "2026-11-06", "seenAt": "2026-11-06T23:05:17.831478687Z" } ], "githubStars": 229, "npmWeekly": 21825916, "pypiWeekly": 637851852, "securityTxt": { "url": "https://amazon.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:18.354437696Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/bedrock/latest/userguide/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:17.63045618Z" }, "pages": [ { "url": "https://docs.aws.amazon.com/bedrock/latest/userguide/model-lifecycle-legacy.html", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:05:11.906374144Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "dce416908c57" } ], "updatedAt": "2026-11-07T18:20:09.570975096Z" } }, "answer": "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 \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": 700, "ranked": true, "rankOf": 1486, "categoryRank": 24, "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-07T18:20:59.348953122Z", "lastOk": true, "lastStatus": 404, "lastMs": 813, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 839, "p95ms24h": 1161, "samples24h": 239, "samples30d": 1375, "days": [ { "date": "2026-11-01", "probes": 18, "ok": 18 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "versions": [ { "registry": "npm", "name": "tencent-tokenhub-cli", "version": "1.0.2", "seenAt": "2026-11-07T00:10:56.11915484Z" } ], "githubStars": 12, "npmWeekly": 563, "securityTxt": { "url": "https://tencentmaas.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-07T16:00:51.946401273Z" }, "llmsTxt": { "url": "https://cloud.tencent.com/document/product/1823/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:07.341361344Z" }, "pages": [ { "url": "https://cloud.tencent.com/document/product/1823/130675", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:01:36.805781891Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2287", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:20.295617745Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2469", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:22.306047727Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2496", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:24.307216514Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2511", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:26.305052043Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2516", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:28.308079433Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2524", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:30.306693329Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2538", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:34.709118103Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://privacy.qq.com/document/preview/91d5fd3c98ce4468ae462ac59233bba2", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:17:28.357626414Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/document/product/301/129852", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:01:36.816423311Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" } ], "github": { "repo": "tencentcloud/thcli", "checkedAt": "2026-11-02T08:23:47.915102454Z", "stars": 12, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-30T06:58:13Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 4 }, "updatedAt": "2026-11-07T18:20:59.348953122Z" } }, "edges": [ { "by": 34, "category": "reliability", "leads": "amazon-bedrock", "name": "Reliability", "reasons": { "a": "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).", "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": 80, "b": 46 } }, { "by": 31, "category": "transparency", "leads": "amazon-bedrock", "name": "Transparency \u0026 trust", "reasons": { "a": "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).", "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": 85, "b": 54 } }, { "by": 27, "category": "security", "leads": "amazon-bedrock", "name": "Security \u0026 auth", "reasons": { "a": "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.", "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": 98, "b": 71 } }, { "by": 21, "category": "schema", "leads": "amazon-bedrock", "name": "Schema \u0026 documentation", "reasons": { "a": "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).", "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": 94, "b": 73 } }, { "by": 9, "category": "ergonomics", "leads": "amazon-bedrock", "name": "Agent ergonomics", "reasons": { "a": "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).", "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": 92, "b": 83 } }, { "by": 8, "category": "maintenance", "leads": "amazon-bedrock", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "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\u0026A 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)." }, "scores": { "a": 81, "b": 73 } } ], "facts": [ { "a": "Model API", "b": "Model router", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Tencent Cloud", "name": "Vendor" }, { "a": "https://bedrock-runtime.us-east-1.amazonaws.com", "b": "https://tokenhub.tencentmaas.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "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-10-30", "b": "2026-10-24", "name": "Last release" }, { "a": "2026-10-01", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "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": "21.8M npm/wk", "b": "204 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "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 \u0026 pricing.", "question": "Which is better for AI agents, Amazon Bedrock or Tencent Cloud TokenHub?" }, { "answer": "Amazon Bedrock takes an API key or an OAuth sign-in. Tencent Cloud TokenHub needs an API key.", "question": "Do Amazon Bedrock and Tencent Cloud TokenHub need an API key?" }, { "answer": "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.", "question": "Can an agent call Amazon Bedrock and Tencent Cloud TokenHub without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 46", "Schema \u0026 documentation, 94 against 73", "Agent ergonomics, 92 against 83", "Security \u0026 auth, 98 against 71", "Maintenance \u0026 community, 81 against 73", "Transparency \u0026 trust, 85 against 54" ], "also": [ "Agent-ready, a grade of BB or better", "No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them" ], "goodFor": "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.", "slug": "amazon-bedrock", "watchFor": "An AWS account, IAM setup and a Region choice come before the first call, and an agent can't sign up alone" }, { "aheadOn": [ "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": null, "job": { "capability": "inference.llm", "name": "LLM inference" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-anthropic-api.json", "title": "Amazon Bedrock vs Claude API", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-anthropic-api" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-antseed.json", "title": "Amazon Bedrock vs Antseed", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-antseed" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-azure-openai.json", "title": "Amazon Bedrock vs Azure OpenAI in Foundry Models", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-azure-openai" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-blockrun-ai.json", "title": "Amazon Bedrock vs BlockRun.AI", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-blockrun-ai" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-cerebras-inference.json", "title": "Amazon Bedrock vs Cerebras Inference", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-cerebras-inference" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-cloudflare-ai-gateway.json", "title": "Amazon Bedrock vs Cloudflare AI Gateway", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-cloudflare-ai-gateway" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-cloudflare-workers-ai.json", "title": "Amazon Bedrock vs Cloudflare Workers AI", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-cloudflare-workers-ai" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-cohere-chat.json", "title": "Amazon Bedrock vs Cohere Chat API (Command models)", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-cohere-chat" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-deepinfra.json", "title": "Amazon Bedrock vs DeepInfra", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-deepinfra" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-deepseek-api.json", "title": "Amazon Bedrock vs DeepSeek API", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-deepseek-api" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-eden-ai.json", "title": "Amazon Bedrock vs Eden AI", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-eden-ai" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-elorian-glimpse.json", "title": "Amazon Bedrock vs Glimpse", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-fireworks-inference.json", "title": "Amazon Bedrock vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-fireworks-inference" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-gemini-api.json", "title": "Amazon Bedrock vs Gemini Developer API", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-gemini-api" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-groq.json", "title": "Amazon Bedrock vs GroqCloud", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-groq" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-hugging-face-inference-providers.json", "title": "Amazon Bedrock vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-hugging-face-inference-providers" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-inkling-2-small.json", "title": "Amazon Bedrock vs Inkling 2 Small", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-inkling-2-small" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-jais-3.json", "title": "Amazon Bedrock vs Jais 3", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-jais-3" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-meta-model-api.json", "title": "Amazon Bedrock vs Meta Model API", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-meta-model-api" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-minimax-api.json", "title": "Amazon Bedrock vs MiniMax API", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-minimax-api" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-mistral-api.json", "title": "Amazon Bedrock vs Mistral AI API", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-mistral-api" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-muse-spark-open.json", "title": "Amazon Bedrock vs Muse Spark Open", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-muse-spark-open" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-nemotron-3-5-super-vl.json", "title": "Amazon Bedrock vs Nemotron 3.5 Super VL", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-nemotron-3-5-super-vl" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-novita-ai.json", "title": "Amazon Bedrock vs Novita AI", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-novita-ai" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-openai-api.json", "title": "Amazon Bedrock vs OpenAI API", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-openai-api" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-openrouter.json", "title": "Amazon Bedrock vs OpenRouter", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-openrouter" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-prism-inference.json", "title": "Amazon Bedrock vs Prism Inference", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-prism-inference" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-ramp-router.json", "title": "Amazon Bedrock vs Router.com (Ramp Router)", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-ramp-router" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-reflection-beam.json", "title": "Amazon Bedrock vs Beam 1.0", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-reflection-beam" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-routerplus.json", "title": "Amazon Bedrock vs RouterPlus", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-sambanova.json", "title": "Amazon Bedrock vs SambaCloud", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-sambanova" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-siliconflow.json", "title": "Amazon Bedrock vs SiliconFlow", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-siliconflow" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-simplismart.json", "title": "Amazon Bedrock vs Simplismart", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-stepfun-api.json", "title": "Amazon Bedrock vs StepFun API", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-stepfun-api" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-swe-2-flash.json", "title": "Amazon Bedrock vs SWE-2 Flash", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-swe-2-flash" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-together-inference.json", "title": "Amazon Bedrock vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-vercel-ai-gateway.json", "title": "Amazon Bedrock vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-vercel-ai-gateway" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-vertex-ai.json", "title": "Amazon Bedrock vs Vertex AI (Gemini Enterprise Agent Platform)", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-vertex-ai" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-xai-api.json", "title": "Amazon Bedrock vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-xai-api" }, { "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/azure-openai-vs-tencent-tokenhub.json", "title": "Azure OpenAI in Foundry Models vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub" }, { "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-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-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-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-tencent-tokenhub.json", "title": "Cohere Chat API (Command models) vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub" }, { "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/inkling-2-small-vs-tencent-tokenhub.json", "title": "Inkling 2 Small vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/inkling-2-small-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/swe-2-flash-vs-tencent-tokenhub.json", "title": "SWE-2 Flash vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/swe-2-flash-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/tencent-tokenhub-vs-vertex-ai.json", "title": "Tencent Cloud TokenHub vs Vertex AI (Gemini Enterprise Agent Platform)", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vertex-ai" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api.json", "title": "Tencent Cloud TokenHub vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api" }, { "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/eden-ai-vs-tencent-tokenhub.json", "title": "Eden AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/eden-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.json", "title": "Hugging Face Inference Providers vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/litellm-vs-tencent-tokenhub.json", "title": "LiteLLM vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/litellm-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" }, { "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" } ], "panel": null, "scores": [ { "amazon-bedrock": 80, "by": 34, "edge": "amazon-bedrock", "key": "reliability", "name": "Reliability", "tencent-tokenhub": 46, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-bedrock": 94, "by": 21, "edge": "amazon-bedrock", "key": "schema", "name": "Schema \u0026 documentation", "tencent-tokenhub": 73, "weight": 13 }, { "amazon-bedrock": 92, "by": 9, "edge": "amazon-bedrock", "key": "ergonomics", "name": "Agent ergonomics", "tencent-tokenhub": 83, "weight": 13 }, { "amazon-bedrock": 98, "by": 27, "edge": "amazon-bedrock", "key": "security", "name": "Security \u0026 auth", "tencent-tokenhub": 71, "weight": 14 }, { "amazon-bedrock": 30, "by": 5, "edge": "tencent-tokenhub", "key": "payments", "name": "Payments \u0026 pricing", "tencent-tokenhub": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-bedrock": 81, "by": 8, "edge": "amazon-bedrock", "key": "maintenance", "name": "Maintenance \u0026 community", "tencent-tokenhub": 73, "weight": 7 }, { "amazon-bedrock": 85, "by": 31, "edge": "amazon-bedrock", "key": "transparency", "name": "Transparency \u0026 trust", "tencent-tokenhub": 54, "weight": 7 } ], "summary": "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 \u0026 pricing. Both do llm inference.", "tasks": null, "tutorials": [], "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-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/amazon-bedrock-vs-tencent-tokenhub", "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub.min.md" }, "markdown": "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 \u0026 pricing. Both do llm inference.\n\n- Amazon Bedrock: grade A, 81.7/100, rank #8 of 1486. Markdown https://www.anchorterminal.com/tools/amazon-bedrock.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-bedrock.json\n- Tencent Cloud TokenHub: grade C, 59.5/100, rank #700 of 1486. 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 830 models comparisons: https://www.anchorterminal.com/compare/inference/index.md\n\n## Which one, for what\n\n### Amazon Bedrock (A)\n\nGood 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.\n\nAhead on:\n- Reliability, 80 against 46\n- Schema \u0026 documentation, 94 against 73\n- Agent ergonomics, 92 against 83\n- Security \u0026 auth, 98 against 71\n- Maintenance \u0026 community, 81 against 73\n- Transparency \u0026 trust, 85 against 54\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them\n\nWatch for: An AWS account, IAM setup and a Region choice come before the first call, and an agent can't sign up alone\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- 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### Reliability: Amazon Bedrock +34\n\n- 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).\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### Transparency \u0026 trust: Amazon Bedrock +31\n\n- 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).\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### Security \u0026 auth: Amazon Bedrock +27\n\n- 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.\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: Amazon Bedrock +21\n\n- 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).\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: Amazon Bedrock +9\n\n- 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).\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### Maintenance \u0026 community: Amazon Bedrock +8\n\n- 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.\n- 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\u0026A 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).\n\n## Score by category\n\n| Category | Weight | Amazon Bedrock | Tencent Cloud TokenHub | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 46 | Amazon Bedrock +34 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 94 | 73 | Amazon Bedrock +21 |\n| Agent ergonomics | 13% (16.2 this run) | 92 | 83 | Amazon Bedrock +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 98 | 71 | Amazon Bedrock +27 |\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) | 81 | 73 | Amazon Bedrock +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 85 | 54 | Amazon Bedrock +31 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **81.7 · A** | **59.5 · C** | |\n\n## Facts side by side\n\n| Fact | Amazon Bedrock | Tencent Cloud TokenHub |\n| --- | --- | --- |\n| Kind | Model API | Model router |\n| Vendor | Amazon Web Services | Tencent Cloud |\n| Hosted endpoint | `https://bedrock-runtime.us-east-1.amazonaws.com` | `https://tokenhub.tencentmaas.com/v1` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-30 | 2026-10-24 |\n| Terms last updated | 2026-10-01 | couldn't be read |\n| Privacy policy last updated | 2026-05-18 | couldn't be read |\n| Customer content may train models | yes, with an opt-out | couldn't be read |\n| Terms restrict automated access | yes | 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 | 21.8M npm/wk | 204 npm/wk |\n\n## Verdicts\n\n**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.\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### Amazon Bedrock\n\n1. 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\n2. Set `data_retention_mode` to `none` in each Region before sending sensitive data. Models that need retention then return ValidationException\n3. Back off with jitter on 429 ThrottlingException, 503 and 529 `overloaded_error`, and honour `Retry-After` when it's sent\n4. Generate short-term API keys from an IAM role for production. Long-term keys create an IAM user and AWS marks them exploration only\n5. Call ListFoundationModels in your Region and read `modelLifecycle` before pinning a model ID. Claude 3.x IDs in several Regions stop working on 13 November 2026 and requests don't redirect\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, Amazon Bedrock or Tencent Cloud TokenHub?\n\nAmazon 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 \u0026 pricing.\n\n### Do Amazon Bedrock and Tencent Cloud TokenHub need an API key?\n\nAmazon Bedrock takes an API key or an OAuth sign-in. Tencent Cloud TokenHub needs an API key.\n\n### Can an agent call Amazon Bedrock and Tencent Cloud TokenHub without installing anything?\n\nYes. 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.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-bedrock\", \"b\": \"tencent-tokenhub\"}`. From a terminal: `anchor compare amazon-bedrock tencent-tokenhub`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-bedrock.json and https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n\n## Other comparisons with Amazon Bedrock or Tencent Cloud TokenHub\n\n- [Amazon Bedrock vs Claude API](https://www.anchorterminal.com/compare/amazon-bedrock-vs-anthropic-api.md)\n- [Amazon Bedrock vs Antseed](https://www.anchorterminal.com/compare/amazon-bedrock-vs-antseed.md)\n- [Amazon Bedrock vs Azure OpenAI in Foundry Models](https://www.anchorterminal.com/compare/amazon-bedrock-vs-azure-openai.md)\n- [Amazon Bedrock vs BlockRun.AI](https://www.anchorterminal.com/compare/amazon-bedrock-vs-blockrun-ai.md)\n- [Amazon Bedrock vs Cerebras Inference](https://www.anchorterminal.com/compare/amazon-bedrock-vs-cerebras-inference.md)\n- [Amazon Bedrock vs Cloudflare AI Gateway](https://www.anchorterminal.com/compare/amazon-bedrock-vs-cloudflare-ai-gateway.md)\n- [Amazon Bedrock vs Cloudflare Workers AI](https://www.anchorterminal.com/compare/amazon-bedrock-vs-cloudflare-workers-ai.md)\n- [Amazon Bedrock vs Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/amazon-bedrock-vs-cohere-chat.md)\n- [Amazon Bedrock vs DeepInfra](https://www.anchorterminal.com/compare/amazon-bedrock-vs-deepinfra.md)\n- [Amazon Bedrock vs DeepSeek API](https://www.anchorterminal.com/compare/amazon-bedrock-vs-deepseek-api.md)\n- [Amazon Bedrock vs Eden AI](https://www.anchorterminal.com/compare/amazon-bedrock-vs-eden-ai.md)\n- [Amazon Bedrock vs Glimpse](https://www.anchorterminal.com/compare/amazon-bedrock-vs-elorian-glimpse.md)\n- [Amazon Bedrock vs Fireworks AI Inference](https://www.anchorterminal.com/compare/amazon-bedrock-vs-fireworks-inference.md)\n- [Amazon Bedrock vs Gemini Developer API](https://www.anchorterminal.com/compare/amazon-bedrock-vs-gemini-api.md)\n- [Amazon Bedrock vs GroqCloud](https://www.anchorterminal.com/compare/amazon-bedrock-vs-groq.md)\n- [Amazon Bedrock vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/amazon-bedrock-vs-hugging-face-inference-providers.md)\n- [Amazon Bedrock vs Inkling 2 Small](https://www.anchorterminal.com/compare/amazon-bedrock-vs-inkling-2-small.md)\n- [Amazon Bedrock vs Jais 3](https://www.anchorterminal.com/compare/amazon-bedrock-vs-jais-3.md)\n- [Amazon Bedrock vs Meta Model API](https://www.anchorterminal.com/compare/amazon-bedrock-vs-meta-model-api.md)\n- [Amazon Bedrock vs MiniMax API](https://www.anchorterminal.com/compare/amazon-bedrock-vs-minimax-api.md)\n- [Amazon Bedrock vs Mistral AI API](https://www.anchorterminal.com/compare/amazon-bedrock-vs-mistral-api.md)\n- [Amazon Bedrock vs Muse Spark Open](https://www.anchorterminal.com/compare/amazon-bedrock-vs-muse-spark-open.md)\n- [Amazon Bedrock vs Nemotron 3.5 Super VL](https://www.anchorterminal.com/compare/amazon-bedrock-vs-nemotron-3-5-super-vl.md)\n- [Amazon Bedrock vs Novita AI](https://www.anchorterminal.com/compare/amazon-bedrock-vs-novita-ai.md)\n- [Amazon Bedrock vs OpenAI API](https://www.anchorterminal.com/compare/amazon-bedrock-vs-openai-api.md)\n- [Amazon Bedrock vs OpenRouter](https://www.anchorterminal.com/compare/amazon-bedrock-vs-openrouter.md)\n- [Amazon Bedrock vs Prism Inference](https://www.anchorterminal.com/compare/amazon-bedrock-vs-prism-inference.md)\n- [Amazon Bedrock vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/amazon-bedrock-vs-ramp-router.md)\n- [Amazon Bedrock vs Beam 1.0](https://www.anchorterminal.com/compare/amazon-bedrock-vs-reflection-beam.md)\n- [Amazon Bedrock vs RouterPlus](https://www.anchorterminal.com/compare/amazon-bedrock-vs-routerplus.md)\n- [Amazon Bedrock vs SambaCloud](https://www.anchorterminal.com/compare/amazon-bedrock-vs-sambanova.md)\n- [Amazon Bedrock vs SiliconFlow](https://www.anchorterminal.com/compare/amazon-bedrock-vs-siliconflow.md)\n- [Amazon Bedrock vs Simplismart](https://www.anchorterminal.com/compare/amazon-bedrock-vs-simplismart.md)\n- [Amazon Bedrock vs StepFun API](https://www.anchorterminal.com/compare/amazon-bedrock-vs-stepfun-api.md)\n- [Amazon Bedrock vs SWE-2 Flash](https://www.anchorterminal.com/compare/amazon-bedrock-vs-swe-2-flash.md)\n- [Amazon Bedrock vs Together AI Inference](https://www.anchorterminal.com/compare/amazon-bedrock-vs-together-inference.md)\n- [Amazon Bedrock vs Vercel AI Gateway](https://www.anchorterminal.com/compare/amazon-bedrock-vs-vercel-ai-gateway.md)\n- [Amazon Bedrock vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/amazon-bedrock-vs-vertex-ai.md)\n- [Amazon Bedrock vs xAI API (Grok)](https://www.anchorterminal.com/compare/amazon-bedrock-vs-xai-api.md)\n- [Claude API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.md)\n- [Azure OpenAI in Foundry Models vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub.md)\n- [BlockRun.AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.md)\n- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.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 Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub.md)\n- [Cohere Chat API (Command models) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.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- [Inkling 2 Small vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/inkling-2-small-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- [SWE-2 Flash vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/swe-2-flash-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Together AI Inference](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.md)\n- [Tencent Cloud TokenHub vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vertex-ai.md)\n- [Tencent Cloud TokenHub vs xAI API (Grok)](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api.md)\n- [Antseed vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.md)\n- [Eden AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/eden-ai-vs-tencent-tokenhub.md)\n- [Hugging Face Inference Providers vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.md)\n- [LiteLLM vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/litellm-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- [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", "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-07", "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": "Amazon Bedrock vs Tencent Cloud TokenHub", "url": "" } ], "description": "Amazon Bedrock scores 81.7 (A) to Tencent Cloud TokenHub's 59.5 (C) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Amazon Bedrock A 81.7", "Tencent Cloud TokenHub C 59.5", "scores" ], "h1": "Amazon Bedrock vs Tencent Cloud TokenHub", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/amazon-bedrock-vs-tencent-tokenhub", "published": "2026-10-01", "section": "tools", "title": "Amazon Bedrock vs Tencent Cloud TokenHub for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub" }, "tokens": { "markdown": 8000, "slim": 4330 }, "version": 1 }