{ "data": { "a": { "slug": "azure-openai", "name": "Azure OpenAI in Foundry Models", "vendor": "Microsoft", "vendorUrl": "https://azure.microsoft.com", "kind": "model", "category": "inference", "summary": "Microsoft Azure's hosted API for OpenAI's GPT models and other Foundry Models sold by Azure, such as DeepSeek, Llama, Mistral and Grok, called through an OpenAI-compatible v1 endpoint on each customer's Azure resource.", "url": "https://www.anchorterminal.com/tools/azure-openai", "markdownUrl": "https://www.anchorterminal.com/tools/azure-openai.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/azure-openai.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/azure-openai.json", "dns": "azure-openai.grade.anchorterminal.com", "repo": "https://github.com/Azure/azure-rest-api-specs", "license": "Proprietary service under the Microsoft Product Terms. The v1 OpenAPI spec is MIT, and the OpenAI SDKs the docs use are Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://\u003cresource\u003e.openai.azure.com/openai/v1", "packages": [ { "registry": "pypi", "name": "openai" }, { "registry": "npm", "name": "openai" }, { "registry": "npm", "name": "@azure/openai" } ], "auth": "mixed", "authNotes": "`api-key` header with one of the resource's two regenerable keys, or a Microsoft Entra ID bearer token (scope https://ai.azure.com/.default) with the Cognitive Services OpenAI User role. Key authentication can be disabled per resource (`disableLocalAuth`). Each model must be deployed in the resource before it can be called, by deployment name.", "pricing": "usage", "pricingNotes": "Pay per token on an Azure subscription. Global Standard GPT-6 and GPT-6.1 prices match OpenAI's list (GPT-6.1 Sol $2/$10, GPT-6.1 Terra $1/$5 per million tokens), Data Zone costs 10% more, long-context requests cost 2x input and 1.5x output, cached input 0.1x, cache writes 1.25x, Flex half price and priority processing 2x (GPT-6 Sol). Batch is 50% off Global Standard. Provisioned throughput is billed per PTU hour. Prices from the Azure Retail Prices API, because the pricing page fills its table with JavaScript (checked 2026-11-06).", "priceSummary": "from $0.10 / 1M in", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Foundry docs, the v1 OpenAPI spec or the pricing page. Access needs an Azure subscription with a payment method (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 454039, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://learn.microsoft.com/en-us/azure/foundry/openai/", "rateLimitsUrl": "https://learn.microsoft.com/en-us/azure/foundry/openai/quotas-limits", "openapi": "https://github.com/Azure/azure-rest-api-specs/blob/main/specification/ai/data-plane/OpenAI.v1/azure-v1-v1-generated.json", "capabilities": [ "inference.llm", "inference.open-weights" ], "tags": [ "official", "hosted", "model", "card-required", "openapi", "openai-compatible", "closed-source", "enterprise", "eu", "python", "typescript", "status-page", "bug-bounty" ], "lastRelease": "2026-10-26", "graded": true, "anchor": { "graded": true, "score": 80, "grade": "A", "agentReady": true, "rank": 14, "ranked": true, "rankOf": 1486, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 98, "maintenance": 86, "payments": 20, "reliability": 80, "schema": 87, "security": 95, "transparency": 83 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "An OpenAI-compatible v1 API with a public OpenAPI spec, Entra ID roles in place of shared keys and FedRAMP High scope, with GPT-6 and GPT-6.1 at OpenAI's list prices on Global Standard. Access needs an Azure subscription with a card and a deployment per model, and a 29 September 2026 incident caused about six hours of failures in Sweden Central.", "bestFor": "Teams on Azure that need OpenAI models with Entra ID, private networking, EU or US data zones or FedRAMP scope, and one resource that also serves DeepSeek, Llama, Mistral and Grok models.", "strengths": [ "Public OpenAPI 3.2 spec for the v1 API, 71 paths covering Responses, Chat Completions, batches, files and vector stores", "Microsoft Entra ID tokens with Azure roles, and key authentication can be switched off per resource", "GA models carry a retirement date 18 months after launch, set at release and readable through the Models API", "Data Zone deployments keep processing inside the EU or US, and Azure OpenAI is in FedRAMP High scope", "GPT-6 Astra, Sol and Luna at $10/$50, $2/$10 and $0.10/$0.50 per million tokens on Global Standard" ], "weaknesses": [ "Intermittent failures and 5xx errors in Sweden Central for about six hours on 29 September 2026", "An Azure subscription with a card, a resource and a model deployment come before the first call", "No llms.txt, and no Azure OpenAI what's new page was found; the Foundry one still covered August on 6 November", "No retention period stated for prompts kept for human abuse review, and Responses data is kept 30 days by default", "The retirement schedule lists two `gpt-realtime-mini` versions twice with different retirement dates, and no GPT-6 retirement dates yet" ], "agentNotes": [ "Point the OpenAI SDK at https://\u003cresource\u003e.openai.azure.com/openai/v1/ and pass the deployment name as `model`, not the model id", "Prefer Entra ID with the Cognitive Services OpenAI User role over the resource key, which opens the whole data plane", "On 429 wait for `retry-after-ms`, then back off with jitter. The OpenAI SDK retries twice by default", "Set `store: false` on Responses calls you don't need kept. Stored responses persist 30 days by default", "Keep remote MCP approvals on for servers you don't control. They're required by default" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "A", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 80 } ], "editorialScores": { "ergonomics": 98, "maintenance": 86, "payments": 20, "reliability": 80, "schema": 87, "security": 95, "transparency": 77 }, "provenanceScore": 88, "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 openai azure-identity # or: npm i openai @azure/identity", "http": "curl \"https://$AZURE_OPENAI_RESOURCE.openai.azure.com/openai/v1/responses\" \\\n -H \"api-key: $AZURE_OPENAI_API_KEY\" -H \"content-type: application/json\" \\\n -d '{\"model\":\"\u003cyour-deployment-name\u003e\",\"input\":\"hello\"}'" }, "letme": { "capability": "https://letme.dev/inference.llm", "tool": "https://letme.dev/azure-openai" }, "sameCompany": [ "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-key-vault", "bing-grounding", "azure-document-intelligence", "azure-devops-mcp", "microsoft-learn-mcp", "tokeneconomizer", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "azure-blob-storage", "onedrive-sharepoint", "microsoft-teams", "dynamics-365-sales", "copilot-studio-mcp", "power-automate", "foundry-local", "microsoft-decision-1", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph", "microsoft-graph-people", "mage-vl-cowork" ], "area": "models", "unitPrices": [ { "item": "GPT-6.1 Sol input, Global Standard", "unit": "1m-tokens", "usd": 2, "note": "short context, Retail Prices API meter effective 2026-10-01" }, { "item": "GPT-6.1 Sol output, Global Standard", "unit": "1m-tokens", "usd": 10, "note": "short context" }, { "item": "GPT-6.1 Terra input, Global Standard", "unit": "1m-tokens", "usd": 1, "note": "short context" }, { "item": "GPT-6.1 Terra output, Global Standard", "unit": "1m-tokens", "usd": 5, "note": "short context" }, { "item": "GPT-6 Astra input, Global Standard", "unit": "1m-tokens", "usd": 10, "note": "short context" }, { "item": "GPT-6 Astra output, Global Standard", "unit": "1m-tokens", "usd": 50, "note": "short context" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "domainNote": "Endpoints are on openai.azure.com and cognitiveservices.azure.com. microsoft.com publishes a security.txt, but it passed its Expires date on 2026-09-23 and was still expired on 2026-11-06.", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/licensing/terms/product/ForOnlineServices/all", "privacy": "https://privacy.microsoft.com/en-us/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "https://learn.microsoft.com/en-us/azure/foundry/whats-new-foundry", "securityTxt": "expired", "checked": "2026-11-06", "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/azure-openai.json", "live": { "slug": "azure-openai", "probe": { "target": "https://\u003cresource\u003e.openai.azure.com/openai/v1", "method": "get", "lastAt": "2026-11-07T18:07:43.010540289Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "DNS lookup failed", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 198, "samples30d": 198, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 0 }, { "date": "2026-11-07", "probes": 185, "ok": 0 } ], "outages": [ { "start": "2026-11-06T22:45:05.888142257Z", "end": "0001-01-01T00:00:00Z", "note": "DNS lookup failed" } ] }, "versions": [ { "registry": "npm", "name": "@azure/openai", "version": "2.0.0", "seenAt": "2026-11-06T23:09:28.988578937Z" }, { "registry": "npm", "name": "openai", "version": "7.53.0", "seenAt": "2026-11-06T23:09:28.954764315Z" }, { "registry": "pypi", "name": "openai", "version": "3.46.0", "released": "2026-11-05", "seenAt": "2026-11-06T23:09:28.844701934Z" } ], "githubStars": 3113, "npmWeekly": 56543040, "pypiWeekly": 91156146, "securityTxt": { "url": "https://microsoft.com/.well-known/security.txt", "state": "valid", "expires": "2027-10-27T16:00:00.000Z", "checkedAt": "2026-11-07T16:02:01.196666056Z" }, "pages": [ { "url": "https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirement-schedule", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:13:01.613678733Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "51438ff38076" } ], "updatedAt": "2026-11-07T18:07:43.010540289Z" } }, "answer": "Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 6 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing.", "b": { "slug": "tencent-tokenhub", "name": "Tencent Cloud TokenHub", "vendor": "Tencent Cloud", "vendorUrl": "https://cloud.tencent.com", "kind": "router", "category": "inference", "summary": "Tencent Cloud TokenHub is a hosted model gateway serving Tencent's Hy models and third-party models such as DeepSeek, Kimi, GLM and MiniMax through OpenAI-compatible and Anthropic-compatible endpoints in Guangzhou and Singapore, with per-key scopes and quotas.", "url": "https://www.anchorterminal.com/tools/tencent-tokenhub", "markdownUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json", "dns": "tencent-tokenhub.grade.anchorterminal.com", "repo": "https://github.com/TencentCloud/THCLI", "license": "Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://tokenhub.tencentmaas.com/v1", "packages": [ { "registry": "npm", "name": "tencent-tokenhub-cli" } ], "auth": "api-key", "authNotes": "Bearer API key from the TokenHub console, or `x-api-key` on the Anthropic-style `/v1/messages`. Keys are long-lived, belong to one region (Guangzhou or Singapore), can be limited to chosen models and inference services, up to 200 IP ranges and token quotas, and can be disabled or deleted. They can also be created through the CreateApiKey control-plane call with signed Tencent Cloud credentials, or by `thcli auth login`. The account needs real-name verification first.", "pricing": "usage", "pricingNotes": "Pay per token in CNY, billed hourly. Hy4 preview costs 6 CNY in, 18 CNY out and 0.3 CNY cached per 1M tokens, Hy3 1, 4 and 0.25 CNY. DeepSeek models double at weekday peak hours. Batch is half price for Hy3 and Hy4 preview. Each account gets 1M free tokens per language model for a year, in a campaign to 31 December 2026. Token Plan subscriptions run from 28 to 599 CNY a month (https://cloud.tencent.com/document/product/1823/130055, checked 2026-11-01).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs table of contents, the billing pages or the API usage page. Payment is from a Tencent Cloud account balance, billed hourly (checked 2026-11-01).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 204, "pypiWeekly": null, "asOf": "2026-11-01" }, "docsUrl": "https://cloud.tencent.com/document/product/1823/130058", "rateLimitsUrl": "https://cloud.tencent.com/document/product/1823/136028", "llmsTxt": "https://cloud.tencent.com/document/product/1823/llms.txt", "capabilities": [ "inference.router", "inference.llm", "inference.open-weights", "embed.text", "embed.multimodal", "image.generate", "video.generate", "speech.tts", "speech.stt", "audio.music", "translate.text", "web.search", "obs.gateway" ], "tags": [ "hosted", "router", "usage-based", "free-credit", "openai-compatible", "anthropic-compatible", "llms-txt", "cli", "sla", "batch", "bug-bounty", "no-status-page", "regional-endpoints", "singapore", "chinese", "subscription" ], "lastRelease": "2026-10-24", "graded": true, "anchor": { "graded": true, "score": 59.5, "grade": "C", "agentReady": false, "rank": 700, "ranked": true, "rankOf": 1486, "categoryRank": 24, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 73, "payments": 35, "reliability": 46, "schema": 73, "security": 71, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -3, "negativeNotes": [ "2026-10-17. -3, a breaking change without notice. DeepSeek-V4.1-Flash (directly supplied) was moved to its 1017 version under the same model ids and prices on 17 October 2026, and the notice came two days later (https://cloud.tencent.com/announce/detail/2516). Callers pinned to the id got a different model's behaviour with no warning. One term at the floor: the API didn't change. The founder's decision, 1 November 2026." ], "verdict": "Keys can be limited to chosen models, source IPs and token quotas, errors name their source and code, and a 99.5% SLA covers paid use of models Tencent runs. Sign-up needs a Tencent Cloud account with real-name verification, prices are in CNY, no public status page was found, and 18 model retirement notices ran from April to October 2026.", "bestFor": "Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing.", "strengths": [ "API keys can be limited to chosen models and inference services, up to 200 source IP ranges, and daily, monthly or total token quotas", "One base URL answers OpenAI Chat Completions, OpenAI Responses and Anthropic Messages calls, and `GET /v1/models` marks models due to retire as `pre-offline`", "Error bodies carry a six-digit code, English and Chinese messages, the source (client, gateway or upstream) and a request ID, and 429s can carry `Retry-After`", "A published SLA promises 99.5% monthly availability with voucher credits of 10 to 50 per cent of the month's fee, for paid use of models Tencent runs", "Per-call audit logs (request ID, key, client IP, status, tokens, latency) can be delivered to the customer's own Tencent Cloud CLS log service" ], "weaknesses": [ "Sign-up needs a Tencent Cloud account with real-name verification. The international site answered with a bot check, so access from outside China was not established", "No public status page was found. A four-hour outage of DeepSeek's directly supplied models on 15 October 2026 appears only as a compensation notice", "18 model retirement notices from 21 April to 22 October 2026. Those read gave 21 to 33 days, and eligible callers are switched to a successor at its price", "DeepSeek's directly supplied models send inputs to DeepSeek under its own terms, and the TokenHub SLA does not cover them", "Per-model RPM and TPM limits for chat models are shown in the console and the quota API, not in the public docs" ], "agentNotes": [ "Use `https://tokenhub.tencentmaas.com/v1` with keys made for Guangzhou and `https://tokenhub-intl.tencentmaas.com/v1` with keys made for Singapore. Keys do not work across the two", "Send the key as `Authorization: Bearer` on the OpenAI paths and as `x-api-key` on `/v1/messages`", "Parse `error.code` as a string or a number, since 429 codes can come back as integers, and wait for `Retry-After` before retrying", "Take model ids from `GET /v1/models` and watch for `pre-offline`. The quickstart's `deepseek-v3` example is not in the current model list", "Expect DeepSeek prices to double on weekdays from 9am to noon and 2pm to 6pm Beijing time, when the peak rate applies" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.5 } ], "editorialScores": { "ergonomics": 83, "maintenance": 73, "payments": 35, "reliability": 46, "schema": 73, "security": 71, "transparency": 59 }, "provenanceScore": 49, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm i -g tencent-tokenhub-cli", "http": "curl https://tokenhub.tencentmaas.com/v1/models \\\n -H \"Authorization: Bearer $TOKENHUB_API_KEY\"", "claudeCode": "{\n \"env\": {\n \"ANTHROPIC_BASE_URL\": \"https://tokenhub.tencentmaas.com\",\n \"ANTHROPIC_AUTH_TOKEN\": \"YOUR_API_KEY\",\n \"ANTHROPIC_MODEL\": \"hy3\"\n }\n}" }, "letme": { "capability": "https://letme.dev/inference.router", "tool": "https://letme.dev/tencent-tokenhub" }, "area": "models", "provenance": { "legalEntity": "Tencent Cloud Computing (Beijing) Co., Ltd. (腾讯云计算（北京）有限责任公司)", "domain": "tencentmaas.com", "domainRegistered": "2026-03-13", "endpointOnVendorDomain": false, "terms": "https://cloud.tencent.com/document/product/301/129852", "privacy": "https://privacy.qq.com/document/preview/91d5fd3c98ce4468ae462ac59233bba2", "statusPage": "", "changelog": "https://cloud.tencent.com/document/product/1823/130675", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "The TokenHub Terms of Service (effective 14 September 2026), the SLA (effective 23 April 2026) and the special note on third-party deployed models (effective 14 September 2026) name 腾讯云计算（北京）有限责任公司. The docs footer also names 深圳市腾讯计算机系统有限公司 as ICP licence holder.", "The TokenHub privacy policy is linked from the docs to privacy.qq.com, which renders only with JavaScript, so it was not read. privacy.qq.com has no robots.txt (404).", "No public status page was found. status.cloud.tencent.com did not answer, and the Tencent Cloud health dashboard documentation answered with a bot check.", "security.txt answered 404 on cloud.tencent.com, www.tencent.com and tokenhub.tencentmaas.com. Tencent's bug bounty policy at en.security.tencent.com lists Tencent Cloud in scope.", "RDAP at Verisign gives tencentmaas.com a registration date of 13 March 2026 with no registrant. The API answers at tokenhub.tencentmaas.com and tokenhub-intl.tencentmaas.com, named in Tencent Cloud's API usage page.", "cloud.tencent.com allows these docs in robots.txt. Its pages answered some requests with a JavaScript bot check, which was not passed. The pages were read when a later plain request returned them. www.tencentcloud.com answered robots.txt with a bot check, so the international site was not read." ], "score": 49 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.json", "live": { "slug": "tencent-tokenhub", "probe": { "target": "https://tokenhub.tencentmaas.com/v1", "method": "get", "lastAt": "2026-11-07T18:08:23.490340286Z", "lastOk": true, "lastStatus": 404, "lastMs": 821, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 839, "p95ms24h": 1161, "samples24h": 239, "samples30d": 1373, "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": 185, "ok": 185 } ] }, "versions": [ { "registry": "npm", "name": "tencent-tokenhub-cli", "version": "1.0.2", "seenAt": "2026-11-07T00:10:56.11915484Z" } ], "githubStars": 12, "npmWeekly": 563, "securityTxt": { "url": "https://tencentmaas.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-07T16:00:51.946401273Z" }, "llmsTxt": { "url": "https://cloud.tencent.com/document/product/1823/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:07.341361344Z" }, "pages": [ { "url": "https://cloud.tencent.com/document/product/1823/130675", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:01:36.805781891Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2287", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:20.295617745Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2469", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:22.306047727Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2496", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:24.307216514Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2511", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:26.305052043Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2516", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:28.308079433Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2524", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:30.306693329Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/announce/detail/2538", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:01:34.709118103Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://privacy.qq.com/document/preview/91d5fd3c98ce4468ae462ac59233bba2", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:17:28.357626414Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://cloud.tencent.com/document/product/301/129852", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:01:36.816423311Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" } ], "github": { "repo": "tencentcloud/thcli", "checkedAt": "2026-11-02T08:23:47.915102454Z", "stars": 12, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-30T06:58:13Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 4 }, "updatedAt": "2026-11-07T18:08:23.490340286Z" } }, "edges": [ { "by": 34, "category": "reliability", "leads": "azure-openai", "name": "Reliability", "reasons": { "a": "Azure status page with post-incident reviews, listing Azure OpenAI Service, Foundry Models and Foundry Agent Service as components (20). One incident in the 90 days to 6 November 2026 names Azure OpenAI, and no review after it does, intermittent request failures, higher latency and HTTP 5xx errors in Sweden Central from 10:03 to 15:58 UTC on 29 September 2026 (tracking 7QL5-Z50), counted as one major outage as in the Foundry fine-tuning dossier. The 23 July West US review and the 30 September gateway incident don't name it (10). Quota tiers from Free to Tier 6 with TPM and RPM per model and deployment type, 1,000 RPM and 1,000,000 TPM for each GPT-6 model on Global Standard at Tier 1 (15). 429 responses carry `retry-after-ms`, every response carries `x-ratelimit-*` headers, and the quota guide gives exponential backoff with jitter and SDK retry settings (15). The models page says models sold by Azure are covered by Azure service-level agreements and links the Online Services SLA. The consolidated SLA document wouldn't download on 6 October and wasn't retried on 6 November, so the clause rests on Microsoft's docs, read the same way as the 5 October Azure Speech check (10). The v1 API is GA and the GPT-6 models carry no preview label (10).", "b": "Hosted reading. No public status page was found. status.cloud.tencent.com did not answer and the Tencent Cloud health dashboard documentation answered with a bot check (0). With no page there is no incident record to read (5 of 30). The announcements carry one incident, DeepSeek's directly supplied models unavailable from 9:06 to 13:04 Beijing time on 15 October 2026 after a fault at DeepSeek, compensated with vouchers. Rate limits are per model, shown in the console and returned by DescribeModelQuota. The public docs give numbers only for batch jobs (20 created a minute, 10 active), image models (5 concurrent) and DeepSeek V4 Flash and Pro (2,500 and 500 concurrent), with the rules for self-serve increases (8 of 15). Six 429 codes separate RPM, TPM, TPD, concurrency and upstream capacity, 429s may carry `Retry-After` and the docs advise exponential backoff. No idempotency guidance, though inference calls are not writes (13 of 15). The TokenHub SLA promises 99.5% monthly availability with vouchers of 10, 25 or 50 per cent of the month's fee. It excludes free use and third-party deployed models such as DeepSeek's directly supplied ones (10). Generally available since 7 April 2026, with some models marked preview (10)." }, "scores": { "a": 80, "b": 46 } }, { "by": 29, "category": "transparency", "leads": "azure-openai", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under the Microsoft Product Terms, with the v1 spec under MIT and the OpenAI SDKs under Apache-2.0 (15). The data privacy page agrees with the product terms on no training and states where data is processed and stored by deployment type, but gives no retention period for the human-review store and sits beside a 30-day default for Responses data (24 of 30). A published lifecycle policy and a retirement schedule with dates and replacements, but on 6 November the schedule listed `gpt-realtime-mini` 2025-10-06 and 2025-12-15 twice each with different retirement dates, and no GPT-6 model yet (18 of 20, down from 20). Data locations stated for Standard, Data Zone and Global deployments, and a public sub-processor list per the 5 October Azure Speech check, not re-read (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": 83, "b": 54 } }, { "by": 24, "category": "security", "leads": "azure-openai", "name": "Security \u0026 auth", "reasons": { "a": "Model reading. Microsoft Entra ID tokens with Azure roles (the Cognitive Services OpenAI User role for calls), managed identities, and key authentication that can be disabled per resource, or two regenerable resource keys in the `api-key` header. No documented route puts the key in a URL query string (30). Prompts, completions, embeddings and training data aren't used to train foundation models without the customer's permission or instruction, per the data privacy page updated 4 August 2026 (20). Flagged prompts and completions may be stored in the customer's geography for human abuse review, with no retention period stated, and approved customers can turn that storage off through modified abuse monitoring. Responses API data is kept 30 days by default unless `store` is false (12 of 15). Azure Monitor resource logs and the subscription activity log, as read in the Foundry fine-tuning dossier (15). MSRC coordinated disclosure policy and Microsoft's bounty programme, both named in microsoft.com's security.txt, and Azure OpenAI is listed in FedRAMP High and DoD IL2 scope in Azure public regions. The security.txt passed its Expires date on 2026-09-23 and was still expired on 6 November, which the Bedrock and S3 dossiers mark down by 2, applied here too (18 of 20, down from 20 on 6 October for consistency).", "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": 95, "b": 71 } }, { "by": 15, "category": "ergonomics", "leads": "azure-openai", "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 a forced call by naming the function in `tool_choice`, 18 of 20 because `gpt-6.1-sol` calls tools only through the Responses API (18). Strict structured outputs (15). Prompt caching from 1,024 tokens, cached input at 0.1x on GPT-6 ($1 per million on Astra) and cache writes at 1.25x from GPT-5.6 on, with explicit breakpoints (15). 1,050,000-token context on GPT-6 and GPT-6.1, input capped at 922,000 (15). Batch at 50% off Global Standard with a 24-hour target (10). The docs use OpenAI's own SDKs for Python, JavaScript, C#, Go and Java against the v1 endpoint (10). 429 and quota errors documented with retry headers (15). Calls name a deployment rather than a model, so each model must be deployed in the resource first, which the model checklist doesn't score.", "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": 15, "category": "payments", "leads": "tencent-tokenhub", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-1M-token prices are public in the Azure Retail Prices API without a login, while the pricing page fills its table with JavaScript and showed GPT-6 prices as pending on 6 October (20). The quota tiers include a Free tier, but an Azure subscription needs a payment method (0). A person signs up for Azure in a browser and creates a resource and a deployment before the first call (0).", "b": "No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by `thcli auth login`, but only from that account (0)." }, "scores": { "a": 20, "b": 35 } }, { "by": 14, "category": "schema", "leads": "azure-openai", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.2 spec for the v1 data plane in Azure/azure-rest-api-specs (`azure-v1-v1-generated.json`, 71 paths and 852 schemas), linked from the v1 API page (25). No llms.txt at learn.microsoft.com (404). Learn pages offer Copy Markdown and the Markdown sources are public in MicrosoftDocs/azure-ai-docs, last merged 5 October (5 of 10). The models page lists each model's capabilities, context and API support, but the model choice guide, dated 19 May 2026, doesn't cover GPT-6 (15 of 20). Structured outputs with `strict: true` on schemas and function tools, though not together with parallel function calls (15). Examples in Python, C#, JavaScript, Go, Java and REST, and an error table on the quotas page with a fix for 429 and other codes (15). The v1 path replaces monthly `api-version` values, with preview capabilities opted into by header, a dated API version changelog and dated model versions. On 6 November the Foundry what's new still covered August, though updated on 5 November, and no Azure OpenAI what's new was found at learn.microsoft.com/en-us/azure/foundry/openai/whats-new, which answered 404 (12 of 15).", "b": "Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use `deepseek-v3`, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry `/v1`, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15)." }, "scores": { "a": 87, "b": 73 } } ], "facts": [ { "a": "Model API", "b": "Model router", "name": "Kind" }, { "a": "Microsoft", "b": "Tencent Cloud", "name": "Vendor" }, { "a": "https://\u003cresource\u003e.openai.azure.com/openai/v1", "b": "https://tokenhub.tencentmaas.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Microsoft Product Terms. The v1 OpenAPI spec is MIT, and the OpenAI SDKs the docs use are Apache-2.0", "b": "Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-26", "b": "2026-10-24", "name": "Last release" }, { "a": "no date given", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "454k npm/wk", "b": "204 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Azure OpenAI in Foundry Models scores 80 (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, Azure OpenAI in Foundry Models or Tencent Cloud TokenHub?" }, { "answer": "Azure OpenAI in Foundry Models takes an API key or an OAuth sign-in. Tencent Cloud TokenHub needs an API key.", "question": "Do Azure OpenAI in Foundry Models and Tencent Cloud TokenHub need an API key?" }, { "answer": "Yes. Azure OpenAI in Foundry Models has a hosted endpoint at https://\u003cresource\u003e.openai.azure.com/openai/v1 and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.", "question": "Can an agent call Azure OpenAI in Foundry Models and Tencent Cloud TokenHub without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 46", "Schema \u0026 documentation, 87 against 73", "Agent ergonomics, 98 against 83", "Security \u0026 auth, 95 against 71", "Maintenance \u0026 community, 86 against 73", "Transparency \u0026 trust, 83 against 54" ], "also": [ "Agent-ready, a grade of BB or better", "No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them" ], "goodFor": "Teams on Azure that need OpenAI models with Entra ID, private networking, EU or US data zones or FedRAMP scope, and one resource that also serves DeepSeek, Llama, Mistral and Grok models.", "slug": "azure-openai", "watchFor": "Intermittent failures and 5xx errors in Sweden Central for about six hours on 29 September 2026" }, { "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" } ], "history": null, "job": { "capability": "inference.llm", "name": "LLM inference" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-azure-openai.json", "title": "Amazon Bedrock vs Azure OpenAI in Foundry Models", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-azure-openai" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub.json", "title": "Amazon Bedrock vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-azure-openai.json", "title": "Claude API vs Azure OpenAI in Foundry Models", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-azure-openai" }, { "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-azure-openai.json", "title": "Antseed vs Azure OpenAI in Foundry Models", "url": "https://www.anchorterminal.com/compare/antseed-vs-azure-openai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-blockrun-ai.json", "title": "Azure OpenAI in Foundry Models vs BlockRun.AI", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-blockrun-ai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-cerebras-inference.json", "title": "Azure OpenAI in Foundry Models vs Cerebras Inference", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-cerebras-inference" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-ai-gateway.json", "title": "Azure OpenAI in Foundry Models vs Cloudflare AI Gateway", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-ai-gateway" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-workers-ai.json", "title": "Azure OpenAI in Foundry Models vs Cloudflare Workers AI", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-workers-ai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-cohere-chat.json", "title": "Azure OpenAI in Foundry Models vs Cohere Chat API (Command models)", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-cohere-chat" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-deepinfra.json", "title": "Azure OpenAI in Foundry Models vs DeepInfra", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-deepinfra" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-deepseek-api.json", "title": "Azure OpenAI in Foundry Models vs DeepSeek API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-deepseek-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-eden-ai.json", "title": "Azure OpenAI in Foundry Models vs Eden AI", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-eden-ai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-elorian-glimpse.json", "title": "Azure OpenAI in Foundry Models vs Glimpse", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-fireworks-inference.json", "title": "Azure OpenAI in Foundry Models vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-fireworks-inference" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-gemini-api.json", "title": "Azure OpenAI in Foundry Models vs Gemini Developer API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-gemini-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-groq.json", "title": "Azure OpenAI in Foundry Models vs GroqCloud", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-groq" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-hugging-face-inference-providers.json", "title": "Azure OpenAI in Foundry Models vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-hugging-face-inference-providers" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-inkling-2-small.json", "title": "Azure OpenAI in Foundry Models vs Inkling 2 Small", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-inkling-2-small" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-jais-3.json", "title": "Azure OpenAI in Foundry Models vs Jais 3", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-jais-3" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-meta-model-api.json", "title": "Azure OpenAI in Foundry Models vs Meta Model API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-meta-model-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-minimax-api.json", "title": "Azure OpenAI in Foundry Models vs MiniMax API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-minimax-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-mistral-api.json", "title": "Azure OpenAI in Foundry Models vs Mistral AI API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-mistral-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-muse-spark-open.json", "title": "Azure OpenAI in Foundry Models vs Muse Spark Open", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-muse-spark-open" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-nemotron-3-5-super-vl.json", "title": "Azure OpenAI in Foundry Models vs Nemotron 3.5 Super VL", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-nemotron-3-5-super-vl" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-novita-ai.json", "title": "Azure OpenAI in Foundry Models vs Novita AI", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-novita-ai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-openai-api.json", "title": "Azure OpenAI in Foundry Models vs OpenAI API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-openai-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-openrouter.json", "title": "Azure OpenAI in Foundry Models vs OpenRouter", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-openrouter" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-prism-inference.json", "title": "Azure OpenAI in Foundry Models vs Prism Inference", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-prism-inference" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-ramp-router.json", "title": "Azure OpenAI in Foundry Models vs Router.com (Ramp Router)", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-ramp-router" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-reflection-beam.json", "title": "Azure OpenAI in Foundry Models vs Beam 1.0", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-reflection-beam" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-routerplus.json", "title": "Azure OpenAI in Foundry Models vs RouterPlus", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-sambanova.json", "title": "Azure OpenAI in Foundry Models vs SambaCloud", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-sambanova" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-siliconflow.json", "title": "Azure OpenAI in Foundry Models vs SiliconFlow", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-siliconflow" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-simplismart.json", "title": "Azure OpenAI in Foundry Models vs Simplismart", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api.json", "title": "Azure OpenAI in Foundry Models vs StepFun API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-swe-2-flash.json", "title": "Azure OpenAI in Foundry Models vs SWE-2 Flash", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-swe-2-flash" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-together-inference.json", "title": "Azure OpenAI in Foundry Models vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-vercel-ai-gateway.json", "title": "Azure OpenAI in Foundry Models vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-vercel-ai-gateway" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-vertex-ai.json", "title": "Azure OpenAI in Foundry Models vs Vertex AI (Gemini Enterprise Agent Platform)", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-vertex-ai" }, { "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/cerebras-inference-vs-tencent-tokenhub.json", "title": "Cerebras Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub.json", "title": "Cloudflare AI Gateway vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub.json", "title": "Cloudflare Workers AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.json", "title": "Cohere Chat API (Command models) vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.json", "title": "DeepInfra vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.json", "title": "DeepSeek API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.json", "title": "Glimpse vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.json", "title": "Fireworks AI Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.json", "title": "Gemini Developer API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.json", "title": "GroqCloud vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/inkling-2-small-vs-tencent-tokenhub.json", "title": "Inkling 2 Small vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/inkling-2-small-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.json", "title": "Jais 3 vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.json", "title": "Meta Model API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.json", "title": "MiniMax API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.json", "title": "Mistral AI API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.json", "title": "Muse Spark Open vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.json", "title": "Novita AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.json", "title": "OpenAI API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.json", "title": "OpenRouter vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.json", "title": "Beam 1.0 vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.json", "title": "SambaCloud vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.json", "title": "SiliconFlow vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.json", "title": "Simplismart vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.json", "title": "StepFun API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/swe-2-flash-vs-tencent-tokenhub.json", "title": "SWE-2 Flash vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/swe-2-flash-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.json", "title": "Tencent Cloud TokenHub vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vertex-ai.json", "title": "Tencent Cloud TokenHub vs Vertex AI (Gemini Enterprise Agent Platform)", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vertex-ai" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api.json", "title": "Tencent Cloud TokenHub vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.json", "title": "Antseed vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/eden-ai-vs-tencent-tokenhub.json", "title": "Eden AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/eden-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.json", "title": "Hugging Face Inference Providers vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/litellm-vs-tencent-tokenhub.json", "title": "LiteLLM vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/litellm-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.json", "title": "Router.com (Ramp Router) vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.json", "title": "RouterPlus vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.json", "title": "Tencent Cloud TokenHub vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway" }, { "json": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub.json", "title": "Nemotron 3.5 Super VL vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.json", "title": "Prism Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub" } ], "panel": null, "scores": [ { "azure-openai": 80, "by": 34, "edge": "azure-openai", "key": "reliability", "name": "Reliability", "tencent-tokenhub": 46, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "azure-openai": 87, "by": 14, "edge": "azure-openai", "key": "schema", "name": "Schema \u0026 documentation", "tencent-tokenhub": 73, "weight": 13 }, { "azure-openai": 98, "by": 15, "edge": "azure-openai", "key": "ergonomics", "name": "Agent ergonomics", "tencent-tokenhub": 83, "weight": 13 }, { "azure-openai": 95, "by": 24, "edge": "azure-openai", "key": "security", "name": "Security \u0026 auth", "tencent-tokenhub": 71, "weight": 14 }, { "azure-openai": 20, "by": 15, "edge": "tencent-tokenhub", "key": "payments", "name": "Payments \u0026 pricing", "tencent-tokenhub": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "azure-openai": 86, "by": 13, "edge": "azure-openai", "key": "maintenance", "name": "Maintenance \u0026 community", "tencent-tokenhub": 73, "weight": 7 }, { "azure-openai": 83, "by": 29, "edge": "azure-openai", "key": "transparency", "name": "Transparency \u0026 trust", "tencent-tokenhub": 54, "weight": 7 } ], "summary": "Azure OpenAI in Foundry Models scores 80 (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": { "azure-openai": "An OpenAI-compatible v1 API with a public OpenAPI spec, Entra ID roles in place of shared keys and FedRAMP High scope, with GPT-6 and GPT-6.1 at OpenAI's list prices on Global Standard. Access needs an Azure subscription with a card and a deployment per model, and a 29 September 2026 incident caused about six hours of failures in Sweden Central.", "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/azure-openai-vs-tencent-tokenhub", "json": "https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub.min.md" }, "markdown": "Azure OpenAI in Foundry Models scores 80 (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- Azure OpenAI in Foundry Models: grade A, 80/100, rank #14 of 1486. Markdown https://www.anchorterminal.com/tools/azure-openai.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-openai.json\n- Tencent Cloud TokenHub: grade C, 59.5/100, rank #700 of 1486. Markdown https://www.anchorterminal.com/tools/tencent-tokenhub.md · JSON https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n- Best model APIs and inference for AI agents: https://www.anchorterminal.com/best/inference/index.md\n- All 830 models comparisons: https://www.anchorterminal.com/compare/inference/index.md\n\n## Which one, for what\n\n### Azure OpenAI in Foundry Models (A)\n\nGood for: Teams on Azure that need OpenAI models with Entra ID, private networking, EU or US data zones or FedRAMP scope, and one resource that also serves DeepSeek, Llama, Mistral and Grok models.\n\nAhead on:\n- Reliability, 80 against 46\n- Schema \u0026 documentation, 87 against 73\n- Agent ergonomics, 98 against 83\n- Security \u0026 auth, 95 against 71\n- Maintenance \u0026 community, 86 against 73\n- Transparency \u0026 trust, 83 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: Intermittent failures and 5xx errors in Sweden Central for about six hours on 29 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 20\n\nWatch for: Sign-up needs a Tencent Cloud account with real-name verification. The international site answered with a bot check, so access from outside China was not established\n\n\n## Why the edge\n\n### Reliability: Azure OpenAI in Foundry Models +34\n\n- Azure OpenAI in Foundry Models (80): Azure status page with post-incident reviews, listing Azure OpenAI Service, Foundry Models and Foundry Agent Service as components (20). One incident in the 90 days to 6 November 2026 names Azure OpenAI, and no review after it does, intermittent request failures, higher latency and HTTP 5xx errors in Sweden Central from 10:03 to 15:58 UTC on 29 September 2026 (tracking 7QL5-Z50), counted as one major outage as in the Foundry fine-tuning dossier. The 23 July West US review and the 30 September gateway incident don't name it (10). Quota tiers from Free to Tier 6 with TPM and RPM per model and deployment type, 1,000 RPM and 1,000,000 TPM for each GPT-6 model on Global Standard at Tier 1 (15). 429 responses carry `retry-after-ms`, every response carries `x-ratelimit-*` headers, and the quota guide gives exponential backoff with jitter and SDK retry settings (15). The models page says models sold by Azure are covered by Azure service-level agreements and links the Online Services SLA. The consolidated SLA document wouldn't download on 6 October and wasn't retried on 6 November, so the clause rests on Microsoft's docs, read the same way as the 5 October Azure Speech check (10). The v1 API is GA and the GPT-6 models carry no preview label (10).\n- Tencent Cloud TokenHub (46): Hosted reading. No public status page was found. status.cloud.tencent.com did not answer and the Tencent Cloud health dashboard documentation answered with a bot check (0). With no page there is no incident record to read (5 of 30). The announcements carry one incident, DeepSeek's directly supplied models unavailable from 9:06 to 13:04 Beijing time on 15 October 2026 after a fault at DeepSeek, compensated with vouchers. Rate limits are per model, shown in the console and returned by DescribeModelQuota. The public docs give numbers only for batch jobs (20 created a minute, 10 active), image models (5 concurrent) and DeepSeek V4 Flash and Pro (2,500 and 500 concurrent), with the rules for self-serve increases (8 of 15). Six 429 codes separate RPM, TPM, TPD, concurrency and upstream capacity, 429s may carry `Retry-After` and the docs advise exponential backoff. No idempotency guidance, though inference calls are not writes (13 of 15). The TokenHub SLA promises 99.5% monthly availability with vouchers of 10, 25 or 50 per cent of the month's fee. It excludes free use and third-party deployed models such as DeepSeek's directly supplied ones (10). Generally available since 7 April 2026, with some models marked preview (10).\n\n### Transparency \u0026 trust: Azure OpenAI in Foundry Models +29\n\n- Azure OpenAI in Foundry Models (83): Closed service under the Microsoft Product Terms, with the v1 spec under MIT and the OpenAI SDKs under Apache-2.0 (15). The data privacy page agrees with the product terms on no training and states where data is processed and stored by deployment type, but gives no retention period for the human-review store and sits beside a 30-day default for Responses data (24 of 30). A published lifecycle policy and a retirement schedule with dates and replacements, but on 6 November the schedule listed `gpt-realtime-mini` 2025-10-06 and 2025-12-15 twice each with different retirement dates, and no GPT-6 model yet (18 of 20, down from 20). Data locations stated for Standard, Data Zone and Global deployments, and a public sub-processor list per the 5 October Azure Speech check, not re-read (20).\n- Tencent Cloud TokenHub (54): Closed service under the TokenHub Terms of Service (effective 14 September 2026), the SLA (23 April 2026), a special note on third-party deployed models and the Tencent Cloud Service Agreement, naming Tencent Cloud Computing (Beijing) Co., Ltd. The CLI is Apache-2.0 (18 of 30). The terms and the FAQ agree that inputs are processed on the customer's instructions and not used for training, and clause 2.14 limits retention to what the service needs without periods. The TokenHub privacy policy on privacy.qq.com renders only with JavaScript and was not read (15 of 30). Dated retirement notices, shutdown dates in the model list, a `pre-offline` status in `/v1/models` and a `DiscontinuedAt` field in the control API. Clause 6.3 refunds paid, unused tokens when a third-party model is removed. No minimum notice period is written (13 of 20). Clause 2.13 places processing generally in mainland China for the China site and in Singapore for the international site, and the third-party model list names DeepSeek's Hangzhou company with a link to its terms. No subprocessor list was found (13 of 20).\n\n### Security \u0026 auth: Azure OpenAI in Foundry Models +24\n\n- Azure OpenAI in Foundry Models (95): Model reading. Microsoft Entra ID tokens with Azure roles (the Cognitive Services OpenAI User role for calls), managed identities, and key authentication that can be disabled per resource, or two regenerable resource keys in the `api-key` header. No documented route puts the key in a URL query string (30). Prompts, completions, embeddings and training data aren't used to train foundation models without the customer's permission or instruction, per the data privacy page updated 4 August 2026 (20). Flagged prompts and completions may be stored in the customer's geography for human abuse review, with no retention period stated, and approved customers can turn that storage off through modified abuse monitoring. Responses API data is kept 30 days by default unless `store` is false (12 of 15). Azure Monitor resource logs and the subscription activity log, as read in the Foundry fine-tuning dossier (15). MSRC coordinated disclosure policy and Microsoft's bounty programme, both named in microsoft.com's security.txt, and Azure OpenAI is listed in FedRAMP High and DoD IL2 scope in Azure public regions. The security.txt passed its Expires date on 2026-09-23 and was still expired on 6 November, which the Bedrock and S3 dossiers mark down by 2, applied here too (18 of 20, down from 20 on 6 October for consistency).\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### Agent ergonomics: Azure OpenAI in Foundry Models +15\n\n- Azure OpenAI in Foundry Models (98): Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use with parallel calls and a forced call by naming the function in `tool_choice`, 18 of 20 because `gpt-6.1-sol` calls tools only through the Responses API (18). Strict structured outputs (15). Prompt caching from 1,024 tokens, cached input at 0.1x on GPT-6 ($1 per million on Astra) and cache writes at 1.25x from GPT-5.6 on, with explicit breakpoints (15). 1,050,000-token context on GPT-6 and GPT-6.1, input capped at 922,000 (15). Batch at 50% off Global Standard with a 24-hour target (10). The docs use OpenAI's own SDKs for Python, JavaScript, C#, Go and Java against the v1 endpoint (10). 429 and quota errors documented with retry headers (15). Calls name a deployment rather than a model, so each model must be deployed in the resource first, which the model checklist doesn't score.\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### Payments \u0026 pricing: Tencent Cloud TokenHub +15\n\n- Azure OpenAI in Foundry Models (20): No x402, MPP or L402 (0). Per-1M-token prices are public in the Azure Retail Prices API without a login, while the pricing page fills its table with JavaScript and showed GPT-6 prices as pending on 6 October (20). The quota tiers include a Free tier, but an Azure subscription needs a payment method (0). A person signs up for Azure in a browser and creates a resource and a deployment before the first call (0).\n- Tencent Cloud TokenHub (35): No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by `thcli auth login`, but only from that account (0).\n\n### Schema \u0026 documentation: Azure OpenAI in Foundry Models +14\n\n- Azure OpenAI in Foundry Models (87): OpenAPI 3.2 spec for the v1 data plane in Azure/azure-rest-api-specs (`azure-v1-v1-generated.json`, 71 paths and 852 schemas), linked from the v1 API page (25). No llms.txt at learn.microsoft.com (404). Learn pages offer Copy Markdown and the Markdown sources are public in MicrosoftDocs/azure-ai-docs, last merged 5 October (5 of 10). The models page lists each model's capabilities, context and API support, but the model choice guide, dated 19 May 2026, doesn't cover GPT-6 (15 of 20). Structured outputs with `strict: true` on schemas and function tools, though not together with parallel function calls (15). Examples in Python, C#, JavaScript, Go, Java and REST, and an error table on the quotas page with a fix for 429 and other codes (15). The v1 path replaces monthly `api-version` values, with preview capabilities opted into by header, a dated API version changelog and dated model versions. On 6 November the Foundry what's new still covered August, though updated on 5 November, and no Azure OpenAI what's new was found at learn.microsoft.com/en-us/azure/foundry/openai/whats-new, which answered 404 (12 of 15).\n- Tencent Cloud TokenHub (73): Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use `deepseek-v3`, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry `/v1`, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15).\n\n## Score by category\n\n| Category | Weight | Azure OpenAI in Foundry Models | Tencent Cloud TokenHub | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 46 | Azure OpenAI in Foundry Models +34 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 73 | Azure OpenAI in Foundry Models +14 |\n| Agent ergonomics | 13% (16.2 this run) | 98 | 83 | Azure OpenAI in Foundry Models +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 95 | 71 | Azure OpenAI in Foundry Models +24 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 35 | Tencent Cloud TokenHub +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 86 | 73 | Azure OpenAI in Foundry Models +13 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 54 | Azure OpenAI in Foundry Models +29 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **80 · A** | **59.5 · C** | |\n\n## Facts side by side\n\n| Fact | Azure OpenAI in Foundry Models | Tencent Cloud TokenHub |\n| --- | --- | --- |\n| Kind | Model API | Model router |\n| Vendor | Microsoft | Tencent Cloud |\n| Hosted endpoint | `https://\u003cresource\u003e.openai.azure.com/openai/v1` | `https://tokenhub.tencentmaas.com/v1` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under the Microsoft Product Terms. The v1 OpenAPI spec is MIT, and the OpenAI SDKs the docs use are Apache-2.0 | Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-26 | 2026-10-24 |\n| Terms last updated | no date given | couldn't be read |\n| Privacy policy last updated | 2026-09-01 | couldn't be read |\n| Customer content may train models | yes | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | 454k npm/wk | 204 npm/wk |\n\n## Verdicts\n\n**Azure OpenAI in Foundry Models.** An OpenAI-compatible v1 API with a public OpenAPI spec, Entra ID roles in place of shared keys and FedRAMP High scope, with GPT-6 and GPT-6.1 at OpenAI's list prices on Global Standard. Access needs an Azure subscription with a card and a deployment per model, and a 29 September 2026 incident caused about six hours of failures in Sweden Central.\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### Azure OpenAI in Foundry Models\n\n1. Point the OpenAI SDK at https://\u003cresource\u003e.openai.azure.com/openai/v1/ and pass the deployment name as `model`, not the model id\n2. Prefer Entra ID with the Cognitive Services OpenAI User role over the resource key, which opens the whole data plane\n3. On 429 wait for `retry-after-ms`, then back off with jitter. The OpenAI SDK retries twice by default\n4. Set `store: false` on Responses calls you don't need kept. Stored responses persist 30 days by default\n5. Keep remote MCP approvals on for servers you don't control. They're required by default\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, Azure OpenAI in Foundry Models or Tencent Cloud TokenHub?\n\nAzure OpenAI in Foundry Models scores 80 (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 Azure OpenAI in Foundry Models and Tencent Cloud TokenHub need an API key?\n\nAzure OpenAI in Foundry Models takes an API key or an OAuth sign-in. Tencent Cloud TokenHub needs an API key.\n\n### Can an agent call Azure OpenAI in Foundry Models and Tencent Cloud TokenHub without installing anything?\n\nYes. Azure OpenAI in Foundry Models has a hosted endpoint at https://\u003cresource\u003e.openai.azure.com/openai/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/azure-openai-vs-tencent-tokenhub.json, and with the fewest tokens: https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"azure-openai\", \"b\": \"tencent-tokenhub\"}`. From a terminal: `anchor compare azure-openai tencent-tokenhub`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/azure-openai.json and https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n\n## Other comparisons with Azure OpenAI in Foundry Models or Tencent Cloud TokenHub\n\n- [Amazon Bedrock vs Azure OpenAI in Foundry Models](https://www.anchorterminal.com/compare/amazon-bedrock-vs-azure-openai.md)\n- [Amazon Bedrock vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/amazon-bedrock-vs-tencent-tokenhub.md)\n- [Claude API vs Azure OpenAI in Foundry Models](https://www.anchorterminal.com/compare/anthropic-api-vs-azure-openai.md)\n- [Claude API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.md)\n- [Antseed vs Azure OpenAI in Foundry Models](https://www.anchorterminal.com/compare/antseed-vs-azure-openai.md)\n- [Azure OpenAI in Foundry Models vs BlockRun.AI](https://www.anchorterminal.com/compare/azure-openai-vs-blockrun-ai.md)\n- [Azure OpenAI in Foundry Models vs Cerebras Inference](https://www.anchorterminal.com/compare/azure-openai-vs-cerebras-inference.md)\n- [Azure OpenAI in Foundry Models vs Cloudflare AI Gateway](https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-ai-gateway.md)\n- [Azure OpenAI in Foundry Models vs Cloudflare Workers AI](https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-workers-ai.md)\n- [Azure OpenAI in Foundry Models vs Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/azure-openai-vs-cohere-chat.md)\n- [Azure OpenAI in Foundry Models vs DeepInfra](https://www.anchorterminal.com/compare/azure-openai-vs-deepinfra.md)\n- [Azure OpenAI in Foundry Models vs DeepSeek API](https://www.anchorterminal.com/compare/azure-openai-vs-deepseek-api.md)\n- [Azure OpenAI in Foundry Models vs Eden AI](https://www.anchorterminal.com/compare/azure-openai-vs-eden-ai.md)\n- [Azure OpenAI in Foundry Models vs Glimpse](https://www.anchorterminal.com/compare/azure-openai-vs-elorian-glimpse.md)\n- [Azure OpenAI in Foundry Models vs Fireworks AI Inference](https://www.anchorterminal.com/compare/azure-openai-vs-fireworks-inference.md)\n- [Azure OpenAI in Foundry Models vs Gemini Developer API](https://www.anchorterminal.com/compare/azure-openai-vs-gemini-api.md)\n- [Azure OpenAI in Foundry Models vs GroqCloud](https://www.anchorterminal.com/compare/azure-openai-vs-groq.md)\n- [Azure OpenAI in Foundry Models vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/azure-openai-vs-hugging-face-inference-providers.md)\n- [Azure OpenAI in Foundry Models vs Inkling 2 Small](https://www.anchorterminal.com/compare/azure-openai-vs-inkling-2-small.md)\n- [Azure OpenAI in Foundry Models vs Jais 3](https://www.anchorterminal.com/compare/azure-openai-vs-jais-3.md)\n- [Azure OpenAI in Foundry Models vs Meta Model API](https://www.anchorterminal.com/compare/azure-openai-vs-meta-model-api.md)\n- [Azure OpenAI in Foundry Models vs MiniMax API](https://www.anchorterminal.com/compare/azure-openai-vs-minimax-api.md)\n- [Azure OpenAI in Foundry Models vs Mistral AI API](https://www.anchorterminal.com/compare/azure-openai-vs-mistral-api.md)\n- [Azure OpenAI in Foundry Models vs Muse Spark Open](https://www.anchorterminal.com/compare/azure-openai-vs-muse-spark-open.md)\n- [Azure OpenAI in Foundry Models vs Nemotron 3.5 Super VL](https://www.anchorterminal.com/compare/azure-openai-vs-nemotron-3-5-super-vl.md)\n- [Azure OpenAI in Foundry Models vs Novita AI](https://www.anchorterminal.com/compare/azure-openai-vs-novita-ai.md)\n- [Azure OpenAI in Foundry Models vs OpenAI API](https://www.anchorterminal.com/compare/azure-openai-vs-openai-api.md)\n- [Azure OpenAI in Foundry Models vs OpenRouter](https://www.anchorterminal.com/compare/azure-openai-vs-openrouter.md)\n- [Azure OpenAI in Foundry Models vs Prism Inference](https://www.anchorterminal.com/compare/azure-openai-vs-prism-inference.md)\n- [Azure OpenAI in Foundry Models vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/azure-openai-vs-ramp-router.md)\n- [Azure OpenAI in Foundry Models vs Beam 1.0](https://www.anchorterminal.com/compare/azure-openai-vs-reflection-beam.md)\n- [Azure OpenAI in Foundry Models vs RouterPlus](https://www.anchorterminal.com/compare/azure-openai-vs-routerplus.md)\n- [Azure OpenAI in Foundry Models vs SambaCloud](https://www.anchorterminal.com/compare/azure-openai-vs-sambanova.md)\n- [Azure OpenAI in Foundry Models vs SiliconFlow](https://www.anchorterminal.com/compare/azure-openai-vs-siliconflow.md)\n- [Azure OpenAI in Foundry Models vs Simplismart](https://www.anchorterminal.com/compare/azure-openai-vs-simplismart.md)\n- [Azure OpenAI in Foundry Models vs StepFun API](https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api.md)\n- [Azure OpenAI in Foundry Models vs SWE-2 Flash](https://www.anchorterminal.com/compare/azure-openai-vs-swe-2-flash.md)\n- [Azure OpenAI in Foundry Models vs Together AI Inference](https://www.anchorterminal.com/compare/azure-openai-vs-together-inference.md)\n- [Azure OpenAI in Foundry Models vs Vercel AI Gateway](https://www.anchorterminal.com/compare/azure-openai-vs-vercel-ai-gateway.md)\n- [Azure OpenAI in Foundry Models vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/azure-openai-vs-vertex-ai.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- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.md)\n- [Cloudflare AI Gateway vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub.md)\n- [Cloudflare Workers AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub.md)\n- [Cohere Chat API (Command models) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.md)\n- [DeepInfra vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.md)\n- [DeepSeek API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.md)\n- [Glimpse vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.md)\n- [Fireworks AI Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.md)\n- [Gemini Developer API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.md)\n- [GroqCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.md)\n- [Inkling 2 Small vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/inkling-2-small-vs-tencent-tokenhub.md)\n- [Jais 3 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.md)\n- [Meta Model API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.md)\n- [MiniMax API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.md)\n- [Mistral AI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.md)\n- [Muse Spark Open vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.md)\n- [Novita AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.md)\n- [OpenAI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.md)\n- [OpenRouter vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.md)\n- [Beam 1.0 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.md)\n- [SambaCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.md)\n- [SiliconFlow vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.md)\n- [Simplismart vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.md)\n- [StepFun API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.md)\n- [SWE-2 Flash vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/swe-2-flash-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Together AI Inference](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.md)\n- [Tencent Cloud TokenHub vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vertex-ai.md)\n- [Tencent Cloud TokenHub vs xAI API (Grok)](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-xai-api.md)\n- [Antseed vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.md)\n- [Eden AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/eden-ai-vs-tencent-tokenhub.md)\n- [Hugging Face Inference Providers vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.md)\n- [LiteLLM vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/litellm-vs-tencent-tokenhub.md)\n- [Router.com (Ramp Router) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.md)\n- [RouterPlus vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Vercel AI Gateway](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.md)\n- [Nemotron 3.5 Super VL vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub.md)\n- [Prism Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Azure OpenAI in Foundry Models vs Tencent Cloud TokenHub", "url": "" } ], "description": "Azure OpenAI in Foundry Models scores 80 (A) to Tencent Cloud TokenHub's 59.5 (C) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Azure OpenAI in Foundry Models A 80", "Tencent Cloud TokenHub C 59.5", "scores" ], "h1": "Azure OpenAI in Foundry Models vs Tencent Cloud TokenHub", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/azure-openai-vs-tencent-tokenhub", "published": "2026-10-01", "section": "tools", "title": "Azure OpenAI in Foundry Models vs Tencent Cloud TokenHub (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub" }, "tokens": { "markdown": 7900, "slim": 4130 }, "version": 1 }