{ "data": { "a": { "slug": "hugging-face-inference-providers", "name": "Hugging Face Inference Providers", "vendor": "Hugging Face, Inc.", "vendorUrl": "https://huggingface.co", "kind": "router", "category": "inference", "summary": "Hugging Face's serverless router that sends model calls to partner inference providers such as Groq, Cerebras, Together and Fireworks through one Hugging Face token, with an OpenAI-compatible API at router.huggingface.co/v1 and Python and JavaScript clients.", "url": "https://www.anchorterminal.com/tools/hugging-face-inference-providers", "markdownUrl": "https://www.anchorterminal.com/tools/hugging-face-inference-providers.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hugging-face-inference-providers.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hugging-face-inference-providers.json", "dns": "hugging-face-inference-providers.grade.anchorterminal.com", "repo": "https://github.com/huggingface/huggingface_hub", "license": "Proprietary service under the Hugging Face Terms of Service, which name Inference Providers. The `huggingface_hub` Python client is Apache-2.0 and `@huggingface/inference` is MIT", "transports": [ "http" ], "remoteUrl": "https://router.huggingface.co/v1", "packages": [ { "registry": "pypi", "name": "huggingface_hub" }, { "registry": "npm", "name": "@huggingface/inference" } ], "auth": "api-key", "authNotes": "Hugging Face user access token sent as `Authorization: Bearer $HF_TOKEN`. The docs recommend a fine-grained token with only the `Make calls to Inference Providers` permission. Tokens are made in account settings in a browser, can be rotated and revoked, and a leaked token can be revoked by anyone through `POST /api/credentials/revoke`. A provider's own key can be stored in settings instead, and Hugging Face swaps it in when routing.", "pricing": "usage", "pricingNotes": "Pay as you go at each provider's own per-token rates with no Hugging Face markup, drawn from prepaid credits on the Hugging Face account. Free users get no included credits since 7 October 2026 and must buy credits. PRO users and Team or Enterprise seats get $2.00 a month of compute credits. Requests with a custom provider key are billed by the provider (https://huggingface.co/docs/inference-providers/pricing, checked 2026-11-06).", "priceSummary": "$2 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Inference Providers docs, llms.txt or the router's model list. Calls draw on prepaid Hugging Face credits bought in the account's billing settings (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 483470, "pypiWeekly": 71518708, "asOf": "2026-11-06" }, "docsUrl": "https://huggingface.co/docs/inference-providers/index", "llmsTxt": "https://huggingface.co/docs/inference-providers/llms.txt", "capabilities": [ "inference.router", "inference.open-weights", "inference.llm" ], "tags": [ "hosted", "router", "usage", "prepaid", "openai-compatible", "llms-txt", "python", "javascript", "status-page", "soc2" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 54, "grade": "C", "agentReady": false, "rank": 920, "ranked": true, "rankOf": 1486, "categoryRank": 28, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 58, "maintenance": 80, "payments": 20, "reliability": 25, "schema": 62, "security": 79, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "One Hugging Face token reaches open models on 18 partner providers at the providers' own prices, with a public model list that shows each provider's price, context and tool support. Router rate limits, error responses and its own status component were not found in the reviewed documentation, and free accounts have had no included credits since 7 October 2026.", "bestFor": "Agents and developers who want open-weight models from several hosts on one token and one bill, with a public price and capability list per provider.", "strengths": [ "router.huggingface.co/v1/models lists every routed model with each provider's price, context, tool support, latency and throughput, without a token", "Provider choice by suffix (`:fastest`, `:cheapest`, `:preferred` or a provider name) on an OpenAI-compatible endpoint", "Fine-grained tokens can be limited to the `Make calls to Inference Providers` permission and revoked at once", "No markup on provider rates, and request bodies and responses are not stored when routed", "Official clients in Python (`huggingface_hub` 2.4.0, 29 October 2026) and JavaScript (`@huggingface/inference` 4.13.32)" ], "weaknesses": [ "No rate limits, 429 behaviour or error responses documented for the router", "status.huggingface.co has no component for Inference Providers or the router", "Free users have had no included credits since 7 October 2026, and buying credits needs a person in the account settings", "No OpenAPI document for the router, no batch API, and the Responses API is beta", "Data handling past the router depends on each provider's own policy" ], "agentNotes": [ "Read https://router.huggingface.co/v1/models before choosing a provider; it shows price, context and `supports_tools` per provider", "Pin a provider with `model:\u003cprovider\u003e` when tool calling or structured output matters, since support varies by provider", "Use a fine-grained token with only the Inference Providers permission, and send `X-HF-Bill-To` to bill an organisation", "Back off on 429 without assuming a Retry-After header, since none is documented for the router" ], "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": 54 } ], "editorialScores": { "ergonomics": 58, "maintenance": 80, "payments": 20, "reliability": 25, "schema": 62, "security": 79, "transparency": 58 }, "provenanceScore": 84, "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 huggingface_hub # or: pip install openai, with base_url https://router.huggingface.co/v1", "http": "curl https://router.huggingface.co/v1/chat/completions \\\n -H \"Authorization: Bearer $HF_TOKEN\" -H \"Content-Type: application/json\" \\\n -d '{\"model\":\"openai/gpt-oss-120b:fastest\",\"messages\":[{\"role\":\"user\",\"content\":\"How many Gs in huggingface?\"}]}'" }, "letme": { "capability": "https://letme.dev/inference.router", "tool": "https://letme.dev/hugging-face-inference-providers" }, "sameCompany": [ "hugging-face-inference-endpoints", "smolagents", "carbon-x", "smollm3-3b" ], "area": "models", "unitPrices": [ { "item": "openai/gpt-oss-120b input, cheapest provider listed (DeepInfra)", "unit": "1m-tokens", "usd": 0.037, "note": "Output $0.17. Groq lists $0.15/$0.75 and Cerebras $0.35/$0.75, per the router's model list of 6 November 2026" }, { "item": "PRO monthly compute credits", "unit": "month", "usd": 2, "note": "Also $2.00 per seat for Team and Enterprise organisations" } ], "provenance": { "legalEntity": "Hugging Face, Inc.", "domain": "huggingface.co", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://huggingface.co/terms-of-service", "privacy": "https://huggingface.co/privacy", "statusPage": "https://status.huggingface.co", "changelog": "https://huggingface.co/changelog", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The Terms of Service (effective 15 September 2022) name Hugging Face, Inc. and define Inference Providers as a hosted service for running inference through an API on Hub models.", "huggingface.co/robots.txt and router.huggingface.co/robots.txt allow all. status.huggingface.co serves an empty robots.txt.", "status.huggingface.co is a Better Stack page with components for the Hub, git hosting, Inference Endpoints, Spaces, the CDNs and Jobs, and none for Inference Providers or the router.", "huggingface.co/changelog covers the whole Hub and had no Inference Providers entry on its first page on 6 November 2026. Dated changes to the docs are in the hub-docs repository's history.", "security.txt, privacy policy and subprocessor list as recorded on the Inference Endpoints listing (checked 8 October and 2 November 2026); not re-read for this listing." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/hugging-face-inference-providers.json", "live": { "slug": "hugging-face-inference-providers", "probe": { "target": "https://router.huggingface.co/v1", "method": "get", "lastAt": "2026-11-07T18:20:30.999057368Z", "lastOk": true, "lastStatus": 404, "lastMs": 188, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 108, "p95ms24h": 196, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.huggingface.co", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:55.542550557Z" }, "versions": [ { "registry": "github", "name": "huggingface/huggingface_hub", "version": "v2.4.0", "released": "2026-10-29", "seenAt": "2026-11-06T23:33:27.894225298Z" }, { "registry": "npm", "name": "@huggingface/inference", "version": "4.13.32", "seenAt": "2026-11-06T23:33:27.102558197Z" }, { "registry": "pypi", "name": "huggingface_hub", "version": "2.4.0", "released": "2026-10-29", "seenAt": "2026-11-06T23:33:26.910773744Z" } ], "githubStars": 4034, "npmWeekly": 483470, "pypiWeekly": 71518708, "securityTxt": { "url": "https://huggingface.co/.well-known/security.txt", "state": "valid", "expires": "2030-07-01T08:42:00.000Z", "checkedAt": "2026-11-07T16:00:00.493446773Z" }, "llmsTxt": { "url": "https://huggingface.co/docs/inference-providers/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:44.910268229Z" }, "pages": [ { "url": "https://huggingface.co/docs/inference-providers/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:11:37.221950067Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2cbe821ca9d2" } ], "updatedAt": "2026-11-07T18:20:30.999057368Z" } }, "answer": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Hugging Face Inference Providers's 54 (C), and leads in 4 of 7 scored categories. Hugging Face Inference Providers leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "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": 25, "category": "ergonomics", "leads": "tencent-tokenhub", "name": "Agent ergonomics", "reasons": { "a": "Router reading of the model checklist (tool use, structured output, caching, context, batch, SDKs, errors), as for openrouter. Tool calling through the OpenAI-compatible API with `tool_choice`, support flagged per provider in /v1/models (15 of 20). Structured output documented, support flagged per provider and false on some (10 of 15). No prompt caching guidance found, though the Enterprise usage API counts cached input tokens (3 of 15). Routes to models with up to 1,048,576 tokens of context per the model list, a judgement call since a router has no default model (15). No batch API (0 of 10). Official clients in Python and JavaScript, plus any OpenAI SDK (10). Errors not documented (5 of 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": 58, "b": 83 } }, { "by": 21, "category": "reliability", "leads": "tencent-tokenhub", "name": "Reliability", "reasons": { "a": "Hosted lines. status.huggingface.co is a Better Stack page with 90-day component history for the Hub, Inference Endpoints, Spaces, the CDNs and Jobs, but no component for Inference Providers or the router (10 of 20). With no component, there is no readable incident history for the surface agents call, and the feed's 23 items from 10 June to 7 October 2026 don't name it (5). No rate limits for the router were found; the Hub rate-limits page gives numbers for Hub APIs, resolvers and pages only (0). No 429 or overload guidance for the router was found (0). No SLA found (0). Chat completions on the router is generally available; the Responses API is labelled beta (10). Routing between providers with `:fastest` or `:cheapest` softens a single provider's outage, which this checklist doesn't score.", "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": 25, "b": 46 } }, { "by": 17, "category": "transparency", "leads": "hugging-face-inference-providers", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under Terms of Service that name Inference Providers, with an Apache-2.0 Python client and an MIT JavaScript client (20). The security page and the docs agree on no training, no stored bodies and 30-day logs, but the privacy policy dates from 28 March 2023 and each provider's own data policy governs the rest (18 of 30). No deprecation policy found. Provider support changes and the 7 October removal of free credits are dated only in the docs repository history (5 of 20). The privacy policy lists 11 subprocessors with countries per the Inference Endpoints check, and the docs name every provider a request can reach, though not where each runs (15 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": 71, "b": 54 } }, { "by": 15, "category": "payments", "leads": "tencent-tokenhub", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-token prices for every model and provider published without a login in the router's /v1/models and on model pages (20). No free tier since 7 October 2026, when free users lost their included monthly credits; PRO's $2.00 of credits needs a subscription (0). Sign-up, token creation and credit purchase are browser steps (0).", "b": "No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by `thcli auth login`, but only from that account (0)." }, "scores": { "a": 20, "b": 35 } }, { "by": 11, "category": "schema", "leads": "tencent-tokenhub", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI document for the router (openapi.json paths answer 404). The task reference pages are generated from typed JSON Schema specs in huggingface.js, and the router's /v1/models gives a machine-readable catalogue, so 12 of 25. llms.txt for the Inference Providers docs and a Markdown twin of every page via `.md` (10). Guides say what each task and policy is for, with a quick setup page for coding agents (14 of 20). Parameter tables with types for chat completion, though `response_format` and `tool_choice` show as unknown types (9 of 15). Examples in Python, JavaScript and curl on every task page, but no documented error responses for the router (9 of 15). No changelog of its own; the Hub changelog doesn't cover it and dated changes are only in the hub-docs history (8 of 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": 62, "b": 73 } }, { "by": 8, "category": "security", "leads": "hugging-face-inference-providers", "name": "Security \u0026 auth", "reasons": { "a": "Model reading. Fine-grained user access tokens that can be limited to the `Make calls to Inference Providers` permission, rotated and revoked, plus a public revocation endpoint for leaked tokens, and organisation approval of fine-grained tokens on paid plans (30). Hugging Face says it doesn't store user data for training, but data handling past the router follows each provider's policy, with no per-request filter to exclude providers that train or retain (12 of 20). Request bodies and responses aren't stored when routed and debug logs are kept up to 30 days without user data or tokens, with provider retention outside that statement (10 of 15). Usage by model and provider in account settings, an Enterprise usage API, and Team and Enterprise admins can disable providers and set a spending limit (13 of 15). SOC 2 Type 2 for the Hub, of which the docs say Inference Providers is a feature, and security.txt valid to 2030 per the Inference Endpoints check; no bug bounty found (14 of 20).", "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": 79, "b": 71 } } ], "facts": [ { "a": "Model router", "b": "Model router", "name": "Kind" }, { "a": "Hugging Face, Inc.", "b": "Tencent Cloud", "name": "Vendor" }, { "a": "https://router.huggingface.co/v1", "b": "https://tokenhub.tencentmaas.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API 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 Hugging Face Terms of Service, which name Inference Providers. The `huggingface_hub` Python client is Apache-2.0 and `@huggingface/inference` is MIT", "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-29", "b": "2026-10-24", "name": "Last release" }, { "a": "2022-09-15", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2023-03-28", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "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": "483k npm/wk, 71.5M PyPI/wk", "b": "204 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Hugging Face Inference Providers's 54 (C), and leads in 4 of 7 scored categories. Hugging Face Inference Providers leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Hugging Face Inference Providers or Tencent Cloud TokenHub?" }, { "answer": "Both need an API key.", "question": "Do Hugging Face Inference Providers and Tencent Cloud TokenHub need an API key?" }, { "answer": "Yes. Hugging Face Inference Providers has a hosted endpoint at https://router.huggingface.co/v1 and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.", "question": "Can an agent call Hugging Face Inference Providers and Tencent Cloud TokenHub without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 79 against 71", "Maintenance \u0026 community, 80 against 73", "Transparency \u0026 trust, 71 against 54" ], "also": [ "No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them" ], "goodFor": "Agents and developers who want open-weight models from several hosts on one token and one bill, with a public price and capability list per provider.", "slug": "hugging-face-inference-providers", "watchFor": "No rate limits, 429 behaviour or error responses documented for the router" }, { "aheadOn": [ "Reliability, 46 against 25", "Schema \u0026 documentation, 73 against 62", "Agent ergonomics, 83 against 58", "Payments \u0026 pricing, 35 against 20" ], "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.router", "name": "Model routing" }, "others": [ { "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-tencent-tokenhub.json", "title": "Amazon Bedrock vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-hugging-face-inference-providers.json", "title": "Claude API vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "Azure OpenAI in Foundry Models vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "BlockRun.AI vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "Cerebras Inference vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "Cloudflare AI Gateway vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "Cloudflare Workers AI vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "Cohere Chat API (Command models) vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "DeepInfra vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "DeepSeek API vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "Glimpse vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "Fireworks AI Inference vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "Gemini Developer API vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "GroqCloud vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/groq-vs-hugging-face-inference-providers" }, { "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/hugging-face-inference-providers-vs-inkling-2-small.json", "title": "Hugging Face Inference Providers vs Inkling 2 Small", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-inkling-2-small" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-jais-3.json", "title": "Hugging Face Inference Providers vs Jais 3", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-jais-3" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-meta-model-api.json", "title": "Hugging Face Inference Providers vs Meta Model API", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-meta-model-api" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-minimax-api.json", "title": "Hugging Face Inference Providers vs MiniMax API", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-minimax-api" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-mistral-api.json", "title": "Hugging Face Inference Providers vs Mistral AI API", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-mistral-api" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-muse-spark-open.json", "title": "Hugging Face Inference Providers vs Muse Spark Open", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-muse-spark-open" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-novita-ai.json", "title": "Hugging Face Inference Providers vs Novita AI", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-novita-ai" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-openai-api.json", "title": "Hugging Face Inference Providers vs OpenAI API", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-openai-api" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-reflection-beam.json", "title": "Hugging Face Inference Providers vs Beam 1.0", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-reflection-beam" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-sambanova.json", "title": "Hugging Face Inference Providers vs SambaCloud", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-sambanova" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-siliconflow.json", "title": "Hugging Face Inference Providers vs SiliconFlow", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-siliconflow" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-simplismart.json", "title": "Hugging Face Inference Providers vs Simplismart", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-stepfun-api.json", "title": "Hugging Face Inference Providers vs StepFun API", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-stepfun-api" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-swe-2-flash.json", "title": "Hugging Face Inference Providers vs SWE-2 Flash", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-swe-2-flash" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-together-inference.json", "title": "Hugging Face Inference Providers vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-vertex-ai.json", "title": "Hugging Face Inference Providers vs Vertex AI (Gemini Enterprise Agent Platform)", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-vertex-ai" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-xai-api.json", "title": "Hugging Face Inference Providers vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-xai-api" }, { "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-hugging-face-inference-providers.json", "title": "Antseed vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/antseed-vs-hugging-face-inference-providers" }, { "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-hugging-face-inference-providers.json", "title": "Eden AI vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/eden-ai-vs-hugging-face-inference-providers" }, { "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-litellm.json", "title": "Hugging Face Inference Providers vs LiteLLM", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-litellm" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-openrouter.json", "title": "Hugging Face Inference Providers vs OpenRouter", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-openrouter" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-ramp-router.json", "title": "Hugging Face Inference Providers vs Router.com (Ramp Router)", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-ramp-router" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-routerplus.json", "title": "Hugging Face Inference Providers vs RouterPlus", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-vercel-ai-gateway.json", "title": "Hugging Face Inference Providers vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-vercel-ai-gateway" }, { "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/hugging-face-inference-providers-vs-nemotron-3-5-super-vl.json", "title": "Hugging Face Inference Providers vs Nemotron 3.5 Super VL", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-nemotron-3-5-super-vl" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-prism-inference.json", "title": "Hugging Face Inference Providers vs Prism Inference", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-prism-inference" }, { "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": [ { "by": 21, "edge": "tencent-tokenhub", "hugging-face-inference-providers": 25, "key": "reliability", "name": "Reliability", "tencent-tokenhub": 46, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 11, "edge": "tencent-tokenhub", "hugging-face-inference-providers": 62, "key": "schema", "name": "Schema \u0026 documentation", "tencent-tokenhub": 73, "weight": 13 }, { "by": 25, "edge": "tencent-tokenhub", "hugging-face-inference-providers": 58, "key": "ergonomics", "name": "Agent ergonomics", "tencent-tokenhub": 83, "weight": 13 }, { "by": 8, "edge": "hugging-face-inference-providers", "hugging-face-inference-providers": 79, "key": "security", "name": "Security \u0026 auth", "tencent-tokenhub": 71, "weight": 14 }, { "by": 15, "edge": "tencent-tokenhub", "hugging-face-inference-providers": 20, "key": "payments", "name": "Payments \u0026 pricing", "tencent-tokenhub": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 7, "edge": "hugging-face-inference-providers", "hugging-face-inference-providers": 80, "key": "maintenance", "name": "Maintenance \u0026 community", "tencent-tokenhub": 73, "weight": 7 }, { "by": 17, "edge": "hugging-face-inference-providers", "hugging-face-inference-providers": 71, "key": "transparency", "name": "Transparency \u0026 trust", "tencent-tokenhub": 54, "weight": 7 } ], "summary": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Hugging Face Inference Providers's 54 (C), and leads in 4 of 7 scored categories. Hugging Face Inference Providers leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do model routing.", "tasks": null, "tutorials": [], "verdicts": { "hugging-face-inference-providers": "One Hugging Face token reaches open models on 18 partner providers at the providers' own prices, with a public model list that shows each provider's price, context and tool support. Router rate limits, error responses and its own status component were not found in the reviewed documentation, and free accounts have had no included credits since 7 October 2026.", "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/hugging-face-inference-providers-vs-tencent-tokenhub", "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.min.md" }, "markdown": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Hugging Face Inference Providers's 54 (C), and leads in 4 of 7 scored categories. Hugging Face Inference Providers leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do model routing.\n\n- Hugging Face Inference Providers: grade C, 54/100, rank #920 of 1486. Markdown https://www.anchorterminal.com/tools/hugging-face-inference-providers.md · JSON https://www.anchorterminal.com/api/v1/tools/hugging-face-inference-providers.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### Hugging Face Inference Providers (C)\n\nGood for: Agents and developers who want open-weight models from several hosts on one token and one bill, with a public price and capability list per provider.\n\nAhead on:\n- Security \u0026 auth, 79 against 71\n- Maintenance \u0026 community, 80 against 73\n- Transparency \u0026 trust, 71 against 54\n\nAlso in its favour:\n- No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them\n\nWatch for: No rate limits, 429 behaviour or error responses documented for the router\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- Reliability, 46 against 25\n- Schema \u0026 documentation, 73 against 62\n- Agent ergonomics, 83 against 58\n- Payments \u0026 pricing, 35 against 20\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### Agent ergonomics: Tencent Cloud TokenHub +25\n\n- Hugging Face Inference Providers (58): Router reading of the model checklist (tool use, structured output, caching, context, batch, SDKs, errors), as for openrouter. Tool calling through the OpenAI-compatible API with `tool_choice`, support flagged per provider in /v1/models (15 of 20). Structured output documented, support flagged per provider and false on some (10 of 15). No prompt caching guidance found, though the Enterprise usage API counts cached input tokens (3 of 15). Routes to models with up to 1,048,576 tokens of context per the model list, a judgement call since a router has no default model (15). No batch API (0 of 10). Official clients in Python and JavaScript, plus any OpenAI SDK (10). Errors not documented (5 of 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### Reliability: Tencent Cloud TokenHub +21\n\n- Hugging Face Inference Providers (25): Hosted lines. status.huggingface.co is a Better Stack page with 90-day component history for the Hub, Inference Endpoints, Spaces, the CDNs and Jobs, but no component for Inference Providers or the router (10 of 20). With no component, there is no readable incident history for the surface agents call, and the feed's 23 items from 10 June to 7 October 2026 don't name it (5). No rate limits for the router were found; the Hub rate-limits page gives numbers for Hub APIs, resolvers and pages only (0). No 429 or overload guidance for the router was found (0). No SLA found (0). Chat completions on the router is generally available; the Responses API is labelled beta (10). Routing between providers with `:fastest` or `:cheapest` softens a single provider's outage, which this checklist doesn't score.\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: Hugging Face Inference Providers +17\n\n- Hugging Face Inference Providers (71): Closed service under Terms of Service that name Inference Providers, with an Apache-2.0 Python client and an MIT JavaScript client (20). The security page and the docs agree on no training, no stored bodies and 30-day logs, but the privacy policy dates from 28 March 2023 and each provider's own data policy governs the rest (18 of 30). No deprecation policy found. Provider support changes and the 7 October removal of free credits are dated only in the docs repository history (5 of 20). The privacy policy lists 11 subprocessors with countries per the Inference Endpoints check, and the docs name every provider a request can reach, though not where each runs (15 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### Payments \u0026 pricing: Tencent Cloud TokenHub +15\n\n- Hugging Face Inference Providers (20): No x402, MPP or L402 (0). Per-token prices for every model and provider published without a login in the router's /v1/models and on model pages (20). No free tier since 7 October 2026, when free users lost their included monthly credits; PRO's $2.00 of credits needs a subscription (0). Sign-up, token creation and credit purchase are browser steps (0).\n- Tencent Cloud TokenHub (35): No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by `thcli auth login`, but only from that account (0).\n\n### Schema \u0026 documentation: Tencent Cloud TokenHub +11\n\n- Hugging Face Inference Providers (62): No OpenAPI document for the router (openapi.json paths answer 404). The task reference pages are generated from typed JSON Schema specs in huggingface.js, and the router's /v1/models gives a machine-readable catalogue, so 12 of 25. llms.txt for the Inference Providers docs and a Markdown twin of every page via `.md` (10). Guides say what each task and policy is for, with a quick setup page for coding agents (14 of 20). Parameter tables with types for chat completion, though `response_format` and `tool_choice` show as unknown types (9 of 15). Examples in Python, JavaScript and curl on every task page, but no documented error responses for the router (9 of 15). No changelog of its own; the Hub changelog doesn't cover it and dated changes are only in the hub-docs history (8 of 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### Security \u0026 auth: Hugging Face Inference Providers +8\n\n- Hugging Face Inference Providers (79): Model reading. Fine-grained user access tokens that can be limited to the `Make calls to Inference Providers` permission, rotated and revoked, plus a public revocation endpoint for leaked tokens, and organisation approval of fine-grained tokens on paid plans (30). Hugging Face says it doesn't store user data for training, but data handling past the router follows each provider's policy, with no per-request filter to exclude providers that train or retain (12 of 20). Request bodies and responses aren't stored when routed and debug logs are kept up to 30 days without user data or tokens, with provider retention outside that statement (10 of 15). Usage by model and provider in account settings, an Enterprise usage API, and Team and Enterprise admins can disable providers and set a spending limit (13 of 15). SOC 2 Type 2 for the Hub, of which the docs say Inference Providers is a feature, and security.txt valid to 2030 per the Inference Endpoints check; no bug bounty found (14 of 20).\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## Score by category\n\n| Category | Weight | Hugging Face Inference Providers | Tencent Cloud TokenHub | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 25 | 46 | Tencent Cloud TokenHub +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 62 | 73 | Tencent Cloud TokenHub +11 |\n| Agent ergonomics | 13% (16.2 this run) | 58 | 83 | Tencent Cloud TokenHub +25 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 71 | Hugging Face Inference Providers +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 35 | Tencent Cloud TokenHub +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 73 | Hugging Face Inference Providers +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 54 | Hugging Face Inference Providers +17 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **54 · C** | **59.5 · C** | |\n\n## Facts side by side\n\n| Fact | Hugging Face Inference Providers | Tencent Cloud TokenHub |\n| --- | --- | --- |\n| Kind | Model router | Model router |\n| Vendor | Hugging Face, Inc. | Tencent Cloud |\n| Hosted endpoint | `https://router.huggingface.co/v1` | `https://tokenhub.tencentmaas.com/v1` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under the Hugging Face Terms of Service, which name Inference Providers. The `huggingface_hub` Python client is Apache-2.0 and `@huggingface/inference` is MIT | Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-29 | 2026-10-24 |\n| Terms last updated | 2022-09-15 | couldn't be read |\n| Privacy policy last updated | 2023-03-28 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | 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 | 483k npm/wk, 71.5M PyPI/wk | 204 npm/wk |\n\n## Verdicts\n\n**Hugging Face Inference Providers.** One Hugging Face token reaches open models on 18 partner providers at the providers' own prices, with a public model list that shows each provider's price, context and tool support. Router rate limits, error responses and its own status component were not found in the reviewed documentation, and free accounts have had no included credits since 7 October 2026.\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### Hugging Face Inference Providers\n\n1. Read https://router.huggingface.co/v1/models before choosing a provider; it shows price, context and `supports_tools` per provider\n2. Pin a provider with `model:\u003cprovider\u003e` when tool calling or structured output matters, since support varies by provider\n3. Use a fine-grained token with only the Inference Providers permission, and send `X-HF-Bill-To` to bill an organisation\n4. Back off on 429 without assuming a Retry-After header, since none is documented for the router\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, Hugging Face Inference Providers or Tencent Cloud TokenHub?\n\nTencent Cloud TokenHub scores 59.5 (C) on agent readiness against Hugging Face Inference Providers's 54 (C), and leads in 4 of 7 scored categories. Hugging Face Inference Providers leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Hugging Face Inference Providers and Tencent Cloud TokenHub need an API key?\n\nBoth need an API key.\n\n### Can an agent call Hugging Face Inference Providers and Tencent Cloud TokenHub without installing anything?\n\nYes. Hugging Face Inference Providers has a hosted endpoint at https://router.huggingface.co/v1 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/hugging-face-inference-providers-vs-tencent-tokenhub.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"hugging-face-inference-providers\", \"b\": \"tencent-tokenhub\"}`. From a terminal: `anchor compare hugging-face-inference-providers tencent-tokenhub`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hugging-face-inference-providers.json and https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n\n## Other comparisons with Hugging Face Inference Providers or Tencent Cloud TokenHub\n\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 Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub.md)\n- [Claude API vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/anthropic-api-vs-hugging-face-inference-providers.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 Hugging Face Inference Providers](https://www.anchorterminal.com/compare/azure-openai-vs-hugging-face-inference-providers.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 Hugging Face Inference Providers](https://www.anchorterminal.com/compare/blockrun-ai-vs-hugging-face-inference-providers.md)\n- [BlockRun.AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.md)\n- [Cerebras Inference vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/cerebras-inference-vs-hugging-face-inference-providers.md)\n- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.md)\n- [Cloudflare AI Gateway vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-hugging-face-inference-providers.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 Hugging Face Inference Providers](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-hugging-face-inference-providers.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 Hugging Face Inference Providers](https://www.anchorterminal.com/compare/cohere-chat-vs-hugging-face-inference-providers.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 Hugging Face Inference Providers](https://www.anchorterminal.com/compare/deepinfra-vs-hugging-face-inference-providers.md)\n- [DeepInfra vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.md)\n- [DeepSeek API vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/deepseek-api-vs-hugging-face-inference-providers.md)\n- [DeepSeek API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.md)\n- [Glimpse vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/elorian-glimpse-vs-hugging-face-inference-providers.md)\n- [Glimpse vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.md)\n- [Fireworks AI Inference vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/fireworks-inference-vs-hugging-face-inference-providers.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 Hugging Face Inference Providers](https://www.anchorterminal.com/compare/gemini-api-vs-hugging-face-inference-providers.md)\n- [Gemini Developer API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.md)\n- [GroqCloud vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/groq-vs-hugging-face-inference-providers.md)\n- [GroqCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.md)\n- [Hugging Face Inference Providers vs Inkling 2 Small](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-inkling-2-small.md)\n- [Hugging Face Inference Providers vs Jais 3](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-jais-3.md)\n- [Hugging Face Inference Providers vs Meta Model API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-meta-model-api.md)\n- [Hugging Face Inference Providers vs MiniMax API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-minimax-api.md)\n- [Hugging Face Inference Providers vs Mistral AI API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-mistral-api.md)\n- [Hugging Face Inference Providers vs Muse Spark Open](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-muse-spark-open.md)\n- [Hugging Face Inference Providers vs Novita AI](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-novita-ai.md)\n- [Hugging Face Inference Providers vs OpenAI API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-openai-api.md)\n- [Hugging Face Inference Providers vs Beam 1.0](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-reflection-beam.md)\n- [Hugging Face Inference Providers vs SambaCloud](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-sambanova.md)\n- [Hugging Face Inference Providers vs SiliconFlow](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-siliconflow.md)\n- [Hugging Face Inference Providers vs Simplismart](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-simplismart.md)\n- [Hugging Face Inference Providers vs StepFun API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-stepfun-api.md)\n- [Hugging Face Inference Providers vs SWE-2 Flash](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-swe-2-flash.md)\n- [Hugging Face Inference Providers vs Together AI Inference](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-together-inference.md)\n- [Hugging Face Inference Providers vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-vertex-ai.md)\n- [Hugging Face Inference Providers vs xAI API (Grok)](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-xai-api.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 Hugging Face Inference Providers](https://www.anchorterminal.com/compare/antseed-vs-hugging-face-inference-providers.md)\n- [Antseed vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.md)\n- [Eden AI vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/eden-ai-vs-hugging-face-inference-providers.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 LiteLLM](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-litellm.md)\n- [Hugging Face Inference Providers vs OpenRouter](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-openrouter.md)\n- [Hugging Face Inference Providers vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-ramp-router.md)\n- [Hugging Face Inference Providers vs RouterPlus](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-routerplus.md)\n- [Hugging Face Inference Providers vs Vercel AI Gateway](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-vercel-ai-gateway.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- [Hugging Face Inference Providers vs Nemotron 3.5 Super VL](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-nemotron-3-5-super-vl.md)\n- [Hugging Face Inference Providers vs Prism Inference](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-prism-inference.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": "Hugging Face Inference Providers vs Tencent Cloud TokenHub", "url": "" } ], "description": "Tencent Cloud TokenHub scores 59.5 (C) to Hugging Face Inference Providers's 54 (C) for model routing. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Hugging Face Inference Providers C 54", "Tencent Cloud TokenHub C 59.5", "scores" ], "h1": "Hugging Face Inference Providers vs Tencent Cloud TokenHub", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/hugging-face-inference-providers-vs-tencent-tokenhub", "published": "2026-10-01", "section": "tools", "title": "Hugging Face Inference Providers vs Tencent Cloud TokenHub (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub" }, "tokens": { "markdown": 7800, "slim": 3730 }, "version": 1 }