{ "data": { "a": { "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": 703, "ranked": true, "rankOf": 1510, "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-07T19:22:39.030430078Z", "lastOk": true, "lastStatus": 404, "lastMs": 783, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 836, "p95ms24h": 1161, "samples24h": 238, "samples30d": 1385, "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": 197, "ok": 197 } ] }, "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-07T19:22:39.030430078Z" } }, "answer": "xAI API (Grok) scores 71.7 (BB) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing.", "b": { "slug": "xai-api", "name": "xAI API (Grok)", "vendor": "SpaceXSI (xAI)", "vendorUrl": "https://x.ai", "kind": "model", "category": "inference", "summary": "xAI's API for its Grok models (the docs now name the company SpaceXSI), with text, image, video and voice endpoints, server-side search and remote MCP tools, through an OpenAI-compatible REST API or gRPC.", "url": "https://www.anchorterminal.com/tools/xai-api", "markdownUrl": "https://www.anchorterminal.com/tools/xai-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/xai-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/xai-api.json", "dns": "xai-api.grade.anchorterminal.com", "repo": "https://github.com/xai-org/xai-sdk-python", "license": "Proprietary service under xAI's enterprise terms of service. The Python SDK is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://api.x.ai/v1", "packages": [ { "registry": "pypi", "name": "xai-sdk" } ], "auth": "api-key", "authNotes": "`Authorization: Bearer` with a team API key from console.x.ai. Keys can be limited to endpoints and models by ACL, capped by QPM and TPM, given an expiry, and rotated or disabled through the Management API. mTLS is documented as an option, and GitHub secret scanning disables leaked keys.", "pricing": "usage", "pricingNotes": "Prepaid credits, then the default payment method at month end. Grok 4.7 costs $2 input, $0.50 cached input and $6 output per 1M tokens below 200K prompt tokens, and $4/$1/$12 above, applied to the whole request. Batch is 20% off on grok-4.7, 4.6, 4.5, 4.3 and the grok-4.20 models. Priority processing 2x, the US regional endpoint 1.1x. Web search, code execution and attachment search $5 per 1,000 calls, collections search $2.50, X search $5 per 1,000 posts. $0.05 fee for a request blocked before generation for a usage-policy violation (https://docs.x.ai/developers/pricing, checked 2026-11-06).", "priceSummary": "from $1.25 / 1M in", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms.txt or the OpenAPI spec. Access needs a console account loaded with prepaid credits (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 597, "npmWeekly": null, "pypiWeekly": 912149, "asOf": "2026-11-06" }, "docsUrl": "https://docs.x.ai", "rateLimitsUrl": "https://docs.x.ai/developers/rate-limits", "llmsTxt": "https://docs.x.ai/llms.txt", "openapi": "https://docs.x.ai/openapi.json", "capabilities": [ "inference.llm" ], "tags": [ "official", "hosted", "model", "prepaid", "openapi", "llms-txt", "openai-compatible", "closed-source", "python", "batch", "status-page", "bug-bounty", "soc2" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 71.7, "grade": "BB", "agentReady": true, "rank": 152, "ranked": true, "rankOf": 1510, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 90, "maintenance": 77, "payments": 20, "reliability": 55, "schema": 88, "security": 97, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Grok 4.7 at $2/$6 per million tokens, now 20% off in batch, with a public OpenAPI spec, llms.txt, API keys limited by endpoint and model, and self-serve zero data retention. The API endpoints had a 3 hour 40 minute models outage on 3 September 2026, no SLA was found, and there's no free tier or first-party SDK beyond Python.", "bestFor": "Agents that want a capable model at a low per-token price with built-in web and X search, remote MCP and voice, and teams that need self-serve ZDR or US-only processing.", "strengths": [ "Grok 4.7 at $2/$6 per million tokens below 200K prompt tokens, with a 500K context and 20% off through the Batch API", "API keys restricted by endpoint and model ACLs, with QPM and TPM caps, expiry and a rotate endpoint", "Self-serve team-wide zero data retention, confirmed on every response by an `x-zero-data-retention` header", "OpenAPI 3.1 spec, llms.txt and a Markdown twin of every docs page", "security.txt valid to 2027-06-29 and a HackerOne bug bounty" ], "weaknesses": [ "API models outage of about 3 hours 40 minutes on 3 September 2026, and high error rates on grok-4.6 and grok-4.5 on 17 August", "No SLA, no free tier for the text API, and no Retry-After header documented for 429s", "No stated minimum notice for retirements, and retired slugs are served by a different model at its price", "Remote MCP doesn't support `require_approval`, so server-side tool calls run without an approval step", "The terms, privacy policy and DPA at x.ai/legal answered a Cloudflare block on 6 October and 6 November 2026, so they weren't read" ], "agentNotes": [ "Build on the Responses API at https://api.x.ai/v1. Chat Completions is labelled deprecated and the Anthropic-compatible endpoint fully deprecated", "Pin a dated model slug. A retired slug keeps answering from a replacement model, billed at the replacement's price", "Back off exponentially on 429. The per-second cap is the per-minute budget divided by 48, with a minimum of 2", "Set `allowed_tools` on remote MCP servers. There's no approval step, and every exposed tool enters the context", "Use https://us.api.x.ai/v1 when processing must stay in the US. It costs 1.1x and serves only grok-4.7 and grok-4.6" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.7 } ], "editorialScores": { "ergonomics": 90, "maintenance": 77, "payments": 20, "reliability": 55, "schema": 88, "security": 97, "transparency": 52 }, "provenanceScore": 73, "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 xai-sdk # or: pip install openai, with base_url https://api.x.ai/v1", "http": "curl https://api.x.ai/v1/responses \\\n -H \"Authorization: Bearer $XAI_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"model\":\"grok-4.7\",\"input\":\"What is the meaning of life?\"}'" }, "letme": { "capability": "https://letme.dev/inference.llm", "tool": "https://letme.dev/xai-api" }, "area": "models", "unitPrices": [ { "item": "Web search tool", "unit": "1k-requests", "usd": 5 }, { "item": "Code execution tool", "unit": "1k-requests", "usd": 5 }, { "item": "Collections search tool", "unit": "1k-requests", "usd": 2.5 } ], "provenance": { "legalEntity": "", "domain": "x.ai", "domainRegistered": "2017-12-16", "domainNote": "x.ai was registered in 2017, before the company, and transferred on 2026-06-02 per RDAP. Every x.ai page except robots.txt and security.txt answered a Cloudflare block page (403) on 2026-11-06, as the legal pages did on 2026-10-06, so the contracting entity wasn't confirmed. The docs now use the name SpaceXSI and the status page SpaceXAI.", "endpointOnVendorDomain": true, "terms": "https://x.ai/legal/terms-of-service-enterprise", "privacy": "https://x.ai/legal/privacy-policy", "statusPage": "https://status.x.ai", "changelog": "https://docs.x.ai/developers/release-notes", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "x.ai/robots.txt allows all but /tools/, with Content-Signal ai-train=yes, search=yes, ai-input=yes. docs.x.ai allows all with ai-input=yes. The x.ai pages that robots.txt allows answered a Cloudflare 'Attention Required' page, which we did not try to get past.", "security.txt at x.ai/.well-known/security.txt is valid to 2027-06-29, with vulnerabilities@x.ai and abuse@x.ai." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/xai-api.json", "live": { "slug": "xai-api", "probe": { "target": "https://api.x.ai/v1", "method": "get", "lastAt": "2026-11-07T19:22:45.426736159Z", "lastOk": true, "lastStatus": 404, "lastMs": 193, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 178, "p95ms24h": 276, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.x.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:49:01.143662157Z" }, "versions": [ { "registry": "github", "name": "xai-org/xai-sdk-python", "version": "v1.21.0", "released": "2026-10-23", "seenAt": "2026-11-07T00:18:15.193708838Z" }, { "registry": "pypi", "name": "xai-sdk", "version": "1.21.0", "released": "2026-10-23", "seenAt": "2026-11-07T00:18:15.09038487Z" } ], "githubStars": 598, "pypiWeekly": 912149, "securityTxt": { "url": "https://x.ai/.well-known/security.txt", "state": "valid", "expires": "2027-06-29T00:00:00.000Z", "checkedAt": "2026-11-07T16:01:43.978620532Z" }, "llmsTxt": { "url": "https://docs.x.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:24.762831371Z" }, "pages": [ { "url": "https://docs.x.ai/developers/migration/imagine-image-quality-nov-2", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:08:46.034096807Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1238569c8142" }, { "url": "https://docs.x.ai/developers/migration/may-15-retirement", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:08:48.207542223Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "813d0e188a0e" }, { "url": "https://docs.x.ai/developers/release-notes", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:08:52.143682141Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7b37cfaf2576" }, { "url": "https://docs.x.ai/developers/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:08:50.158330981Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a563de9617fe" }, { "url": "https://x.ai/legal/privacy-policy", "kind": "privacy", "status": 403, "checkedAt": "2026-11-07T14:38:04.991061235Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://x.ai/legal/terms-of-service-enterprise", "kind": "terms", "status": 403, "checkedAt": "2026-11-07T14:38:09.200382604Z", "changedAt": "0001-01-01T00:00:00Z" } ], "updatedAt": "2026-11-07T19:22:45.426736159Z" } }, "edges": [ { "by": 26, "category": "security", "leads": "xai-api", "name": "Security \u0026 auth", "reasons": { "a": "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).", "b": "Model reading. Team API keys with ACLs per endpoint and per model, QPM and TPM caps, expiry, and create, rotate, disable and delete through the Management API, plus documented mTLS. GitHub secret scanning disables leaked keys and emails the owner (30). The security FAQ says SpaceXSI never trains on API inputs or outputs without explicit permission (20). Requests and responses are kept 30 days for abuse auditing, then deleted, and team admins can switch on zero data retention themselves, confirmed by an `x-zero-data-retention` header on every response (15). Console audit log and a Management API audit-events endpoint, plus optional per-key request logging (15). security.txt valid to 2027-06-29 with a HackerOne bug bounty and a separate safety contact for prompt-injection issues. SOC 2 Type 2 is claimed in the security FAQ with the reports behind an NDA in the trust centre, so 17 of 20. Remote MCP doesn't support `require_approval`, which the model checklist doesn't score but reviewers should see. New in October, a `guidelines` array lets the caller make the model decline nsfw, violence or profanity content, which the checklist doesn't score." }, "scores": { "a": 71, "b": 97 } }, { "by": 15, "category": "schema", "leads": "xai-api", "name": "Schema \u0026 documentation", "reasons": { "a": "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).", "b": "OpenAPI 3.1 document at docs.x.ai/openapi.json, 39 paths and 205 schemas on 6 November, covering Responses, Chat Completions, files, images, videos and models. The batch endpoints documented in the REST reference still aren't in it (20 of 25, applied as for gemini-api's missing Interactions API). llms.txt and a Markdown twin of every page, plus a docs MCP server (10). The models page says which model to use for code, chat, images, video and voice, and reference pages list each parameter. Reference not read in full (18 of 20). Structured outputs are guaranteed to match the schema for supported keywords, and tool arguments always conform with `strict` implicitly true (15). Examples in Python, JavaScript and curl on every guide. The debugging page lists status codes with fixes, but the cause cells for 400, 403, 404 and 415 are still empty (13 of 15). Release notes are grouped by month without day dates, and model slugs come as aliases and dated versions (12 of 15)." }, "scores": { "a": 73, "b": 88 } }, { "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 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).", "b": "No x402, MPP or L402 (0). Per-token and per-call prices published without a login on docs.x.ai/developers/pricing (20). No free tier found for the text API, and the quickstart says to load the account with credits (0). Sign-up is in the browser at console.x.ai. The Management API can create keys and top up prepaid credit, but only with a management key made by a person in the console, so no line credit (0)." }, "scores": { "a": 35, "b": 20 } }, { "by": 9, "category": "reliability", "leads": "xai-api", "name": "Reliability", "reasons": { "a": "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).", "b": "Status page at status.x.ai with components for the global and US API endpoints, voice, the consumer apps and, since the Cursor merger, Cursor's services, with an RSS feed (20). The feed, read on 6 November, now holds 267 incidents back to 11 August, so the whole 90-day window is readable. On the API components there were high error rates on grok-4.6 and grok-4.5 from 21:57 to 23:28 UTC on 17 August (about 90 minutes) and a models outage on the global and US endpoints from 13:30 to 17:09 UTC on 3 September (about 3 hours 40 minutes), so several majors. A 26-minute datacenter outage across the API on 22 September, voice disruptions of 12 and 28 minutes on 10 September and 6 October, a 63-minute voice and Imagine degradation on 30 October and a 37-second model degradation on 24 October add to the record (0). Rate limits published per model and tier, grok-4.7 at Tier 0 is 150 requests a second and 50M TPM, with the per-second cap derived as RPM divided by 48 (15). The rate-limits page shows exponential backoff on 429, but no Retry-After header or overload guidance was found (10 of 15). No SLA found in the docs or llms.txt (0). The Responses API has been GA since September 2025 and grok-4.7 carries no preview label (10)." }, "scores": { "a": 46, "b": 55 } }, { "by": 9, "category": "transparency", "leads": "xai-api", "name": "Transparency \u0026 trust", "reasons": { "a": "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).", "b": "Closed service under xAI's enterprise terms, with the Python SDK under Apache-2.0 (15). The docs agree with each other on no training, 30-day abuse retention, 30-day storage of stateful responses and the ZDR route, but the privacy policy, enterprise terms and DPA at x.ai/legal answered a Cloudflare block page on 6 October and again on 6 November, so they couldn't be compared (15 of 30). Dated migration guides and redirect tables for each retirement, but no written deprecation policy, and Chat Completions, Anthropic compatibility and grok-voice-2.0 are labelled deprecated with no date (12 of 20). The US regional endpoint states what stays in the US, the global endpoint guarantees no region, and no subprocessor list was readable (10 of 20)." }, "scores": { "a": 54, "b": 63 } }, { "by": 7, "category": "ergonomics", "leads": "xai-api", "name": "Agent ergonomics", "reasons": { "a": "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).", "b": "Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling with parallel calls on by default and `tool_choice` of auto, required, none or a named function (20). Guaranteed structured outputs (15). Automatic prompt caching, cached input at 0.25x on grok-4.7 ($0.50 per million) and 0.16x on grok-4.3 (15). 500,000-token context on grok-4.7 and 1,000,000 on grok-4.3, 13 of 15 for the default model's 500K. The Batch API is now 20% off on grok-4.7, 4.6 and 4.5 as well as the older models, with batch requests outside the rate limits (10 of 10, up from 5 on 6 October). One first-party SDK, `xai-sdk` for Python, with the OpenAI SDKs and Vercel's AI SDK documented as alternatives (5 of 10). Status codes documented with fixes, no Retry-After header found (12 of 15)." }, "scores": { "a": 83, "b": 90 } } ], "facts": [ { "a": "Model router", "b": "Model API", "name": "Kind" }, { "a": "Tencent Cloud", "b": "SpaceXSI (xAI)", "name": "Vendor" }, { "a": "https://tokenhub.tencentmaas.com/v1", "b": "https://api.x.ai/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 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", "b": "Proprietary service under xAI's enterprise terms of service. The Python SDK 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-24", "b": "2026-11-02", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-10-27", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-10-27", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "yes", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "204 npm/wk", "b": "597 stars, 912k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "xAI API (Grok) scores 71.7 (BB) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Tencent Cloud TokenHub or xAI API (Grok)?" }, { "answer": "Both need an API key.", "question": "Do Tencent Cloud TokenHub and xAI API (Grok) need an API key?" }, { "answer": "Yes. Tencent Cloud TokenHub has a hosted endpoint at https://tokenhub.tencentmaas.com/v1 and xAI API (Grok) at https://api.x.ai/v1.", "question": "Can an agent call Tencent Cloud TokenHub and xAI API (Grok) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "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" }, { "aheadOn": [ "Reliability, 55 against 46", "Schema \u0026 documentation, 88 against 73", "Agent ergonomics, 90 against 83", "Security \u0026 auth, 97 against 71", "Transparency \u0026 trust, 63 against 54" ], "also": [ "Agent-ready, a grade of BB or better", "No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them" ], "goodFor": "Agents that want a capable model at a low per-token price with built-in web and X search, remote MCP and voice, and teams that need self-serve ZDR or US-only processing.", "slug": "xai-api", "watchFor": "API models outage of about 3 hours 40 minutes on 3 September 2026, and high error rates on grok-4.6 and grok-4.5 on 17 August" } ], "history": null, "job": { "capability": "inference.llm", "name": "LLM inference" }, "others": [ { "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/amazon-bedrock-vs-xai-api.json", "title": "Amazon Bedrock vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.json", "title": "Claude API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-xai-api.json", "title": "Claude API vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-xai-api.json", "title": "Antseed vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/antseed-vs-xai-api" }, { "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/azure-openai-vs-xai-api.json", "title": "Azure OpenAI in Foundry Models vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-xai-api" }, { "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/blockrun-ai-vs-xai-api.json", "title": "BlockRun.AI vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-xai-api" }, { "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/cerebras-inference-vs-xai-api.json", "title": "Cerebras Inference vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-xai-api" }, { "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-ai-gateway-vs-xai-api.json", "title": "Cloudflare AI Gateway vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-xai-api" }, { "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/cloudflare-workers-ai-vs-xai-api.json", "title": "Cloudflare Workers AI vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-xai-api" }, { "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/cohere-chat-vs-xai-api.json", "title": "Cohere Chat API (Command models) vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-xai-api" }, { "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/deepinfra-vs-xai-api.json", "title": "DeepInfra vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-xai-api" }, { "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/deepseek-api-vs-xai-api.json", "title": "DeepSeek API vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/eden-ai-vs-xai-api.json", "title": "Eden AI vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/eden-ai-vs-xai-api" }, { "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/elorian-glimpse-vs-xai-api.json", "title": "Glimpse vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-xai-api" }, { "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/fireworks-inference-vs-xai-api.json", "title": "Fireworks AI Inference vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-xai-api" }, { "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/gemini-api-vs-xai-api.json", "title": "Gemini Developer API vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-xai-api" }, { "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/groq-vs-xai-api.json", "title": "GroqCloud vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/groq-vs-xai-api" }, { "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/inkling-2-small-vs-xai-api.json", "title": "Inkling 2 Small vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/inkling-2-small-vs-xai-api" }, { "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/jais-3-vs-xai-api.json", "title": "Jais 3 vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/jais-3-vs-xai-api" }, { "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/meta-model-api-vs-xai-api.json", "title": "Meta Model API vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-xai-api" }, { "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/minimax-api-vs-xai-api.json", "title": "MiniMax API vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-xai-api" }, { "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/mistral-api-vs-xai-api.json", "title": "Mistral AI API vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-xai-api" }, { "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/muse-spark-open-vs-xai-api.json", "title": "Muse Spark Open vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-xai-api.json", "title": "Nemotron 3.5 Super VL vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-xai-api" }, { "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/novita-ai-vs-xai-api.json", "title": "Novita AI vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-xai-api" }, { "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/openai-api-vs-xai-api.json", "title": "OpenAI API vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/openai-api-vs-xai-api" }, { "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/openrouter-vs-xai-api.json", "title": "OpenRouter vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/openrouter-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/prism-inference-vs-xai-api.json", "title": "Prism Inference vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/ramp-router-vs-xai-api.json", "title": "Router.com (Ramp Router) vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-xai-api" }, { "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/reflection-beam-vs-xai-api.json", "title": "Beam 1.0 vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/reflection-beam-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-xai-api.json", "title": "RouterPlus vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/routerplus-vs-xai-api" }, { "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/sambanova-vs-xai-api.json", "title": "SambaCloud vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/sambanova-vs-xai-api" }, { "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/siliconflow-vs-xai-api.json", "title": "SiliconFlow vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/siliconflow-vs-xai-api" }, { "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/simplismart-vs-xai-api.json", "title": "Simplismart vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/simplismart-vs-xai-api" }, { "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/stepfun-api-vs-xai-api.json", "title": "StepFun API vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/stepfun-api-vs-xai-api" }, { "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/swe-2-flash-vs-xai-api.json", "title": "SWE-2 Flash vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/swe-2-flash-vs-xai-api" }, { "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/together-inference-vs-xai-api.json", "title": "Together AI Inference vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/together-inference-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/vercel-ai-gateway-vs-xai-api.json", "title": "Vercel AI Gateway vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/vercel-ai-gateway-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/vertex-ai-vs-xai-api.json", "title": "Vertex AI (Gemini Enterprise Agent Platform) vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/vertex-ai-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.json", "title": "Antseed vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/eden-ai-vs-tencent-tokenhub.json", "title": "Eden AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/eden-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.json", "title": "Hugging Face Inference Providers vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/litellm-vs-tencent-tokenhub.json", "title": "LiteLLM vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/litellm-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.json", "title": "Router.com (Ramp Router) vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.json", "title": "RouterPlus vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.json", "title": "Tencent Cloud TokenHub vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway" }, { "json": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub.json", "title": "Nemotron 3.5 Super VL vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.json", "title": "Prism Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub" } ], "panel": null, "scores": [ { "by": 9, "edge": "xai-api", "key": "reliability", "name": "Reliability", "tencent-tokenhub": 46, "weight": 16, "xai-api": 55 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 15, "edge": "xai-api", "key": "schema", "name": "Schema \u0026 documentation", "tencent-tokenhub": 73, "weight": 13, "xai-api": 88 }, { "by": 7, "edge": "xai-api", "key": "ergonomics", "name": "Agent ergonomics", "tencent-tokenhub": 83, "weight": 13, "xai-api": 90 }, { "by": 26, "edge": "xai-api", "key": "security", "name": "Security \u0026 auth", "tencent-tokenhub": 71, "weight": 14, "xai-api": 97 }, { "by": 15, "edge": "tencent-tokenhub", "key": "payments", "name": "Payments \u0026 pricing", "tencent-tokenhub": 35, "weight": 10, "xai-api": 20 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "edge": "xai-api", "key": "maintenance", "name": "Maintenance \u0026 community", "tencent-tokenhub": 73, "weight": 7, "xai-api": 77 }, { "by": 9, "edge": "xai-api", "key": "transparency", "name": "Transparency \u0026 trust", "tencent-tokenhub": 54, "weight": 7, "xai-api": 63 } ], "summary": "xAI API (Grok) scores 71.7 (BB) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing. Both do llm inference.", "tasks": null, "tutorials": [], "verdicts": { "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.", "xai-api": "Grok 4.7 at $2/$6 per million tokens, now 20% off in batch, with a public OpenAPI spec, llms.txt, API keys limited by endpoint and model, and self-serve zero data retention. The API endpoints had a 3 hour 40 minute models outage on 3 September 2026, no SLA was found, and there's no free tier or first-party SDK beyond Python." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api", "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api.min.md" }, "markdown": "xAI API (Grok) scores 71.7 (BB) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing. Both do llm inference.\n\n- Tencent Cloud TokenHub: grade C, 59.5/100, rank #703 of 1510. Markdown https://www.anchorterminal.com/tools/tencent-tokenhub.md · JSON https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n- xAI API (Grok): grade BB, 71.7/100, rank #152 of 1510. Markdown https://www.anchorterminal.com/tools/xai-api.md · JSON https://www.anchorterminal.com/api/v1/tools/xai-api.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### Tencent Cloud TokenHub (C)\n\nGood for: Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing.\n\nAhead on:\n- Payments \u0026 pricing, 35 against 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### xAI API (Grok) (BB)\n\nGood for: Agents that want a capable model at a low per-token price with built-in web and X search, remote MCP and voice, and teams that need self-serve ZDR or US-only processing.\n\nAhead on:\n- Reliability, 55 against 46\n- Schema \u0026 documentation, 88 against 73\n- Agent ergonomics, 90 against 83\n- Security \u0026 auth, 97 against 71\n- Transparency \u0026 trust, 63 against 54\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them\n\nWatch for: API models outage of about 3 hours 40 minutes on 3 September 2026, and high error rates on grok-4.6 and grok-4.5 on 17 August\n\n\n## Why the edge\n\n### Security \u0026 auth: xAI API (Grok) +26\n\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- xAI API (Grok) (97): Model reading. Team API keys with ACLs per endpoint and per model, QPM and TPM caps, expiry, and create, rotate, disable and delete through the Management API, plus documented mTLS. GitHub secret scanning disables leaked keys and emails the owner (30). The security FAQ says SpaceXSI never trains on API inputs or outputs without explicit permission (20). Requests and responses are kept 30 days for abuse auditing, then deleted, and team admins can switch on zero data retention themselves, confirmed by an `x-zero-data-retention` header on every response (15). Console audit log and a Management API audit-events endpoint, plus optional per-key request logging (15). security.txt valid to 2027-06-29 with a HackerOne bug bounty and a separate safety contact for prompt-injection issues. SOC 2 Type 2 is claimed in the security FAQ with the reports behind an NDA in the trust centre, so 17 of 20. Remote MCP doesn't support `require_approval`, which the model checklist doesn't score but reviewers should see. New in October, a `guidelines` array lets the caller make the model decline nsfw, violence or profanity content, which the checklist doesn't score.\n\n### Schema \u0026 documentation: xAI API (Grok) +15\n\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- xAI API (Grok) (88): OpenAPI 3.1 document at docs.x.ai/openapi.json, 39 paths and 205 schemas on 6 November, covering Responses, Chat Completions, files, images, videos and models. The batch endpoints documented in the REST reference still aren't in it (20 of 25, applied as for gemini-api's missing Interactions API). llms.txt and a Markdown twin of every page, plus a docs MCP server (10). The models page says which model to use for code, chat, images, video and voice, and reference pages list each parameter. Reference not read in full (18 of 20). Structured outputs are guaranteed to match the schema for supported keywords, and tool arguments always conform with `strict` implicitly true (15). Examples in Python, JavaScript and curl on every guide. The debugging page lists status codes with fixes, but the cause cells for 400, 403, 404 and 415 are still empty (13 of 15). Release notes are grouped by month without day dates, and model slugs come as aliases and dated versions (12 of 15).\n\n### Payments \u0026 pricing: Tencent Cloud TokenHub +15\n\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- xAI API (Grok) (20): No x402, MPP or L402 (0). Per-token and per-call prices published without a login on docs.x.ai/developers/pricing (20). No free tier found for the text API, and the quickstart says to load the account with credits (0). Sign-up is in the browser at console.x.ai. The Management API can create keys and top up prepaid credit, but only with a management key made by a person in the console, so no line credit (0).\n\n### Reliability: xAI API (Grok) +9\n\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- xAI API (Grok) (55): Status page at status.x.ai with components for the global and US API endpoints, voice, the consumer apps and, since the Cursor merger, Cursor's services, with an RSS feed (20). The feed, read on 6 November, now holds 267 incidents back to 11 August, so the whole 90-day window is readable. On the API components there were high error rates on grok-4.6 and grok-4.5 from 21:57 to 23:28 UTC on 17 August (about 90 minutes) and a models outage on the global and US endpoints from 13:30 to 17:09 UTC on 3 September (about 3 hours 40 minutes), so several majors. A 26-minute datacenter outage across the API on 22 September, voice disruptions of 12 and 28 minutes on 10 September and 6 October, a 63-minute voice and Imagine degradation on 30 October and a 37-second model degradation on 24 October add to the record (0). Rate limits published per model and tier, grok-4.7 at Tier 0 is 150 requests a second and 50M TPM, with the per-second cap derived as RPM divided by 48 (15). The rate-limits page shows exponential backoff on 429, but no Retry-After header or overload guidance was found (10 of 15). No SLA found in the docs or llms.txt (0). The Responses API has been GA since September 2025 and grok-4.7 carries no preview label (10).\n\n### Transparency \u0026 trust: xAI API (Grok) +9\n\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- xAI API (Grok) (63): Closed service under xAI's enterprise terms, with the Python SDK under Apache-2.0 (15). The docs agree with each other on no training, 30-day abuse retention, 30-day storage of stateful responses and the ZDR route, but the privacy policy, enterprise terms and DPA at x.ai/legal answered a Cloudflare block page on 6 October and again on 6 November, so they couldn't be compared (15 of 30). Dated migration guides and redirect tables for each retirement, but no written deprecation policy, and Chat Completions, Anthropic compatibility and grok-voice-2.0 are labelled deprecated with no date (12 of 20). The US regional endpoint states what stays in the US, the global endpoint guarantees no region, and no subprocessor list was readable (10 of 20).\n\n### Agent ergonomics: xAI API (Grok) +7\n\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- xAI API (Grok) (90): Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling with parallel calls on by default and `tool_choice` of auto, required, none or a named function (20). Guaranteed structured outputs (15). Automatic prompt caching, cached input at 0.25x on grok-4.7 ($0.50 per million) and 0.16x on grok-4.3 (15). 500,000-token context on grok-4.7 and 1,000,000 on grok-4.3, 13 of 15 for the default model's 500K. The Batch API is now 20% off on grok-4.7, 4.6 and 4.5 as well as the older models, with batch requests outside the rate limits (10 of 10, up from 5 on 6 October). One first-party SDK, `xai-sdk` for Python, with the OpenAI SDKs and Vercel's AI SDK documented as alternatives (5 of 10). Status codes documented with fixes, no Retry-After header found (12 of 15).\n\n## Score by category\n\n| Category | Weight | Tencent Cloud TokenHub | xAI API (Grok) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 46 | 55 | xAI API (Grok) +9 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 73 | 88 | xAI API (Grok) +15 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 90 | xAI API (Grok) +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 71 | 97 | xAI API (Grok) +26 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 20 | 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) | 73 | 77 | xAI API (Grok) +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 54 | 63 | xAI API (Grok) +9 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **59.5 · C** | **71.7 · BB** | |\n\n## Facts side by side\n\n| Fact | Tencent Cloud TokenHub | xAI API (Grok) |\n| --- | --- | --- |\n| Kind | Model router | Model API |\n| Vendor | Tencent Cloud | SpaceXSI (xAI) |\n| Hosted endpoint | `https://tokenhub.tencentmaas.com/v1` | `https://api.x.ai/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 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 | Proprietary service under xAI's enterprise terms of service. The Python SDK is Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-24 | 2026-11-02 |\n| Terms last updated | couldn't be read | 2026-10-27 |\n| Privacy policy last updated | couldn't be read | 2026-10-27 |\n| Customer content may train models | couldn't be read | yes |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 204 npm/wk | 597 stars, 912k PyPI/wk |\n\n## Verdicts\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**xAI API (Grok).** Grok 4.7 at $2/$6 per million tokens, now 20% off in batch, with a public OpenAPI spec, llms.txt, API keys limited by endpoint and model, and self-serve zero data retention. The API endpoints had a 3 hour 40 minute models outage on 3 September 2026, no SLA was found, and there's no free tier or first-party SDK beyond Python.\n\n## Before you call either\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### xAI API (Grok)\n\n1. Build on the Responses API at https://api.x.ai/v1. Chat Completions is labelled deprecated and the Anthropic-compatible endpoint fully deprecated\n2. Pin a dated model slug. A retired slug keeps answering from a replacement model, billed at the replacement's price\n3. Back off exponentially on 429. The per-second cap is the per-minute budget divided by 48, with a minimum of 2\n4. Set `allowed_tools` on remote MCP servers. There's no approval step, and every exposed tool enters the context\n5. Use https://us.api.x.ai/v1 when processing must stay in the US. It costs 1.1x and serves only grok-4.7 and grok-4.6\n\n## Questions\n\n### Which is better for AI agents, Tencent Cloud TokenHub or xAI API (Grok)?\n\nxAI API (Grok) scores 71.7 (BB) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing.\n\n### Do Tencent Cloud TokenHub and xAI API (Grok) need an API key?\n\nBoth need an API key.\n\n### Can an agent call Tencent Cloud TokenHub and xAI API (Grok) without installing anything?\n\nYes. Tencent Cloud TokenHub has a hosted endpoint at https://tokenhub.tencentmaas.com/v1 and xAI API (Grok) at https://api.x.ai/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"tencent-tokenhub\", \"b\": \"xai-api\"}`. From a terminal: `anchor compare tencent-tokenhub xai-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json and https://www.anchorterminal.com/api/v1/tools/xai-api.json\n\n## Other comparisons with Tencent Cloud TokenHub or xAI API (Grok)\n\n- [Amazon Bedrock vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub.md)\n- [Amazon Bedrock vs xAI API (Grok)](https://www.anchorterminal.com/compare/amazon-bedrock-vs-xai-api.md)\n- [Claude API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.md)\n- [Claude API vs xAI API (Grok)](https://www.anchorterminal.com/compare/anthropic-api-vs-xai-api.md)\n- [Antseed vs xAI API (Grok)](https://www.anchorterminal.com/compare/antseed-vs-xai-api.md)\n- [Azure OpenAI in Foundry Models vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub.md)\n- [Azure OpenAI in Foundry Models vs xAI API (Grok)](https://www.anchorterminal.com/compare/azure-openai-vs-xai-api.md)\n- [BlockRun.AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.md)\n- [BlockRun.AI vs xAI API (Grok)](https://www.anchorterminal.com/compare/blockrun-ai-vs-xai-api.md)\n- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.md)\n- [Cerebras Inference vs xAI API (Grok)](https://www.anchorterminal.com/compare/cerebras-inference-vs-xai-api.md)\n- [Cloudflare AI Gateway vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub.md)\n- [Cloudflare AI Gateway vs xAI API (Grok)](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-xai-api.md)\n- [Cloudflare Workers AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub.md)\n- [Cloudflare Workers AI vs xAI API (Grok)](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-xai-api.md)\n- [Cohere Chat API (Command models) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.md)\n- [Cohere Chat API (Command models) vs xAI API (Grok)](https://www.anchorterminal.com/compare/cohere-chat-vs-xai-api.md)\n- [DeepInfra vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.md)\n- [DeepInfra vs xAI API (Grok)](https://www.anchorterminal.com/compare/deepinfra-vs-xai-api.md)\n- [DeepSeek API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.md)\n- [DeepSeek API vs xAI API (Grok)](https://www.anchorterminal.com/compare/deepseek-api-vs-xai-api.md)\n- [Eden AI vs xAI API (Grok)](https://www.anchorterminal.com/compare/eden-ai-vs-xai-api.md)\n- [Glimpse vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.md)\n- [Glimpse vs xAI API (Grok)](https://www.anchorterminal.com/compare/elorian-glimpse-vs-xai-api.md)\n- [Fireworks AI Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.md)\n- [Fireworks AI Inference vs xAI API (Grok)](https://www.anchorterminal.com/compare/fireworks-inference-vs-xai-api.md)\n- [Gemini Developer API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.md)\n- [Gemini Developer API vs xAI API (Grok)](https://www.anchorterminal.com/compare/gemini-api-vs-xai-api.md)\n- [GroqCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.md)\n- [GroqCloud vs xAI API (Grok)](https://www.anchorterminal.com/compare/groq-vs-xai-api.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- [Inkling 2 Small vs xAI API (Grok)](https://www.anchorterminal.com/compare/inkling-2-small-vs-xai-api.md)\n- [Jais 3 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.md)\n- [Jais 3 vs xAI API (Grok)](https://www.anchorterminal.com/compare/jais-3-vs-xai-api.md)\n- [Meta Model API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.md)\n- [Meta Model API vs xAI API (Grok)](https://www.anchorterminal.com/compare/meta-model-api-vs-xai-api.md)\n- [MiniMax API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.md)\n- [MiniMax API vs xAI API (Grok)](https://www.anchorterminal.com/compare/minimax-api-vs-xai-api.md)\n- [Mistral AI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.md)\n- [Mistral AI API vs xAI API (Grok)](https://www.anchorterminal.com/compare/mistral-api-vs-xai-api.md)\n- [Muse Spark Open vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.md)\n- [Muse Spark Open vs xAI API (Grok)](https://www.anchorterminal.com/compare/muse-spark-open-vs-xai-api.md)\n- [Nemotron 3.5 Super VL vs xAI API (Grok)](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-xai-api.md)\n- [Novita AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.md)\n- [Novita AI vs xAI API (Grok)](https://www.anchorterminal.com/compare/novita-ai-vs-xai-api.md)\n- [OpenAI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.md)\n- [OpenAI API vs xAI API (Grok)](https://www.anchorterminal.com/compare/openai-api-vs-xai-api.md)\n- [OpenRouter vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.md)\n- [OpenRouter vs xAI API (Grok)](https://www.anchorterminal.com/compare/openrouter-vs-xai-api.md)\n- [Prism Inference vs xAI API (Grok)](https://www.anchorterminal.com/compare/prism-inference-vs-xai-api.md)\n- [Router.com (Ramp Router) vs xAI API (Grok)](https://www.anchorterminal.com/compare/ramp-router-vs-xai-api.md)\n- [Beam 1.0 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.md)\n- [Beam 1.0 vs xAI API (Grok)](https://www.anchorterminal.com/compare/reflection-beam-vs-xai-api.md)\n- [RouterPlus vs xAI API (Grok)](https://www.anchorterminal.com/compare/routerplus-vs-xai-api.md)\n- [SambaCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.md)\n- [SambaCloud vs xAI API (Grok)](https://www.anchorterminal.com/compare/sambanova-vs-xai-api.md)\n- [SiliconFlow vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.md)\n- [SiliconFlow vs xAI API (Grok)](https://www.anchorterminal.com/compare/siliconflow-vs-xai-api.md)\n- [Simplismart vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.md)\n- [Simplismart vs xAI API (Grok)](https://www.anchorterminal.com/compare/simplismart-vs-xai-api.md)\n- [StepFun API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.md)\n- [StepFun API vs xAI API (Grok)](https://www.anchorterminal.com/compare/stepfun-api-vs-xai-api.md)\n- [SWE-2 Flash vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/swe-2-flash-vs-tencent-tokenhub.md)\n- [SWE-2 Flash vs xAI API (Grok)](https://www.anchorterminal.com/compare/swe-2-flash-vs-xai-api.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- [Together AI Inference vs xAI API (Grok)](https://www.anchorterminal.com/compare/together-inference-vs-xai-api.md)\n- [Vercel AI Gateway vs xAI API (Grok)](https://www.anchorterminal.com/compare/vercel-ai-gateway-vs-xai-api.md)\n- [Vertex AI (Gemini Enterprise Agent Platform) vs xAI API (Grok)](https://www.anchorterminal.com/compare/vertex-ai-vs-xai-api.md)\n- [Antseed vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.md)\n- [Eden AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/eden-ai-vs-tencent-tokenhub.md)\n- [Hugging Face Inference Providers vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.md)\n- [LiteLLM vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/litellm-vs-tencent-tokenhub.md)\n- [Router.com (Ramp Router) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.md)\n- [RouterPlus vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Vercel AI Gateway](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.md)\n- [Nemotron 3.5 Super VL vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub.md)\n- [Prism Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Tencent Cloud TokenHub vs xAI API (Grok)", "url": "" } ], "description": "xAI scores 71.7 (BB) to Tencent Cloud TokenHub's 59.5 (C) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Tencent Cloud TokenHub C 59.5", "xAI API (Grok) BB 71.7", "scores" ], "h1": "Tencent Cloud TokenHub vs xAI API (Grok)", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/tencent-tokenhub-vs-xai-api", "published": "2026-10-01", "section": "tools", "title": "Tencent Cloud TokenHub vs xAI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api" }, "tokens": { "markdown": 7450, "slim": 3880 }, "version": 1 }