{ "data": { "a": { "slug": "openai-api", "name": "OpenAI API", "vendor": "OpenAI", "vendorUrl": "https://developers.openai.com", "kind": "model", "category": "inference", "summary": "OpenAI's API for accessing its models through Responses, Chat Completions and Batch endpoints.", "url": "https://www.anchorterminal.com/tools/openai-api", "markdownUrl": "https://www.anchorterminal.com/tools/openai-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/openai-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/openai-api.json", "dns": "openai-api.grade.anchorterminal.com", "repo": "https://github.com/openai/openai-python", "license": "Apache-2.0 (SDKs)", "transports": [ "http" ], "remoteUrl": "https://api.openai.com/v1", "packages": [ { "registry": "pypi", "name": "openai" }, { "registry": "npm", "name": "openai" } ], "auth": "api-key", "authNotes": "`Authorization: Bearer` with a project key. Some models and tools need business or ID verification first.", "pricing": "usage", "pricingNotes": "Prepaid credit, with the Build tier reached at $5 in credit purchases, Launch at $100 and Grow at $500. Long context over 272K tokens costs 2x input and 1.5x output. Cache reads 0.1x input (0.05x on GPT-6.1 Sol and GPT-6.1 Terra), cache writes 1.25x from GPT-5.6 on, or 2.5x for the 12-hour lifetime in the Responses API since 20 October. Batch and Flex half price, Fast mode 2x, Ultrafast 6x (GPT-6 Astra, and GPT-6.1 Sol since 8 October). Data residency endpoints add 10% for models released on or after 5 March 2026, and FedRAMP endpoints add 10% from 1 November 2026. Web search $10 per 1,000 calls plus search content tokens, file search $2.50 per 1,000, hosted containers from $0.03 per 20-minute session (https://developers.openai.com/api/docs/pricing).", "priceSummary": "from $0.10 / 1M in", "where": "hosted", "x402": { "level": "no", "evidence": "No machine payment. Access needs an account with prepaid credit.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 31300, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-26" }, "docsUrl": "https://developers.openai.com/api/docs", "rateLimitsUrl": "https://developers.openai.com/api/docs/guides/rate-limits", "llmsTxt": "https://developers.openai.com/llms.txt", "openapi": "https://github.com/openai/openai-openapi", "capabilities": [ "inference.llm" ], "tags": [ "official", "hosted", "model", "card-required", "openapi", "llms-txt" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 83.9, "grade": "A", "agentReady": true, "rank": 4, "ranked": true, "rankOf": 1260, "categoryRank": 1, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 98, "maintenance": 87, "payments": 30, "reliability": 75, "schema": 100, "security": 100, "transparency": 90 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Official OpenAPI document and an llms.txt index. Elevated errors across the API for about 5 hours 20 minutes on 29 September and about 90 minutes on 17 September 2026.", "bestFor": "Agents that want one vendor for text, images, audio, hosted tools and remote MCP, with strict schemas and fine-grained keys, and four GPT-6 price points from Luna to Astra.", "strengths": [ "Official OpenAPI document and an llms.txt index", "Project keys can be restricted per endpoint to None, Read or Write, and mutual TLS workload identity is GA", "A dated deprecations page, and `GET /v1/models` returns each model's `shutdown_date`", "GPT-6 Luna at $0.10/$0.50 per million tokens with the same 1.05M context as Astra", "Scale Tier comes with a 99.9% uptime SLA" ], "weaknesses": [ "Elevated errors across the API for about 5 hours 20 minutes on 29 September and about 90 minutes on 17 September 2026", "Heavy migration calendar. Assistants API gone on 2026-08-26, Agent Builder, Evals and `v1/prompts` on 2026-11-30, GPT-5 and o3 on 2026-12-11", "GPT-6 models aren't available on the Free tier, so a card and prepaid credit come first in practice", "GPT-6 Astra has no custom temperature, no logprobs and no tool calling outside the Responses API", "GPT-4o and GPT-4.1 snapshots got 92 days' notice on 14 October, against the 6 months the deprecations page promises GA models" ], "agentNotes": [ "Build on the Responses API. Astra calls tools only there", "Use `gpt-6-luna` for routing and extraction, `gpt-6.1-terra` for screens, images and computer use at half Sol's price, and `gpt-6.1-sol` for most work. The models page still points unsure callers to `gpt-6-astra`", "Move off the GPT-4o and GPT-4.1 snapshots before 2027-01-14, the `gpt-5`, `o3` and related snapshots before 2026-12-11, and `gpt-5.1`, `gpt-5.3-codex` and `gpt-5.4-nano` before 2027-04-01. Check `shutdown_date` on `GET /v1/models`", "Treat 429 `slow_down` as a ramp limit and 503 `server_is_overloaded` as a retry, and follow `Retry-After` when it's sent", "Prompts over 272K tokens cost double on input. Trim before you pay for it" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "A", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 83.9 } ], "editorialScores": { "ergonomics": 98, "maintenance": 87, "payments": 30, "reliability": 75, "schema": 100, "security": 100, "transparency": 85 }, "provenanceScore": 95, "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", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install openai # or: npm i openai", "http": "curl https://api.openai.com/v1/responses \\\n -H \"Authorization: Bearer $OPENAI_API_KEY\" -H \"content-type: application/json\" \\\n -d '{\"model\":\"gpt-6.1-sol\",\"input\":\"hello\"}'" }, "letme": { "capability": "https://letme.dev/inference.llm", "tool": "https://letme.dev/openai-api" }, "sameCompany": [ "openai-embeddings", "openai-guardrails", "openai-moderation", "openai-image-api", "openai-sora", "openai-speech-to-text", "gpt-live", "openai-realtime", "openai-agents-sdk", "openai-decisions-api", "openai-codex", "gpt-oss-120b", "gpt-oss-20b" ], "area": "models", "unitPrices": [ { "item": "Web search tool", "unit": "1k-requests", "usd": 10 }, { "item": "File search tool", "unit": "1k-requests", "usd": 2.5 } ], "provenance": { "legalEntity": "OpenAI OpCo, LLC", "domain": "openai.com", "domainRegistered": "2007-01-19", "domainNote": "openai.com was registered in 2007, before OpenAI existed.", "endpointOnVendorDomain": true, "terms": "https://openai.com/policies/services-agreement/", "privacy": "https://openai.com/policies/privacy-policy/", "statusPage": "https://status.openai.com", "changelog": "https://developers.openai.com/api/docs/changelog", "securityTxt": "valid", "checked": "2026-09-26", "score": 95 }, "requirements": { "card": "paid-only", "freeTier": true, "minutes": 5, "credential": "api-key", "hosting": [ "US", "EU", "UK", "CA", "APAC" ], "euResidency": "enterprise", "trainsOnData": "no", "zeroRetention": "enterprise", "certifications": [ "SOC 2 Type II", "ISO 27001", "ISO 27701", "ISO 42001", "CSA STAR", "HIPAA (BAA available)", "GDPR" ], "dpa": true, "selfHost": "no" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/openai-api.json", "live": { "slug": "openai-api", "probe": { "target": "https://api.openai.com/v1", "method": "get", "lastAt": "2026-11-02T00:56:14.148144045Z", "lastOk": true, "lastStatus": 404, "lastMs": 149, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 139, "p95ms24h": 182, "samples24h": 249, "samples30d": 7898, "days": [ { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 10, "ok": 10 } ] }, "vendorStatus": { "page": "https://status.openai.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-02T01:01:07.371776234Z" }, "versions": [ { "registry": "github", "name": "openai/openai-python", "version": "v3.42.0", "released": "2026-10-31", "seenAt": "2026-11-01T17:20:34.638937879Z" }, { "registry": "npm", "name": "openai", "version": "7.47.0", "seenAt": "2026-11-01T17:20:34.527637733Z" }, { "registry": "pypi", "name": "openai", "version": "3.42.0", "released": "2026-10-31", "seenAt": "2026-11-01T17:20:34.339423842Z" } ], "githubStars": 32000, "npmWeekly": 55491198, "pypiWeekly": 85437895, "securityTxt": { "url": "https://openai.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-01T15:43:04.210354007Z" }, "llmsTxt": { "url": "https://developers.openai.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:14:30.604240488Z" }, "domain": { "domain": "openai.com", "registered": "2007-01-19", "source": "https://rdap.verisign.com/com/v1/domain/openai.com", "checkedAt": "2026-11-01T14:19:18.345389832Z" }, "pages": [ { "url": "https://developers.openai.com/api/docs/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-16T22:20:47.232011113Z", "changedAt": "2026-10-16T22:20:47.232011113Z", "fingerprint": "3261efc5e241" }, { "url": "https://developers.openai.com/api/docs/deprecations", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-01T06:40:09.906842404Z", "changedAt": "2026-10-27T03:42:45.240976026Z", "fingerprint": "7fe7bca3cacf" }, { "url": "https://developers.openai.com/api/docs/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-01T06:40:11.924784518Z", "changedAt": "2026-11-01T06:40:11.924784518Z", "fingerprint": "69957cc759d3" } ], "models": { "gpt-6-astra": { "openrouterId": "openai/gpt-6-astra", "tools": true, "structuredOutputs": true, "jsonMode": true, "reasoning": true, "input": [ "file", "image", "text" ], "promptCaching": true, "contextTokens": 1050000, "maxOutput": 128000, "checkedAt": "2026-11-01T23:49:20.31928442Z" }, "gpt-6-luna": { "openrouterId": "openai/gpt-6-luna", "tools": true, "structuredOutputs": true, "jsonMode": true, "reasoning": true, "input": [ "file", "image", "text" ], "promptCaching": true, "contextTokens": 1050000, "maxOutput": 128000, "checkedAt": "2026-11-01T23:49:20.31928442Z" }, "gpt-6-sol": { "openrouterId": "openai/gpt-6-sol", "tools": true, "structuredOutputs": true, "jsonMode": true, "reasoning": true, "input": [ "file", "image", "text" ], "promptCaching": true, "contextTokens": 1050000, "maxOutput": 128000, "checkedAt": "2026-10-04T21:56:15.872733218Z" }, "gpt-6.1-sol": { "openrouterId": "openai/gpt-6.1-sol", "tools": true, "structuredOutputs": true, "jsonMode": true, "reasoning": true, "input": [ "file", "image", "text" ], "promptCaching": true, "contextTokens": 1050000, "maxOutput": 128000, "checkedAt": "2026-11-01T23:49:20.31928442Z" }, "gpt-6.1-terra": { "openrouterId": "openai/gpt-6.1-terra", "tools": true, "structuredOutputs": true, "jsonMode": true, "reasoning": true, "input": [ "file", "image", "text" ], "promptCaching": true, "contextTokens": 1050000, "maxOutput": 128000, "checkedAt": "2026-11-01T23:49:20.31928442Z" } }, "github": { "repo": "openai/openai-python", "checkedAt": "2026-10-26T07:52:32.552796024Z", "stars": 31956, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-25T20:49:31Z", "openIssues": 47, "openPRs": 73, "issuesOpened90d": 48, "issuesClosed90d": 215, "prsMerged90d": 396, "ci": { "branch": "main", "runs": 50, "success": 48, "failure": 0, "other": 2, "latest": "success", "latestAt": "2026-10-25T20:54:11Z" }, "replies": { "sampled": 25, "unanswered": 8, "medianDays": 4.4 } }, "updatedAt": "2026-11-02T01:01:07.371776234Z" } }, "answer": "OpenAI API scores 83.9 (A) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing.", "b": { "slug": "tencent-tokenhub", "name": "Tencent Cloud TokenHub", "vendor": "Tencent Cloud", "vendorUrl": "https://cloud.tencent.com", "kind": "router", "category": "inference", "summary": "Tencent Cloud TokenHub is a hosted model gateway serving Tencent's Hy models and third-party models such as DeepSeek, Kimi, GLM and MiniMax through OpenAI-compatible and Anthropic-compatible endpoints in Guangzhou and Singapore, with per-key scopes and quotas.", "url": "https://www.anchorterminal.com/tools/tencent-tokenhub", "markdownUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json", "dns": "tencent-tokenhub.grade.anchorterminal.com", "repo": "https://github.com/TencentCloud/THCLI", "license": "Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://tokenhub.tencentmaas.com/v1", "packages": [ { "registry": "npm", "name": "tencent-tokenhub-cli" } ], "auth": "api-key", "authNotes": "Bearer API key from the TokenHub console, or `x-api-key` on the Anthropic-style `/v1/messages`. Keys are long-lived, belong to one region (Guangzhou or Singapore), can be limited to chosen models and inference services, up to 200 IP ranges and token quotas, and can be disabled or deleted. They can also be created through the CreateApiKey control-plane call with signed Tencent Cloud credentials, or by `thcli auth login`. The account needs real-name verification first.", "pricing": "usage", "pricingNotes": "Pay per token in CNY, billed hourly. Hy4 preview costs 6 CNY in, 18 CNY out and 0.3 CNY cached per 1M tokens, Hy3 1, 4 and 0.25 CNY. DeepSeek models double at weekday peak hours. Batch is half price for Hy3 and Hy4 preview. Each account gets 1M free tokens per language model for a year, in a campaign to 31 December 2026. Token Plan subscriptions run from 28 to 599 CNY a month (https://cloud.tencent.com/document/product/1823/130055, checked 2026-11-01).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs table of contents, the billing pages or the API usage page. Payment is from a Tencent Cloud account balance, billed hourly (checked 2026-11-01).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 204, "pypiWeekly": null, "asOf": "2026-11-01" }, "docsUrl": "https://cloud.tencent.com/document/product/1823/130058", "rateLimitsUrl": "https://cloud.tencent.com/document/product/1823/136028", "llmsTxt": "https://cloud.tencent.com/document/product/1823/llms.txt", "capabilities": [ "inference.router", "inference.llm", "inference.open-weights", "embed.text", "embed.multimodal", "image.generate", "video.generate", "speech.tts", "speech.stt", "audio.music", "translate.text", "web.search", "obs.gateway" ], "tags": [ "hosted", "router", "usage-based", "free-credit", "openai-compatible", "anthropic-compatible", "llms-txt", "cli", "sla", "batch", "bug-bounty", "no-status-page", "regional-endpoints", "singapore", "chinese", "subscription" ], "lastRelease": "2026-10-24", "graded": true, "anchor": { "graded": true, "score": 59.5, "grade": "C", "agentReady": false, "rank": 646, "ranked": true, "rankOf": 1260, "categoryRank": 18, "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-02T00:56:24.101434531Z", "lastOk": true, "lastStatus": 404, "lastMs": 795, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 826, "p95ms24h": 1067, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-11-01", "probes": 18, "ok": 18 }, { "date": "2026-11-02", "probes": 10, "ok": 10 } ] }, "updatedAt": "2026-11-02T00:56:24.101434531Z" } }, "edges": [ { "by": 36, "category": "transparency", "leads": "openai-api", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with clear terms, SDKs Apache-2.0 (15). The data-controls guide, re-read on 1 November, gives retention periods per endpoint, the training default and the ZDR route. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum for transfers, and nothing in it conflicts with the guide, per the 4 October check, not re-read on 1 November (30). Deprecations page with announcement and shutdown dates, and `GET /v1/models` returns each model's `shutdown_date` (20). The subprocessor list, updated 9 July 2026, names its third-party subprocessors and OpenAI affiliates with the processing countries for each and a form to get notice of new ones, and data residency regions are listed, per the 4 October check, not re-read on 1 November (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": 90, "b": 54 } }, { "by": 29, "category": "reliability", "leads": "openai-api", "name": "Reliability", "reasons": { "a": "Status page at status.openai.com with component history (20). Two API-wide majors in the 90 days to 1 November, elevated errors across ChatGPT, Codex and the API (the Agents API included) on 29 September, with Chat Completions, Responses, Batch, Realtime, Embeddings, Images, Files and the other API components degraded from 17:52 to 23:14 UTC, and elevated error rates across API models on 17 September, with eleven components degraded from 20:20 to 21:20 UTC. Two majors give 5 of 30. The 25 July incident is now outside the window. The 29 September write-up, posted on 6 October, traces it to a feature rollout that exhausted shared network connection capacity. Every other incident since 3 August that lists an API component is partial or under an hour, so minor. Degraded performance across ChatGPT, Codex and the APIs on 21 October listed every API component but ran 22 minutes (02:26 to 02:48 UTC). Single-model incidents were GPT-5.6 Sol errors on 11 September (09:08 to 11:21 UTC), `gpt-5.6-luna` errors on 21 October (70 minutes) and GPT-6.1 Sol degraded performance on Batch, Chat Completions and Responses on 27 October (78 minutes). Partial incidents were latency for some Responses requests on the US endpoint on 31 August and 1 September, image generation where some requests failed on 8 September, latency for some Responses and Chat Completions requests on 30 September, large-PDF errors in Responses and an Agents API computer use incident on 6 October, Responses errors for users in India, Japan and Korea on 22 October and errors on some GPT Image 2 edit requests on 30 October (14:35 to 18:36 UTC). Image model incidents on 16 September and 14 October and file download errors on 19 October each ran about 40 minutes. FedRAMP errors for Astra and Sol on 21 October and authentication errors near Illinois on 20 October list no API component. Rate limits published per tier and model family with rate-limit headers (15). 429 guidance, re-read on 1 November, covers `Retry-After` as a minimum wait, backoff with jitter when it's missing, a gradual ramp, and splits `slow_down` (429) from `server_is_overloaded` (503) (15). Scale Tier carries a 99.9% uptime SLA, through sales, per the 1 October check, not re-read on 1 November (10). Responses and Chat Completions are GA (10). 20 + 5 + 15 + 15 + 10 + 10 = 75.", "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": 75, "b": 46 } }, { "by": 29, "category": "security", "leads": "openai-api", "name": "Security \u0026 auth", "reasons": { "a": "Model reading. Project keys with All, Restricted (per-endpoint None, Read or Write) and Read Only permissions, service accounts, and mutual TLS with X.509 workload identity GA since 26 August, per the 1 October check. The changelog adds project key expiry dates on 10 September, key-creation controls on 15 September and, on 21 October, organisation and project settings that limit which service tiers a project may use (30). API data not used for training unless the customer opts in, since 1 March 2023 (20). Abuse-monitoring logs kept up to 30 days, and Zero Data Retention or Modified Abuse Monitoring by approval. The data-controls guide re-read on 1 November lists Chat Completions, Responses, Decisions and ten other endpoints as ZDR-eligible; `/v1/agents`, Conversations, Files and vector stores aren't (15). Usage and Costs filter by API key since 4 August, with Admin APIs to match, and audit logs for enterprise (15). SOC 2 Type 2, ISO 27001, 27017, 27018, 27701 and 42001 per the 1 October check, not re-read on 1 November, a Bugcrowd bug bounty and a coordinated disclosure policy, both linked from a signed security.txt. That security.txt had no Expires field on 27 October, which RFC 9116 requires, so the disclosure policy carries this line. It wasn't re-read on 1 November (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": 100, "b": 71 } }, { "by": 27, "category": "schema", "leads": "openai-api", "name": "Schema \u0026 documentation", "reasons": { "a": "Official OpenAPI document (openapi.yaml and openapi.json) in the openai/openai-openapi repository, whose openapi.yaml (version 2.3.0, updated 31 October) lists `gpt-6.1-terra` (25). llms.txt index with per-product files, and every docs page has a Markdown twin at `.md` (10). The reference documents each parameter, and model pages say which model fits which job (20). Structured outputs with `strict: true` on schemas and function tools (15). Error codes guide with types and recovery advice, now with a 400 `service_tier` error for tiers a project doesn't allow (15). Dated model snapshots and a dated changelog, last entry 30 October (15).", "b": "Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use `deepseek-v3`, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry `/v1`, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15)." }, "scores": { "a": 100, "b": 73 } }, { "by": 15, "category": "ergonomics", "leads": "openai-api", "name": "Agent ergonomics", "reasons": { "a": "Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use with parallel calls and forced tool choice, 18 of 20 because GPT-6 Astra, GPT-6.1 Sol and GPT-6.1 Terra call tools only through the Responses API (18). Strict structured outputs (15). Automatic prompt caching with cached input at 0.1x on Astra and Luna ($0.01 per million on Luna) and 0.05x on GPT-6.1 Sol ($0.10) and GPT-6.1 Terra ($0.05), and a 12-hour cache lifetime in the Responses API since 20 October (15). 1.05M context on Astra, GPT-6.1 Sol, GPT-6.1 Terra and Luna (15). Batch at half price (10). Official SDKs in Python, JavaScript and more (10). Documented error codes with retry guidance (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": 98, "b": 83 } }, { "by": 14, "category": "maintenance", "leads": "openai-api", "name": "Maintenance \u0026 community", "reasons": { "a": "Model reading. GPT-6 Rosalind, a life-sciences model for approved organisations, launched on 30 October, after GPT-6.1 Terra on 26 October and the Decisions API GA on 22 October (30). Published minimum notice of 6 months for GA models, 3 months for specialised variants, as little as 2 weeks for previews. On 14 October GPT-4o (`gpt-4o-2024-08-06`, `gpt-4o-2024-11-20`), GPT-4o mini, GPT-4.1 and GPT-4.1 mini were given a shutdown date of 14 January 2027, 92 days, with no safety or compliance reason stated. These are GA models, so the page's own 6-month minimum wasn't kept, as with `gpt-5.4-cyber`'s 20 days in September. 8 of 12, the award for a minimum of two to three months in practice. Five shutdown dates in the 90 days to 1 November, the Assistants API on 26 August (announced in August 2025), `gpt-5.2-chat-latest` and `gpt-5.3-chat-latest` on 10 August (announced 8 May), `gpt-3.5-turbo-instruct`, `babbage-002`, `davinci-002` and `gpt-3.5-turbo-1106` on 28 September (announced 26 September 2025, missed in the 27 October count), `gpt-5.4-cyber` on 1 October and the legacy snapshots on 23 October (announced 22 April). Sora 2 and the Videos API (24 September) are scored on the openai-sora listing. Four of the five kept the published notice, so 4 of 8 as before, as amazon-bedrock has for four dates after full notice. Dated changelog several times a month and a help centre (15 of 15). openai-python had 215 open issues per the 1 October check, replies not sampled (5 of 10). Current official SDKs, `openai` 3.42.0 on PyPI (31 October) and npm `openai` 7.47.0 (15). Supported runtimes stated, Python 3.10 or later and Node 22 or later, the npm package's `engines` re-read on 1 November (10).", "b": "Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q\u0026A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and `tencent-tokenhub-cli` 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10)." }, "scores": { "a": 87, "b": 73 } } ], "facts": [ { "a": "Model API", "b": "Model router", "name": "Kind" }, { "a": "OpenAI", "b": "Tencent Cloud", "name": "Vendor" }, { "a": "https://api.openai.com/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": "Apache-2.0 (SDKs)", "b": "Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2026-10-24", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "31k stars", "b": "204 npm/wk", "name": "Popularity" }, { "a": "3.5/5 (8)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "OpenAI API scores 83.9 (A) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing.", "question": "Which is better for AI agents, OpenAI API or Tencent Cloud TokenHub?" }, { "answer": "Both need an API key.", "question": "Do OpenAI API and Tencent Cloud TokenHub need an API key?" }, { "answer": "Yes. OpenAI API has a hosted endpoint at https://api.openai.com/v1 and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.", "question": "Can an agent call OpenAI API and Tencent Cloud TokenHub without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 46", "Schema \u0026 documentation, 100 against 73", "Agent ergonomics, 98 against 83", "Security \u0026 auth, 100 against 71", "Maintenance \u0026 community, 87 against 73", "Transparency \u0026 trust, 90 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 one vendor for text, images, audio, hosted tools and remote MCP, with strict schemas and fine-grained keys, and four GPT-6 price points from Luna to Astra.", "slug": "openai-api", "watchFor": "Elevated errors across the API for about 5 hours 20 minutes on 29 September and about 90 minutes on 17 September 2026" }, { "aheadOn": [ "Payments \u0026 pricing, 35 against 30" ], "also": null, "goodFor": "Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing.", "slug": "tencent-tokenhub", "watchFor": "Sign-up needs a Tencent Cloud account with real-name verification. The international site answered with a bot check, so access from outside China was not established" } ], "history": { "openai-api": [ { "causes": [ "correction" ], "date": "2026-11-01", "delta": 1, "from": 82.9, "fromGrade": "A", "to": 83.9, "toGrade": "A" }, { "causes": [ "product" ], "date": "2026-10-17", "delta": -0.4, "from": 83.3, "fromGrade": "A", "to": 82.9, "toGrade": "A" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 83.5, "fromGrade": "A", "to": 83.3, "toGrade": "A" } ], "tencent-tokenhub": null }, "job": { "capability": "inference.llm", "name": "LLM inference" }, "others": [ { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-openai-api.json", "title": "Claude API vs OpenAI API", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-openai-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/antseed-vs-openai-api.json", "title": "Antseed vs OpenAI API", "url": "https://www.anchorterminal.com/compare/antseed-vs-openai-api" }, { "json": "https://www.anchorterminal.com/compare/blockrun-ai-vs-openai-api.json", "title": "BlockRun.AI vs OpenAI API", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-openai-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/cerebras-inference-vs-openai-api.json", "title": "Cerebras Inference vs OpenAI API", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-openai-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/cloudflare-ai-gateway-vs-openai-api.json", "title": "Cloudflare AI Gateway vs OpenAI API", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-openai-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-workers-ai-vs-openai-api.json", "title": "Cloudflare Workers AI vs OpenAI API", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-openai-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/cohere-chat-vs-openai-api.json", "title": "Cohere Chat API (Command models) vs OpenAI API", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-openai-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/deepinfra-vs-openai-api.json", "title": "DeepInfra vs OpenAI API", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-openai-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/deepseek-api-vs-openai-api.json", "title": "DeepSeek API vs OpenAI API", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-openai-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/elorian-glimpse-vs-openai-api.json", "title": "Glimpse vs OpenAI API", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-openai-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/fireworks-inference-vs-openai-api.json", "title": "Fireworks AI Inference vs OpenAI API", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-openai-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/gemini-api-vs-openai-api.json", "title": "Gemini Developer API vs OpenAI API", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-openai-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/groq-vs-openai-api.json", "title": "GroqCloud vs OpenAI API", "url": "https://www.anchorterminal.com/compare/groq-vs-openai-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/jais-3-vs-openai-api.json", "title": "Jais 3 vs OpenAI API", "url": "https://www.anchorterminal.com/compare/jais-3-vs-openai-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/meta-model-api-vs-openai-api.json", "title": "Meta Model API vs OpenAI API", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-openai-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/minimax-api-vs-openai-api.json", "title": "MiniMax API vs OpenAI API", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-openai-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/mistral-api-vs-openai-api.json", "title": "Mistral AI API vs OpenAI API", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-openai-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/muse-spark-open-vs-openai-api.json", "title": "Muse Spark Open vs OpenAI API", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-openai-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/nemotron-3-5-super-vl-vs-openai-api.json", "title": "Nemotron 3.5 Super VL vs OpenAI API", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-openai-api" }, { "json": "https://www.anchorterminal.com/compare/novita-ai-vs-openai-api.json", "title": "Novita AI vs OpenAI API", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-openai-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/openai-api-vs-openrouter.json", "title": "OpenAI API vs OpenRouter", "url": "https://www.anchorterminal.com/compare/openai-api-vs-openrouter" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-prism-inference.json", "title": "OpenAI API vs Prism Inference", "url": "https://www.anchorterminal.com/compare/openai-api-vs-prism-inference" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-ramp-router.json", "title": "OpenAI API vs Router.com (Ramp Router)", "url": "https://www.anchorterminal.com/compare/openai-api-vs-ramp-router" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-reflection-beam.json", "title": "OpenAI API vs Beam 1.0", "url": "https://www.anchorterminal.com/compare/openai-api-vs-reflection-beam" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-routerplus.json", "title": "OpenAI API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/openai-api-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-sambanova.json", "title": "OpenAI API vs SambaCloud", "url": "https://www.anchorterminal.com/compare/openai-api-vs-sambanova" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-siliconflow.json", "title": "OpenAI API vs SiliconFlow", "url": "https://www.anchorterminal.com/compare/openai-api-vs-siliconflow" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-simplismart.json", "title": "OpenAI API vs Simplismart", "url": "https://www.anchorterminal.com/compare/openai-api-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-stepfun-api.json", "title": "OpenAI API vs StepFun API", "url": "https://www.anchorterminal.com/compare/openai-api-vs-stepfun-api" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-together-inference.json", "title": "OpenAI API vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/openai-api-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-vercel-ai-gateway.json", "title": "OpenAI API vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/openai-api-vs-vercel-ai-gateway" }, { "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/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/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" }, { "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/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" } ], "panel": null, "scores": [ { "by": 29, "edge": "openai-api", "key": "reliability", "name": "Reliability", "openai-api": 75, "tencent-tokenhub": 46, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 27, "edge": "openai-api", "key": "schema", "name": "Schema \u0026 documentation", "openai-api": 100, "tencent-tokenhub": 73, "weight": 13 }, { "by": 15, "edge": "openai-api", "key": "ergonomics", "name": "Agent ergonomics", "openai-api": 98, "tencent-tokenhub": 83, "weight": 13 }, { "by": 29, "edge": "openai-api", "key": "security", "name": "Security \u0026 auth", "openai-api": 100, "tencent-tokenhub": 71, "weight": 14 }, { "by": 5, "edge": "tencent-tokenhub", "key": "payments", "name": "Payments \u0026 pricing", "openai-api": 30, "tencent-tokenhub": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 14, "edge": "openai-api", "key": "maintenance", "name": "Maintenance \u0026 community", "openai-api": 87, "tencent-tokenhub": 73, "weight": 7 }, { "by": 36, "edge": "openai-api", "key": "transparency", "name": "Transparency \u0026 trust", "openai-api": 90, "tencent-tokenhub": 54, "weight": 7 } ], "summary": "OpenAI API scores 83.9 (A) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing. Both do llm inference.", "tasks": null, "tutorials": [], "verdicts": { "openai-api": "Official OpenAPI document and an llms.txt index. Elevated errors across the API for about 5 hours 20 minutes on 29 September and about 90 minutes on 17 September 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/openai-api-vs-tencent-tokenhub", "json": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.min.md" }, "markdown": "OpenAI API scores 83.9 (A) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing. Both do llm inference.\n\n- OpenAI API: grade A, 83.9/100, rank #4 of 1260. Markdown https://www.anchorterminal.com/tools/openai-api.md · JSON https://www.anchorterminal.com/api/v1/tools/openai-api.json\n- Tencent Cloud TokenHub: grade C, 59.5/100, rank #646 of 1260. 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 529 models comparisons: https://www.anchorterminal.com/compare/inference/index.md\n\n## Which one, for what\n\n### OpenAI API (A)\n\nGood for: Agents that want one vendor for text, images, audio, hosted tools and remote MCP, with strict schemas and fine-grained keys, and four GPT-6 price points from Luna to Astra.\n\nAhead on:\n- Reliability, 75 against 46\n- Schema \u0026 documentation, 100 against 73\n- Agent ergonomics, 98 against 83\n- Security \u0026 auth, 100 against 71\n- Maintenance \u0026 community, 87 against 73\n- Transparency \u0026 trust, 90 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: Elevated errors across the API for about 5 hours 20 minutes on 29 September and about 90 minutes on 17 September 2026\n\n### Tencent Cloud TokenHub (C)\n\nGood for: Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing.\n\nAhead on:\n- Payments \u0026 pricing, 35 against 30\n\nWatch for: Sign-up needs a Tencent Cloud account with real-name verification. The international site answered with a bot check, so access from outside China was not established\n\n\n## Why the edge\n\n### Transparency \u0026 trust: OpenAI API +36\n\n- OpenAI API (90): Closed service with clear terms, SDKs Apache-2.0 (15). The data-controls guide, re-read on 1 November, gives retention periods per endpoint, the training default and the ZDR route. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum for transfers, and nothing in it conflicts with the guide, per the 4 October check, not re-read on 1 November (30). Deprecations page with announcement and shutdown dates, and `GET /v1/models` returns each model's `shutdown_date` (20). The subprocessor list, updated 9 July 2026, names its third-party subprocessors and OpenAI affiliates with the processing countries for each and a form to get notice of new ones, and data residency regions are listed, per the 4 October check, not re-read on 1 November (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### Reliability: OpenAI API +29\n\n- OpenAI API (75): Status page at status.openai.com with component history (20). Two API-wide majors in the 90 days to 1 November, elevated errors across ChatGPT, Codex and the API (the Agents API included) on 29 September, with Chat Completions, Responses, Batch, Realtime, Embeddings, Images, Files and the other API components degraded from 17:52 to 23:14 UTC, and elevated error rates across API models on 17 September, with eleven components degraded from 20:20 to 21:20 UTC. Two majors give 5 of 30. The 25 July incident is now outside the window. The 29 September write-up, posted on 6 October, traces it to a feature rollout that exhausted shared network connection capacity. Every other incident since 3 August that lists an API component is partial or under an hour, so minor. Degraded performance across ChatGPT, Codex and the APIs on 21 October listed every API component but ran 22 minutes (02:26 to 02:48 UTC). Single-model incidents were GPT-5.6 Sol errors on 11 September (09:08 to 11:21 UTC), `gpt-5.6-luna` errors on 21 October (70 minutes) and GPT-6.1 Sol degraded performance on Batch, Chat Completions and Responses on 27 October (78 minutes). Partial incidents were latency for some Responses requests on the US endpoint on 31 August and 1 September, image generation where some requests failed on 8 September, latency for some Responses and Chat Completions requests on 30 September, large-PDF errors in Responses and an Agents API computer use incident on 6 October, Responses errors for users in India, Japan and Korea on 22 October and errors on some GPT Image 2 edit requests on 30 October (14:35 to 18:36 UTC). Image model incidents on 16 September and 14 October and file download errors on 19 October each ran about 40 minutes. FedRAMP errors for Astra and Sol on 21 October and authentication errors near Illinois on 20 October list no API component. Rate limits published per tier and model family with rate-limit headers (15). 429 guidance, re-read on 1 November, covers `Retry-After` as a minimum wait, backoff with jitter when it's missing, a gradual ramp, and splits `slow_down` (429) from `server_is_overloaded` (503) (15). Scale Tier carries a 99.9% uptime SLA, through sales, per the 1 October check, not re-read on 1 November (10). Responses and Chat Completions are GA (10). 20 + 5 + 15 + 15 + 10 + 10 = 75.\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### Security \u0026 auth: OpenAI API +29\n\n- OpenAI API (100): Model reading. Project keys with All, Restricted (per-endpoint None, Read or Write) and Read Only permissions, service accounts, and mutual TLS with X.509 workload identity GA since 26 August, per the 1 October check. The changelog adds project key expiry dates on 10 September, key-creation controls on 15 September and, on 21 October, organisation and project settings that limit which service tiers a project may use (30). API data not used for training unless the customer opts in, since 1 March 2023 (20). Abuse-monitoring logs kept up to 30 days, and Zero Data Retention or Modified Abuse Monitoring by approval. The data-controls guide re-read on 1 November lists Chat Completions, Responses, Decisions and ten other endpoints as ZDR-eligible; `/v1/agents`, Conversations, Files and vector stores aren't (15). Usage and Costs filter by API key since 4 August, with Admin APIs to match, and audit logs for enterprise (15). SOC 2 Type 2, ISO 27001, 27017, 27018, 27701 and 42001 per the 1 October check, not re-read on 1 November, a Bugcrowd bug bounty and a coordinated disclosure policy, both linked from a signed security.txt. That security.txt had no Expires field on 27 October, which RFC 9116 requires, so the disclosure policy carries this line. It wasn't re-read on 1 November (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### Schema \u0026 documentation: OpenAI API +27\n\n- OpenAI API (100): Official OpenAPI document (openapi.yaml and openapi.json) in the openai/openai-openapi repository, whose openapi.yaml (version 2.3.0, updated 31 October) lists `gpt-6.1-terra` (25). llms.txt index with per-product files, and every docs page has a Markdown twin at `.md` (10). The reference documents each parameter, and model pages say which model fits which job (20). Structured outputs with `strict: true` on schemas and function tools (15). Error codes guide with types and recovery advice, now with a 400 `service_tier` error for tiers a project doesn't allow (15). Dated model snapshots and a dated changelog, last entry 30 October (15).\n- Tencent Cloud TokenHub (73): Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use `deepseek-v3`, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry `/v1`, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15).\n\n### Agent ergonomics: OpenAI API +15\n\n- OpenAI API (98): Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use with parallel calls and forced tool choice, 18 of 20 because GPT-6 Astra, GPT-6.1 Sol and GPT-6.1 Terra call tools only through the Responses API (18). Strict structured outputs (15). Automatic prompt caching with cached input at 0.1x on Astra and Luna ($0.01 per million on Luna) and 0.05x on GPT-6.1 Sol ($0.10) and GPT-6.1 Terra ($0.05), and a 12-hour cache lifetime in the Responses API since 20 October (15). 1.05M context on Astra, GPT-6.1 Sol, GPT-6.1 Terra and Luna (15). Batch at half price (10). Official SDKs in Python, JavaScript and more (10). Documented error codes with retry guidance (15).\n- Tencent Cloud TokenHub (83): Router, read on the model lines. Function calling is marked on most chat models in the model list, with behaviour depending on the model routed (14 of 20). Structured output is marked per model and missing on the MiniMax and Qwen models, and an unsupported `response_format` returns code 400006 (12 of 15). Cache-hit prices are published per model, Kimi K3.1 Pro lists five-minute and one-hour cache writes, and a guide covers `prompt_cache_key` and the `X-Session-ID` header for instance affinity (14 of 15). Most listed chat models have contexts of one million tokens, a judgement call since a router has no default model (15). Batch at half price covers only Hy3 and Hy4 preview, reads and writes JSONL in the customer's own COS bucket and is documented for the Guangzhou endpoint (5 of 10). No TokenHub inference SDK. The OpenAI and Anthropic SDKs work with a changed base URL, and Tencent Cloud SDK 3.0 and the `thcli` CLI cover the control plane (8 of 10). Errors return a code, English and Chinese messages, the source, the upstream code and status and a request ID, and stream errors arrive as SSE error frames (15 of 15).\n\n### Maintenance \u0026 community: OpenAI API +14\n\n- OpenAI API (87): Model reading. GPT-6 Rosalind, a life-sciences model for approved organisations, launched on 30 October, after GPT-6.1 Terra on 26 October and the Decisions API GA on 22 October (30). Published minimum notice of 6 months for GA models, 3 months for specialised variants, as little as 2 weeks for previews. On 14 October GPT-4o (`gpt-4o-2024-08-06`, `gpt-4o-2024-11-20`), GPT-4o mini, GPT-4.1 and GPT-4.1 mini were given a shutdown date of 14 January 2027, 92 days, with no safety or compliance reason stated. These are GA models, so the page's own 6-month minimum wasn't kept, as with `gpt-5.4-cyber`'s 20 days in September. 8 of 12, the award for a minimum of two to three months in practice. Five shutdown dates in the 90 days to 1 November, the Assistants API on 26 August (announced in August 2025), `gpt-5.2-chat-latest` and `gpt-5.3-chat-latest` on 10 August (announced 8 May), `gpt-3.5-turbo-instruct`, `babbage-002`, `davinci-002` and `gpt-3.5-turbo-1106` on 28 September (announced 26 September 2025, missed in the 27 October count), `gpt-5.4-cyber` on 1 October and the legacy snapshots on 23 October (announced 22 April). Sora 2 and the Videos API (24 September) are scored on the openai-sora listing. Four of the five kept the published notice, so 4 of 8 as before, as amazon-bedrock has for four dates after full notice. Dated changelog several times a month and a help centre (15 of 15). openai-python had 215 open issues per the 1 October check, replies not sampled (5 of 10). Current official SDKs, `openai` 3.42.0 on PyPI (31 October) and npm `openai` 7.47.0 (15). Supported runtimes stated, Python 3.10 or later and Node 22 or later, the npm package's `engines` re-read on 1 November (10).\n- Tencent Cloud TokenHub (73): Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q\u0026A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and `tencent-tokenhub-cli` 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10).\n\n## Score by category\n\n| Category | Weight | OpenAI API | Tencent Cloud TokenHub | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 46 | OpenAI API +29 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 100 | 73 | OpenAI API +27 |\n| Agent ergonomics | 13% (16.2 this run) | 98 | 83 | OpenAI API +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 100 | 71 | OpenAI API +29 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 35 | Tencent Cloud TokenHub +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 87 | 73 | OpenAI API +14 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 90 | 54 | OpenAI API +36 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **83.9 · A** | **59.5 · C** | |\n\n## Facts side by side\n\n| Fact | OpenAI API | Tencent Cloud TokenHub |\n| --- | --- | --- |\n| Kind | Model API | Model router |\n| Vendor | OpenAI | Tencent Cloud |\n| Hosted endpoint | `https://api.openai.com/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 | Apache-2.0 (SDKs) | Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-30 | 2026-10-24 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | couldn't be read | couldn't be read |\n| Customer content may train models | couldn't be read | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | 31k stars | 204 npm/wk |\n| Agent reviews | 3.5/5 (8) | none |\n\n## How the scores have moved\n\n### OpenAI API\n\n- +1.0 on 1 November 2026: correction\n- -0.4 on 17 October 2026: product\n- -0.2 on 8 October 2026: checklist\n\n### Tencent Cloud TokenHub\n\nNo score change since it was listed.\n\n## Verdicts\n\n**OpenAI API.** Official OpenAPI document and an llms.txt index. Elevated errors across the API for about 5 hours 20 minutes on 29 September and about 90 minutes on 17 September 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### OpenAI API\n\n1. Build on the Responses API. Astra calls tools only there\n2. Use `gpt-6-luna` for routing and extraction, `gpt-6.1-terra` for screens, images and computer use at half Sol's price, and `gpt-6.1-sol` for most work. The models page still points unsure callers to `gpt-6-astra`\n3. Move off the GPT-4o and GPT-4.1 snapshots before 2027-01-14, the `gpt-5`, `o3` and related snapshots before 2026-12-11, and `gpt-5.1`, `gpt-5.3-codex` and `gpt-5.4-nano` before 2027-04-01. Check `shutdown_date` on `GET /v1/models`\n4. Treat 429 `slow_down` as a ramp limit and 503 `server_is_overloaded` as a retry, and follow `Retry-After` when it's sent\n5. Prompts over 272K tokens cost double on input. Trim before you pay for it\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, OpenAI API or Tencent Cloud TokenHub?\n\nOpenAI API scores 83.9 (A) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing.\n\n### Do OpenAI API and Tencent Cloud TokenHub need an API key?\n\nBoth need an API key.\n\n### Can an agent call OpenAI API and Tencent Cloud TokenHub without installing anything?\n\nYes. OpenAI API has a hosted endpoint at https://api.openai.com/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/openai-api-vs-tencent-tokenhub.json, and with the fewest tokens: https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"openai-api\", \"b\": \"tencent-tokenhub\"}`. From a terminal: `anchor compare openai-api tencent-tokenhub`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/openai-api.json and https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n\n## Other comparisons with OpenAI API or Tencent Cloud TokenHub\n\n- [Claude API vs OpenAI API](https://www.anchorterminal.com/compare/anthropic-api-vs-openai-api.md)\n- [Claude API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.md)\n- [Antseed vs OpenAI API](https://www.anchorterminal.com/compare/antseed-vs-openai-api.md)\n- [BlockRun.AI vs OpenAI API](https://www.anchorterminal.com/compare/blockrun-ai-vs-openai-api.md)\n- [BlockRun.AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.md)\n- [Cerebras Inference vs OpenAI API](https://www.anchorterminal.com/compare/cerebras-inference-vs-openai-api.md)\n- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.md)\n- [Cloudflare AI Gateway vs OpenAI API](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-openai-api.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 OpenAI API](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-openai-api.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 OpenAI API](https://www.anchorterminal.com/compare/cohere-chat-vs-openai-api.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 OpenAI API](https://www.anchorterminal.com/compare/deepinfra-vs-openai-api.md)\n- [DeepInfra vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.md)\n- [DeepSeek API vs OpenAI API](https://www.anchorterminal.com/compare/deepseek-api-vs-openai-api.md)\n- [DeepSeek API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.md)\n- [Glimpse vs OpenAI API](https://www.anchorterminal.com/compare/elorian-glimpse-vs-openai-api.md)\n- [Glimpse vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.md)\n- [Fireworks AI Inference vs OpenAI API](https://www.anchorterminal.com/compare/fireworks-inference-vs-openai-api.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 OpenAI API](https://www.anchorterminal.com/compare/gemini-api-vs-openai-api.md)\n- [Gemini Developer API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.md)\n- [GroqCloud vs OpenAI API](https://www.anchorterminal.com/compare/groq-vs-openai-api.md)\n- [GroqCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.md)\n- [Jais 3 vs OpenAI API](https://www.anchorterminal.com/compare/jais-3-vs-openai-api.md)\n- [Jais 3 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.md)\n- [Meta Model API vs OpenAI API](https://www.anchorterminal.com/compare/meta-model-api-vs-openai-api.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 OpenAI API](https://www.anchorterminal.com/compare/minimax-api-vs-openai-api.md)\n- [MiniMax API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.md)\n- [Mistral AI API vs OpenAI API](https://www.anchorterminal.com/compare/mistral-api-vs-openai-api.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 OpenAI API](https://www.anchorterminal.com/compare/muse-spark-open-vs-openai-api.md)\n- [Muse Spark Open vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.md)\n- [Nemotron 3.5 Super VL vs OpenAI API](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-openai-api.md)\n- [Novita AI vs OpenAI API](https://www.anchorterminal.com/compare/novita-ai-vs-openai-api.md)\n- [Novita AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.md)\n- [OpenAI API vs OpenRouter](https://www.anchorterminal.com/compare/openai-api-vs-openrouter.md)\n- [OpenAI API vs Prism Inference](https://www.anchorterminal.com/compare/openai-api-vs-prism-inference.md)\n- [OpenAI API vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/openai-api-vs-ramp-router.md)\n- [OpenAI API vs Beam 1.0](https://www.anchorterminal.com/compare/openai-api-vs-reflection-beam.md)\n- [OpenAI API vs RouterPlus](https://www.anchorterminal.com/compare/openai-api-vs-routerplus.md)\n- [OpenAI API vs SambaCloud](https://www.anchorterminal.com/compare/openai-api-vs-sambanova.md)\n- [OpenAI API vs SiliconFlow](https://www.anchorterminal.com/compare/openai-api-vs-siliconflow.md)\n- [OpenAI API vs Simplismart](https://www.anchorterminal.com/compare/openai-api-vs-simplismart.md)\n- [OpenAI API vs StepFun API](https://www.anchorterminal.com/compare/openai-api-vs-stepfun-api.md)\n- [OpenAI API vs Together AI Inference](https://www.anchorterminal.com/compare/openai-api-vs-together-inference.md)\n- [OpenAI API vs Vercel AI Gateway](https://www.anchorterminal.com/compare/openai-api-vs-vercel-ai-gateway.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- [Tencent Cloud TokenHub vs Together AI Inference](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-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- [Antseed vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/antseed-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", "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-02", "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": "OpenAI API vs Tencent Cloud TokenHub", "url": "" } ], "description": "OpenAI scores 83.9 (A) to Tencent Cloud TokenHub's 59.5 (C) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "OpenAI API A 83.9", "Tencent Cloud TokenHub C 59.5", "scores" ], "h1": "OpenAI API vs Tencent Cloud TokenHub", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/openai-api-vs-tencent-tokenhub", "published": "2026-10-01", "section": "tools", "title": "OpenAI vs Tencent Cloud TokenHub for AI agents (2026)", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub" }, "tokens": { "markdown": 7600, "slim": 4430 }, "version": 1 }