{ "data": { "a": { "slug": "tencent-tokenhub", "name": "Tencent Cloud TokenHub", "vendor": "Tencent Cloud", "vendorUrl": "https://cloud.tencent.com", "kind": "router", "category": "inference", "summary": "Tencent Cloud TokenHub is a hosted model gateway serving Tencent's Hy models and third-party models such as DeepSeek, Kimi, GLM and MiniMax through OpenAI-compatible and Anthropic-compatible endpoints in Guangzhou and Singapore, with per-key scopes and quotas.", "url": "https://www.anchorterminal.com/tools/tencent-tokenhub", "markdownUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json", "dns": "tencent-tokenhub.grade.anchorterminal.com", "repo": "https://github.com/TencentCloud/THCLI", "license": "Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://tokenhub.tencentmaas.com/v1", "packages": [ { "registry": "npm", "name": "tencent-tokenhub-cli" } ], "auth": "api-key", "authNotes": "Bearer API key from the TokenHub console, or `x-api-key` on the Anthropic-style `/v1/messages`. Keys are long-lived, belong to one region (Guangzhou or Singapore), can be limited to chosen models and inference services, up to 200 IP ranges and token quotas, and can be disabled or deleted. They can also be created through the CreateApiKey control-plane call with signed Tencent Cloud credentials, or by `thcli auth login`. The account needs real-name verification first.", "pricing": "usage", "pricingNotes": "Pay per token in CNY, billed hourly. Hy4 preview costs 6 CNY in, 18 CNY out and 0.3 CNY cached per 1M tokens, Hy3 1, 4 and 0.25 CNY. DeepSeek models double at weekday peak hours. Batch is half price for Hy3 and Hy4 preview. Each account gets 1M free tokens per language model for a year, in a campaign to 31 December 2026. Token Plan subscriptions run from 28 to 599 CNY a month (https://cloud.tencent.com/document/product/1823/130055, checked 2026-11-01).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs table of contents, the billing pages or the API usage page. Payment is from a Tencent Cloud account balance, billed hourly (checked 2026-11-01).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 204, "pypiWeekly": null, "asOf": "2026-11-01" }, "docsUrl": "https://cloud.tencent.com/document/product/1823/130058", "rateLimitsUrl": "https://cloud.tencent.com/document/product/1823/136028", "llmsTxt": "https://cloud.tencent.com/document/product/1823/llms.txt", "capabilities": [ "inference.router", "inference.llm", "inference.open-weights", "embed.text", "embed.multimodal", "image.generate", "video.generate", "speech.tts", "speech.stt", "audio.music", "translate.text", "web.search", "obs.gateway" ], "tags": [ "hosted", "router", "usage-based", "free-credit", "openai-compatible", "anthropic-compatible", "llms-txt", "cli", "sla", "batch", "bug-bounty", "no-status-page", "regional-endpoints", "singapore", "chinese", "subscription" ], "lastRelease": "2026-10-24", "graded": true, "anchor": { "graded": true, "score": 59.5, "grade": "C", "agentReady": false, "rank": 646, "ranked": true, "rankOf": 1260, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 73, "payments": 35, "reliability": 46, "schema": 73, "security": 71, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -3, "negativeNotes": [ "2026-10-17. -3, a breaking change without notice. DeepSeek-V4.1-Flash (directly supplied) was moved to its 1017 version under the same model ids and prices on 17 October 2026, and the notice came two days later (https://cloud.tencent.com/announce/detail/2516). Callers pinned to the id got a different model's behaviour with no warning. One term at the floor: the API didn't change. The founder's decision, 1 November 2026." ], "verdict": "Keys can be limited to chosen models, source IPs and token quotas, errors name their source and code, and a 99.5% SLA covers paid use of models Tencent runs. Sign-up needs a Tencent Cloud account with real-name verification, prices are in CNY, no public status page was found, and 18 model retirement notices ran from April to October 2026.", "bestFor": "Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing.", "strengths": [ "API keys can be limited to chosen models and inference services, up to 200 source IP ranges, and daily, monthly or total token quotas", "One base URL answers OpenAI Chat Completions, OpenAI Responses and Anthropic Messages calls, and `GET /v1/models` marks models due to retire as `pre-offline`", "Error bodies carry a six-digit code, English and Chinese messages, the source (client, gateway or upstream) and a request ID, and 429s can carry `Retry-After`", "A published SLA promises 99.5% monthly availability with voucher credits of 10 to 50 per cent of the month's fee, for paid use of models Tencent runs", "Per-call audit logs (request ID, key, client IP, status, tokens, latency) can be delivered to the customer's own Tencent Cloud CLS log service" ], "weaknesses": [ "Sign-up needs a Tencent Cloud account with real-name verification. The international site answered with a bot check, so access from outside China was not established", "No public status page was found. A four-hour outage of DeepSeek's directly supplied models on 15 October 2026 appears only as a compensation notice", "18 model retirement notices from 21 April to 22 October 2026. Those read gave 21 to 33 days, and eligible callers are switched to a successor at its price", "DeepSeek's directly supplied models send inputs to DeepSeek under its own terms, and the TokenHub SLA does not cover them", "Per-model RPM and TPM limits for chat models are shown in the console and the quota API, not in the public docs" ], "agentNotes": [ "Use `https://tokenhub.tencentmaas.com/v1` with keys made for Guangzhou and `https://tokenhub-intl.tencentmaas.com/v1` with keys made for Singapore. Keys do not work across the two", "Send the key as `Authorization: Bearer` on the OpenAI paths and as `x-api-key` on `/v1/messages`", "Parse `error.code` as a string or a number, since 429 codes can come back as integers, and wait for `Retry-After` before retrying", "Take model ids from `GET /v1/models` and watch for `pre-offline`. The quickstart's `deepseek-v3` example is not in the current model list", "Expect DeepSeek prices to double on weekdays from 9am to noon and 2pm to 6pm Beijing time, when the peak rate applies" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.5 } ], "editorialScores": { "ergonomics": 83, "maintenance": 73, "payments": 35, "reliability": 46, "schema": 73, "security": 71, "transparency": 59 }, "provenanceScore": 49, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm i -g tencent-tokenhub-cli", "http": "curl https://tokenhub.tencentmaas.com/v1/models \\\n -H \"Authorization: Bearer $TOKENHUB_API_KEY\"", "claudeCode": "{\n \"env\": {\n \"ANTHROPIC_BASE_URL\": \"https://tokenhub.tencentmaas.com\",\n \"ANTHROPIC_AUTH_TOKEN\": \"YOUR_API_KEY\",\n \"ANTHROPIC_MODEL\": \"hy3\"\n }\n}" }, "letme": { "capability": "https://letme.dev/inference.router", "tool": "https://letme.dev/tencent-tokenhub" }, "area": "models", "provenance": { "legalEntity": "Tencent Cloud Computing (Beijing) Co., Ltd. (腾讯云计算（北京）有限责任公司)", "domain": "tencentmaas.com", "domainRegistered": "2026-03-13", "endpointOnVendorDomain": false, "terms": "https://cloud.tencent.com/document/product/301/129852", "privacy": "https://privacy.qq.com/document/preview/91d5fd3c98ce4468ae462ac59233bba2", "statusPage": "", "changelog": "https://cloud.tencent.com/document/product/1823/130675", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "The TokenHub Terms of Service (effective 14 September 2026), the SLA (effective 23 April 2026) and the special note on third-party deployed models (effective 14 September 2026) name 腾讯云计算（北京）有限责任公司. The docs footer also names 深圳市腾讯计算机系统有限公司 as ICP licence holder.", "The TokenHub privacy policy is linked from the docs to privacy.qq.com, which renders only with JavaScript, so it was not read. privacy.qq.com has no robots.txt (404).", "No public status page was found. status.cloud.tencent.com did not answer, and the Tencent Cloud health dashboard documentation answered with a bot check.", "security.txt answered 404 on cloud.tencent.com, www.tencent.com and tokenhub.tencentmaas.com. Tencent's bug bounty policy at en.security.tencent.com lists Tencent Cloud in scope.", "RDAP at Verisign gives tencentmaas.com a registration date of 13 March 2026 with no registrant. The API answers at tokenhub.tencentmaas.com and tokenhub-intl.tencentmaas.com, named in Tencent Cloud's API usage page.", "cloud.tencent.com allows these docs in robots.txt. Its pages answered some requests with a JavaScript bot check, which was not passed. The pages were read when a later plain request returned them. www.tencentcloud.com answered robots.txt with a bot check, so the international site was not read." ], "score": 49 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.json", "live": { "slug": "tencent-tokenhub", "probe": { "target": "https://tokenhub.tencentmaas.com/v1", "method": "get", "lastAt": "2026-11-02T00:56:24.101434531Z", "lastOk": true, "lastStatus": 404, "lastMs": 795, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 826, "p95ms24h": 1067, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-11-01", "probes": 18, "ok": 18 }, { "date": "2026-11-02", "probes": 10, "ok": 10 } ] }, "updatedAt": "2026-11-02T00:56:24.101434531Z" } }, "answer": "Together AI Inference scores 67.8 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 4 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "together-inference", "name": "Together AI Inference", "vendor": "Together Computer, Inc.", "vendorUrl": "https://www.together.ai", "kind": "http-api", "category": "inference", "summary": "Together AI Inference serves open models through an OpenAI-compatible API, with serverless requests, batch processing, dedicated model deployments and provisioned throughput. Model-dependent capabilities include tool calling, structured outputs and vision.", "url": "https://www.anchorterminal.com/tools/together-inference", "markdownUrl": "https://www.anchorterminal.com/tools/together-inference.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/together-inference.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/together-inference.json", "dns": "together-inference.grade.anchorterminal.com", "repo": "https://github.com/togethercomputer/together-py", "license": "Proprietary hosted service. The official Python SDK is Apache-2.0; served models retain their own licences.", "transports": [ "http" ], "remoteUrl": "https://api.together.ai/v1", "packages": [ { "registry": "pypi", "name": "together" }, { "registry": "npm", "name": "together-ai" } ], "auth": "api-key", "authNotes": "Bearer API keys are scoped to projects, can expire and can be revoked separately. A key has full access to resources in its project. There are no per-key spending or rate limits; legacy default-project keys should be replaced.", "pricing": "paid", "pricingNotes": "Prepaid usage with a $15 minimum first credit purchase, then $5 minimum top-ups. No free trial. GPT OSS 120B is $0.15 per million input tokens and $0.60 per million output tokens. Dedicated hardware and provisioned throughput have separate rates.", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 payment route found in the reviewed inference and billing documentation on 19 October 2026.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 10, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-19" }, "docsUrl": "https://docs.together.ai", "llmsTxt": "https://docs.together.ai/llms.txt", "openapi": "https://docs.together.ai/openapi.yaml", "capabilities": [ "inference.llm", "inference.open-weights" ], "tags": [ "official", "http-api", "inference", "api-key", "openapi", "llms-txt", "paid" ], "lastRelease": "2026-10-23", "graded": true, "anchor": { "graded": true, "score": 67.8, "grade": "B", "agentReady": false, "rank": 236, "ranked": true, "rankOf": 1260, "categoryRank": 9, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 85, "maintenance": 65, "payments": 20, "reliability": 75, "schema": 93, "security": 70, "transparency": 74 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -3, "negativeNotes": [ "2026-08-19 to 2026-08-27. Together removed GA serverless models with notice posted only on the day of removal. Changelog entries of 19, 21, 25 and 27 August say FLUX.1 schnell, Qwen2.5 7B, Kimi K2.6, Cogito v2.1 671B, Gemma 3n E4B, Llama Guard 4 12B, Nemotron 3 Ultra, Pearl's Gemma 4 31B, DeepSeek V4 Pro and Kimi K2.7 Code \"have been deprecated and are no longer available on serverless\", with no earlier entry announcing their removal and no preview label, while the deprecation policy promises 2 or 3 weeks' notice for serverless endpoints. Read at the floor, as fireworks-inference's same-day removals of 27 August were, -3 (https://docs.together.ai/docs/changelog.md)." ], "verdict": "A broad inference API with project-scoped keys, SDKs and multiple capacity options. Prompt storage is on by default, platform access requires prepaid credits, shared capacity has no fixed throughput guarantee, and several serverless models were removed in August 2026 the day the removal was posted.", "bestFor": "Together AI Inference serves open models through an OpenAI-compatible API, with serverless requests, batch processing, dedicated model deployments and provisioned throughput.", "strengths": [ "Public OpenAPI 3.1, Markdown documentation and Python and TypeScript SDKs", "Project-scoped API keys with optional expiry and per-key cost attribution", "Serverless, batch, dedicated and provisioned-throughput options", "Status page with a monitor per serverless model and 90 days of daily history", "US-only serverless processing through us-api.together.ai since 16 October 2026, at 1.25 times standard rates" ], "weaknesses": [ "A $15 credit purchase is required before platform access; no free trial", "Prompt and response storage is on by default; zero data retention must be enabled for the organisation", "Serverless has no guaranteed capacity outside provisioned throughput, and API keys have no individual spend caps", "Serverless models removed on 19, 21, 25 and 27 August 2026 were announced in the changelog only on the day" ], "agentNotes": [ "Create a project-scoped key and set TOGETHER_API_KEY. Avoid deprecated legacy keys.", "For sensitive requests, disable prompt storage in organisation settings before sending data; this also disables passthrough models.", "Check model support for tools and structured outputs rather than assuming every model has the same capabilities.", "Back off on 429 and 503 responses. Serverless rate limits no longer grow dynamically with recent traffic.", "Check the deprecation schedule before choosing a model. Qwen3.8-2.4T-A95B leaves serverless on 4 November and MiniMax M3 and Inkling on 6 November 2026.", "Pin the SDK major version. Python SDK 3.0 and TypeScript SDK 1.0 (22 October 2026) drop `/v1` from the base URL and the `beta` paths" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.8 } ], "editorialScores": { "ergonomics": 85, "maintenance": 65, "payments": 20, "reliability": 75, "schema": 93, "security": 70, "transparency": 65 }, "provenanceScore": 83, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl 'https://api.together.ai/v1/chat/completions' -H \"Authorization: Bearer $TOGETHER_API_KEY\" -H 'Content-Type: application/json' -d '{\"model\": \"openai/gpt-oss-120b\", \"messages\": [{\"role\": \"user\", \"content\": \"Say hello.\"}], \"max_tokens\": 128}'" }, "letme": { "capability": "https://letme.dev/inference.llm", "tool": "https://letme.dev/together-inference" }, "sameCompany": [ "together-fine-tuning", "together-code-sandbox" ], "area": "models", "unitPrices": [ { "item": "GPT OSS 120B input", "unit": "1m-tokens", "usd": 0.15, "note": "Shared/serverless standard rate, per million tokens, checked 1 November 2026" }, { "item": "GPT OSS 120B output", "unit": "1m-tokens", "usd": 0.6, "note": "Shared/serverless standard rate, per million tokens, checked 1 November 2026" } ], "provenance": { "legalEntity": "Together Computer, Inc.", "domain": "together.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.together.ai/terms-of-service", "privacy": "https://www.together.ai/privacy", "statusPage": "https://status.together.ai", "changelog": "https://docs.together.ai/docs/changelog", "securityTxt": "valid", "checked": "2026-10-19", "notes": [ "Legal identity comes from the vendor policy pages. Domain registration was not checked.", "The SDK repository is not the source for the hosted inference service.", "security.txt names the HackerOne programme and expires on 30 September 2028." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/together-inference.json", "live": { "slug": "together-inference", "probe": { "target": "https://api.together.ai/v1", "method": "get", "lastAt": "2026-11-02T00:56:25.075101654Z", "lastOk": true, "lastStatus": 404, "lastMs": 206, "authRequired": false, "uptime24h": 100, "uptime30d": 99.97, "p50ms24h": 212, "p95ms24h": 530, "samples24h": 249, "samples30d": 3439, "days": [ { "date": "2026-10-19", "probes": 173, "ok": 173 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 249 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 10, "ok": 10 } ] }, "vendorStatus": { "page": "https://status.together.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-01T20:59:41.651286421Z" }, "versions": [ { "registry": "github", "name": "togethercomputer/together-py", "version": "v3.0.0", "released": "2026-10-22", "seenAt": "2026-11-01T17:39:30.336395784Z" }, { "registry": "npm", "name": "together-ai", "version": "1.0.0", "seenAt": "2026-11-01T17:39:30.188906698Z" }, { "registry": "pypi", "name": "together", "version": "3.0.0", "released": "2026-10-22", "seenAt": "2026-11-01T17:39:30.026710164Z" } ], "githubStars": 11, "npmWeekly": 127328, "pypiWeekly": 431311, "securityTxt": { "url": "https://together.ai/.well-known/security.txt", "state": "valid", "expires": "2028-09-30T00:00:00.000Z", "checkedAt": "2026-11-01T15:43:10.291659714Z" }, "llmsTxt": { "url": "https://docs.together.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:15:13.541465139Z" }, "domain": { "domain": "together.ai", "registered": "2017-12-16", "source": "https://rdap.identitydigital.services/rdap/domain/together.ai", "checkedAt": "2026-11-01T14:21:27.260418255Z" }, "github": { "repo": "togethercomputer/together-py", "checkedAt": "2026-10-26T07:06:33.982237463Z", "stars": 11, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-23T16:13:17Z", "openIssues": 4, "openPRs": 38, "issuesOpened90d": 3, "issuesClosed90d": 1, "prsMerged90d": 108, "ci": { "branch": "main", "runs": 50, "success": 16, "failure": 0, "other": 34, "latest": "skipped", "latestAt": "2026-10-23T16:12:54Z" }, "replies": { "sampled": 7, "unanswered": 4, "medianDays": 14.2 } }, "updatedAt": "2026-11-02T00:56:25.075101654Z" } }, "edges": [ { "by": 29, "category": "reliability", "leads": "together-inference", "name": "Reliability", "reasons": { "a": "Hosted reading. No public status page was found. status.cloud.tencent.com did not answer and the Tencent Cloud health dashboard documentation answered with a bot check (0). With no page there is no incident record to read (5 of 30). The announcements carry one incident, DeepSeek's directly supplied models unavailable from 9:06 to 13:04 Beijing time on 15 October 2026 after a fault at DeepSeek, compensated with vouchers. Rate limits are per model, shown in the console and returned by DescribeModelQuota. The public docs give numbers only for batch jobs (20 created a minute, 10 active), image models (5 concurrent) and DeepSeek V4 Flash and Pro (2,500 and 500 concurrent), with the rules for self-serve increases (8 of 15). Six 429 codes separate RPM, TPM, TPD, concurrency and upstream capacity, 429s may carry `Retry-After` and the docs advise exponential backoff. No idempotency guidance, though inference calls are not writes (13 of 15). The TokenHub SLA promises 99.5% monthly availability with vouchers of 10, 25 or 50 per cent of the month's fee. It excludes free use and third-party deployed models such as DeepSeek's directly supplied ones (10). Generally available since 7 April 2026, with some models marked preview (10).", "b": "Graded as listed, on the hosted API lines. Public Better Stack status page at status.together.ai with a component for each serverless model plus the website and playground (20). The page shows 90 daily ticks per component, read on 1 November 2026 for 4 August to 1 November, and no incident was posted in that time (the feed's newest items are maintenance windows in April and July 2026). Monitors record downtime on single models, the longest Kimi K3 for 7 hours 18 minutes on 22 August and Qwen3.8-2.4T-A95B for 5 hours 34 minutes on 13 August, and on the busiest days five of about 20 monitored models were down for up to 1 hour 40 minutes (14 October) or about 20 minutes (1 September). Each hit one model or a subset of the catalogue, so the record reads as minor incidents only (20). The current serverless page gives no numeric general request ceiling (0). Explicit 429 and 503 backoff guidance (15). Provisioned throughput has a published 99% eligible-request commitment (10). Serverless inference is generally available (10). 20 + 20 + 0 + 15 + 10 + 10 = 75." }, "scores": { "a": 46, "b": 75 } }, { "by": 20, "category": "schema", "leads": "together-inference", "name": "Schema \u0026 documentation", "reasons": { "a": "Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use `deepseek-v3`, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry `/v1`, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15).", "b": "Public OpenAPI 3.1 (25), llms.txt and Markdown docs (10), endpoint and model-capability guidance (16 of 20), typed inputs and constraints (13 of 15), examples and documented errors (14 of 15), and versioned endpoints with a dated changelog (15)." }, "scores": { "a": 73, "b": 93 } }, { "by": 20, "category": "transparency", "leads": "together-inference", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under the TokenHub Terms of Service (effective 14 September 2026), the SLA (23 April 2026), a special note on third-party deployed models and the Tencent Cloud Service Agreement, naming Tencent Cloud Computing (Beijing) Co., Ltd. The CLI is Apache-2.0 (18 of 30). The terms and the FAQ agree that inputs are processed on the customer's instructions and not used for training, and clause 2.14 limits retention to what the service needs without periods. The TokenHub privacy policy on privacy.qq.com renders only with JavaScript and was not read (15 of 30). Dated retirement notices, shutdown dates in the model list, a `pre-offline` status in `/v1/models` and a `DiscontinuedAt` field in the control API. Clause 6.3 refunds paid, unused tokens when a third-party model is removed. No minimum notice period is written (13 of 20). Clause 2.13 places processing generally in mainland China for the China site and in Singapore for the international site, and the third-party model list names DeepSeek's Hangzhou company with a link to its terms. No subprocessor list was found (13 of 20).", "b": "Proprietary service with published terms and Apache-2.0 SDK (15). Docs distinguish default content storage, training opt-in, organisation ZDR and passthrough models, but default content retention has no fixed duration in the reviewed pages (25 of 30). Public lifecycle policy gives a two-week migration window for breaking model upgrades and 2 or 3 weeks' notice for serverless removals, though removals on 19, 21, 25 and 27 August 2026 were posted only on the day (15 of 20). North American hosting and enterprise residency options are described; full subprocessor locations were not established (10 of 20)." }, "scores": { "a": 54, "b": 74 } }, { "by": 15, "category": "payments", "leads": "tencent-tokenhub", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by `thcli auth login`, but only from that account (0).", "b": "No machine payment protocol found in the reviewed billing and inference docs (0). Public token and capacity prices (20). No free trial and a $15 minimum first credit purchase (0). Browser account and payment setup required (0)." }, "scores": { "a": 35, "b": 20 } }, { "by": 8, "category": "maintenance", "leads": "tencent-tokenhub", "name": "Maintenance \u0026 community", "reasons": { "a": "Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q\u0026A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and `tencent-tokenhub-cli` 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10).", "b": "Graded as listed, on the tool lines. Changelog entries on 22 and 23 October 2026 (Python SDK 3.0, TypeScript SDK 1.0, MiniMax M3.1 Flash on serverless and post-training) (30). 43 dated changelog days and 16 Python SDK tags from 3 August, v2.33.1 to v3.0.0 (20). Support responsiveness not tested (0). Official Python and TypeScript SDKs, both given new majors on 22 October (15). Dependency and CI health not audited (0)." }, "scores": { "a": 73, "b": 65 } } ], "facts": [ { "a": "Model router", "b": "HTTP API", "name": "Kind" }, { "a": "Tencent Cloud", "b": "Together Computer, Inc.", "name": "Vendor" }, { "a": "https://tokenhub.tencentmaas.com/v1", "b": "https://api.together.ai/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0", "b": "Proprietary hosted service. The official Python SDK is Apache-2.0; served models retain their own licences.", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-24", "b": "2026-10-23", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "204 npm/wk", "b": "10 stars", "name": "Popularity" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Together AI Inference scores 67.8 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 4 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Tencent Cloud TokenHub or Together AI Inference?" }, { "answer": "Both need an API key.", "question": "Do Tencent Cloud TokenHub and Together AI Inference need an API key?" }, { "answer": "Yes. Tencent Cloud TokenHub has a hosted endpoint at https://tokenhub.tencentmaas.com/v1 and Together AI Inference at https://api.together.ai/v1.", "question": "Can an agent call Tencent Cloud TokenHub and Together AI Inference without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 35 against 20", "Maintenance \u0026 community, 73 against 65" ], "also": null, "goodFor": "Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing.", "slug": "tencent-tokenhub", "watchFor": "Sign-up needs a Tencent Cloud account with real-name verification. The international site answered with a bot check, so access from outside China was not established" }, { "aheadOn": [ "Reliability, 75 against 46", "Schema \u0026 documentation, 93 against 73", "Transparency \u0026 trust, 74 against 54" ], "also": null, "goodFor": "Together AI Inference serves open models through an OpenAI-compatible API, with serverless requests, batch processing, dedicated model deployments and provisioned throughput.", "slug": "together-inference", "watchFor": "A $15 credit purchase is required before platform access; no free trial" } ], "history": { "tencent-tokenhub": null, "together-inference": [ { "causes": [ "evidence", "correction" ], "date": "2026-11-01", "delta": 0, "from": 67.8, "fromGrade": "B", "to": 67.8, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0, "from": 67.8, "fromGrade": "B", "to": 67.8, "toGrade": "B" } ] }, "job": { "capability": "inference.llm", "name": "LLM inference" }, "others": [ { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.json", "title": "Claude API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-together-inference.json", "title": "Claude API vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-together-inference.json", "title": "Antseed vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/antseed-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.json", "title": "BlockRun.AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/blockrun-ai-vs-together-inference.json", "title": "BlockRun.AI vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.json", "title": "Cerebras Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cerebras-inference-vs-together-inference.json", "title": "Cerebras Inference vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub.json", "title": "Cloudflare AI Gateway vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-together-inference.json", "title": "Cloudflare AI Gateway vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub.json", "title": "Cloudflare Workers AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-together-inference.json", "title": "Cloudflare Workers AI vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.json", "title": "Cohere Chat API (Command models) vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-together-inference.json", "title": "Cohere Chat API (Command models) vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.json", "title": "DeepInfra vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/deepinfra-vs-together-inference.json", "title": "DeepInfra vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.json", "title": "DeepSeek API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/deepseek-api-vs-together-inference.json", "title": "DeepSeek API vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.json", "title": "Glimpse vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-together-inference.json", "title": "Glimpse vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.json", "title": "Fireworks AI Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-together-inference.json", "title": "Fireworks AI Inference vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.json", "title": "Gemini Developer API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/gemini-api-vs-together-inference.json", "title": "Gemini Developer API vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.json", "title": "GroqCloud vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/groq-vs-together-inference.json", "title": "GroqCloud vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/groq-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.json", "title": "Jais 3 vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/jais-3-vs-together-inference.json", "title": "Jais 3 vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/jais-3-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.json", "title": "Meta Model API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/meta-model-api-vs-together-inference.json", "title": "Meta Model API vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.json", "title": "MiniMax API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/minimax-api-vs-together-inference.json", "title": "MiniMax API vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.json", "title": "Mistral AI API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/mistral-api-vs-together-inference.json", "title": "Mistral AI API vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.json", "title": "Muse Spark Open vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/muse-spark-open-vs-together-inference.json", "title": "Muse Spark Open vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.json", "title": "Novita AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/novita-ai-vs-together-inference.json", "title": "Novita AI vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.json", "title": "OpenAI API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-together-inference.json", "title": "OpenAI API vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/openai-api-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.json", "title": "OpenRouter vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/openrouter-vs-together-inference.json", "title": "OpenRouter vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/openrouter-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/prism-inference-vs-together-inference.json", "title": "Prism Inference vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/ramp-router-vs-together-inference.json", "title": "Router.com (Ramp Router) vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.json", "title": "Beam 1.0 vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/reflection-beam-vs-together-inference.json", "title": "Beam 1.0 vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/reflection-beam-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-together-inference.json", "title": "RouterPlus vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/routerplus-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.json", "title": "SambaCloud vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/sambanova-vs-together-inference.json", "title": "SambaCloud vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/sambanova-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.json", "title": "SiliconFlow vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/siliconflow-vs-together-inference.json", "title": "SiliconFlow vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/siliconflow-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.json", "title": "Simplismart vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/simplismart-vs-together-inference.json", "title": "Simplismart vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/simplismart-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.json", "title": "StepFun API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/stepfun-api-vs-together-inference.json", "title": "StepFun API vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/stepfun-api-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/together-inference-vs-vercel-ai-gateway.json", "title": "Together AI Inference vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/together-inference-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/nemotron-3-5-super-vl-vs-together-inference.json", "title": "Nemotron 3.5 Super VL vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.json", "title": "Prism Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.json", "title": "Antseed vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.json", "title": "Router.com (Ramp Router) vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.json", "title": "RouterPlus vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.json", "title": "Tencent Cloud TokenHub vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway" } ], "panel": null, "scores": [ { "by": 29, "edge": "together-inference", "key": "reliability", "name": "Reliability", "tencent-tokenhub": 46, "together-inference": 75, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 20, "edge": "together-inference", "key": "schema", "name": "Schema \u0026 documentation", "tencent-tokenhub": 73, "together-inference": 93, "weight": 13 }, { "by": 2, "edge": "together-inference", "key": "ergonomics", "name": "Agent ergonomics", "tencent-tokenhub": 83, "together-inference": 85, "weight": 13 }, { "by": 1, "edge": "tencent-tokenhub", "key": "security", "name": "Security \u0026 auth", "tencent-tokenhub": 71, "together-inference": 70, "weight": 14 }, { "by": 15, "edge": "tencent-tokenhub", "key": "payments", "name": "Payments \u0026 pricing", "tencent-tokenhub": 35, "together-inference": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "edge": "tencent-tokenhub", "key": "maintenance", "name": "Maintenance \u0026 community", "tencent-tokenhub": 73, "together-inference": 65, "weight": 7 }, { "by": 20, "edge": "together-inference", "key": "transparency", "name": "Transparency \u0026 trust", "tencent-tokenhub": 54, "together-inference": 74, "weight": 7 } ], "summary": "Together AI Inference scores 67.8 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 4 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing and maintenance \u0026 community. Both do llm inference.", "tasks": null, "tutorials": [], "verdicts": { "tencent-tokenhub": "Keys can be limited to chosen models, source IPs and token quotas, errors name their source and code, and a 99.5% SLA covers paid use of models Tencent runs. Sign-up needs a Tencent Cloud account with real-name verification, prices are in CNY, no public status page was found, and 18 model retirement notices ran from April to October 2026.", "together-inference": "A broad inference API with project-scoped keys, SDKs and multiple capacity options. Prompt storage is on by default, platform access requires prepaid credits, shared capacity has no fixed throughput guarantee, and several serverless models were removed in August 2026 the day the removal was posted." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference", "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.min.md" }, "markdown": "Together AI Inference scores 67.8 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 4 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing and maintenance \u0026 community. Both do llm inference.\n\n- Tencent Cloud TokenHub: grade C, 59.5/100, rank #646 of 1260. Markdown https://www.anchorterminal.com/tools/tencent-tokenhub.md · JSON https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n- Together AI Inference: grade B, 67.8/100, rank #236 of 1260. Markdown https://www.anchorterminal.com/tools/together-inference.md · JSON https://www.anchorterminal.com/api/v1/tools/together-inference.json\n- Best model APIs and inference for AI agents: https://www.anchorterminal.com/best/inference/index.md\n- All 529 models comparisons: https://www.anchorterminal.com/compare/inference/index.md\n\n## Which one, for what\n\n### 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- Maintenance \u0026 community, 73 against 65\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### Together AI Inference (B)\n\nGood for: Together AI Inference serves open models through an OpenAI-compatible API, with serverless requests, batch processing, dedicated model deployments and provisioned throughput.\n\nAhead on:\n- Reliability, 75 against 46\n- Schema \u0026 documentation, 93 against 73\n- Transparency \u0026 trust, 74 against 54\n\nWatch for: A $15 credit purchase is required before platform access; no free trial\n\n\n## Why the edge\n\n### Reliability: Together AI Inference +29\n\n- Tencent Cloud TokenHub (46): Hosted reading. No public status page was found. status.cloud.tencent.com did not answer and the Tencent Cloud health dashboard documentation answered with a bot check (0). With no page there is no incident record to read (5 of 30). The announcements carry one incident, DeepSeek's directly supplied models unavailable from 9:06 to 13:04 Beijing time on 15 October 2026 after a fault at DeepSeek, compensated with vouchers. Rate limits are per model, shown in the console and returned by DescribeModelQuota. The public docs give numbers only for batch jobs (20 created a minute, 10 active), image models (5 concurrent) and DeepSeek V4 Flash and Pro (2,500 and 500 concurrent), with the rules for self-serve increases (8 of 15). Six 429 codes separate RPM, TPM, TPD, concurrency and upstream capacity, 429s may carry `Retry-After` and the docs advise exponential backoff. No idempotency guidance, though inference calls are not writes (13 of 15). The TokenHub SLA promises 99.5% monthly availability with vouchers of 10, 25 or 50 per cent of the month's fee. It excludes free use and third-party deployed models such as DeepSeek's directly supplied ones (10). Generally available since 7 April 2026, with some models marked preview (10).\n- Together AI Inference (75): Graded as listed, on the hosted API lines. Public Better Stack status page at status.together.ai with a component for each serverless model plus the website and playground (20). The page shows 90 daily ticks per component, read on 1 November 2026 for 4 August to 1 November, and no incident was posted in that time (the feed's newest items are maintenance windows in April and July 2026). Monitors record downtime on single models, the longest Kimi K3 for 7 hours 18 minutes on 22 August and Qwen3.8-2.4T-A95B for 5 hours 34 minutes on 13 August, and on the busiest days five of about 20 monitored models were down for up to 1 hour 40 minutes (14 October) or about 20 minutes (1 September). Each hit one model or a subset of the catalogue, so the record reads as minor incidents only (20). The current serverless page gives no numeric general request ceiling (0). Explicit 429 and 503 backoff guidance (15). Provisioned throughput has a published 99% eligible-request commitment (10). Serverless inference is generally available (10). 20 + 20 + 0 + 15 + 10 + 10 = 75.\n\n### Schema \u0026 documentation: Together AI Inference +20\n\n- Tencent Cloud TokenHub (73): Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use `deepseek-v3`, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry `/v1`, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15).\n- Together AI Inference (93): Public OpenAPI 3.1 (25), llms.txt and Markdown docs (10), endpoint and model-capability guidance (16 of 20), typed inputs and constraints (13 of 15), examples and documented errors (14 of 15), and versioned endpoints with a dated changelog (15).\n\n### Transparency \u0026 trust: Together AI Inference +20\n\n- Tencent Cloud TokenHub (54): Closed service under the TokenHub Terms of Service (effective 14 September 2026), the SLA (23 April 2026), a special note on third-party deployed models and the Tencent Cloud Service Agreement, naming Tencent Cloud Computing (Beijing) Co., Ltd. The CLI is Apache-2.0 (18 of 30). The terms and the FAQ agree that inputs are processed on the customer's instructions and not used for training, and clause 2.14 limits retention to what the service needs without periods. The TokenHub privacy policy on privacy.qq.com renders only with JavaScript and was not read (15 of 30). Dated retirement notices, shutdown dates in the model list, a `pre-offline` status in `/v1/models` and a `DiscontinuedAt` field in the control API. Clause 6.3 refunds paid, unused tokens when a third-party model is removed. No minimum notice period is written (13 of 20). Clause 2.13 places processing generally in mainland China for the China site and in Singapore for the international site, and the third-party model list names DeepSeek's Hangzhou company with a link to its terms. No subprocessor list was found (13 of 20).\n- Together AI Inference (74): Proprietary service with published terms and Apache-2.0 SDK (15). Docs distinguish default content storage, training opt-in, organisation ZDR and passthrough models, but default content retention has no fixed duration in the reviewed pages (25 of 30). Public lifecycle policy gives a two-week migration window for breaking model upgrades and 2 or 3 weeks' notice for serverless removals, though removals on 19, 21, 25 and 27 August 2026 were posted only on the day (15 of 20). North American hosting and enterprise residency options are described; full subprocessor locations were not established (10 of 20).\n\n### Payments \u0026 pricing: Tencent Cloud TokenHub +15\n\n- Tencent Cloud TokenHub (35): No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by `thcli auth login`, but only from that account (0).\n- Together AI Inference (20): No machine payment protocol found in the reviewed billing and inference docs (0). Public token and capacity prices (20). No free trial and a $15 minimum first credit purchase (0). Browser account and payment setup required (0).\n\n### Maintenance \u0026 community: Tencent Cloud TokenHub +8\n\n- Tencent Cloud TokenHub (73): Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q\u0026A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and `tencent-tokenhub-cli` 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10).\n- Together AI Inference (65): Graded as listed, on the tool lines. Changelog entries on 22 and 23 October 2026 (Python SDK 3.0, TypeScript SDK 1.0, MiniMax M3.1 Flash on serverless and post-training) (30). 43 dated changelog days and 16 Python SDK tags from 3 August, v2.33.1 to v3.0.0 (20). Support responsiveness not tested (0). Official Python and TypeScript SDKs, both given new majors on 22 October (15). Dependency and CI health not audited (0).\n\n## Score by category\n\n| Category | Weight | Tencent Cloud TokenHub | Together AI Inference | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 46 | 75 | Together AI Inference +29 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 73 | 93 | Together AI Inference +20 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 85 | Together AI Inference +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 71 | 70 | Tencent Cloud TokenHub +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 20 | Tencent Cloud TokenHub +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 73 | 65 | Tencent Cloud TokenHub +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 54 | 74 | Together AI Inference +20 |\n| Negative events | ≤15 | -3 | -3 | |\n| **Total** | | **59.5 · C** | **67.8 · B** | |\n\n## Facts side by side\n\n| Fact | Tencent Cloud TokenHub | Together AI Inference |\n| --- | --- | --- |\n| Kind | Model router | HTTP API |\n| Vendor | Tencent Cloud | Together Computer, Inc. |\n| Hosted endpoint | `https://tokenhub.tencentmaas.com/v1` | `https://api.together.ai/v1` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0 | Proprietary hosted service. The official Python SDK is Apache-2.0; served models retain their own licences. |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-24 | 2026-10-23 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | couldn't be read | no date given |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | 204 npm/wk | 10 stars |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### Tencent Cloud TokenHub\n\nNo score change since it was listed.\n\n### Together AI Inference\n\n- no change on 1 November 2026: new evidence, correction\n- no change on 27 October 2026: checklist\n\n## Verdicts\n\n**Tencent Cloud TokenHub.** Keys can be limited to chosen models, source IPs and token quotas, errors name their source and code, and a 99.5% SLA covers paid use of models Tencent runs. Sign-up needs a Tencent Cloud account with real-name verification, prices are in CNY, no public status page was found, and 18 model retirement notices ran from April to October 2026.\n\n**Together AI Inference.** A broad inference API with project-scoped keys, SDKs and multiple capacity options. Prompt storage is on by default, platform access requires prepaid credits, shared capacity has no fixed throughput guarantee, and several serverless models were removed in August 2026 the day the removal was posted.\n\n## Before you call either\n\n### Tencent Cloud TokenHub\n\n1. Use `https://tokenhub.tencentmaas.com/v1` with keys made for Guangzhou and `https://tokenhub-intl.tencentmaas.com/v1` with keys made for Singapore. Keys do not work across the two\n2. Send the key as `Authorization: Bearer` on the OpenAI paths and as `x-api-key` on `/v1/messages`\n3. Parse `error.code` as a string or a number, since 429 codes can come back as integers, and wait for `Retry-After` before retrying\n4. Take model ids from `GET /v1/models` and watch for `pre-offline`. The quickstart's `deepseek-v3` example is not in the current model list\n5. Expect DeepSeek prices to double on weekdays from 9am to noon and 2pm to 6pm Beijing time, when the peak rate applies\n\n### Together AI Inference\n\n1. Create a project-scoped key and set TOGETHER_API_KEY. Avoid deprecated legacy keys.\n2. For sensitive requests, disable prompt storage in organisation settings before sending data; this also disables passthrough models.\n3. Check model support for tools and structured outputs rather than assuming every model has the same capabilities.\n4. Back off on 429 and 503 responses. Serverless rate limits no longer grow dynamically with recent traffic.\n5. Check the deprecation schedule before choosing a model. Qwen3.8-2.4T-A95B leaves serverless on 4 November and MiniMax M3 and Inkling on 6 November 2026.\n6. Pin the SDK major version. Python SDK 3.0 and TypeScript SDK 1.0 (22 October 2026) drop `/v1` from the base URL and the `beta` paths\n\n## Questions\n\n### Which is better for AI agents, Tencent Cloud TokenHub or Together AI Inference?\n\nTogether AI Inference scores 67.8 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 4 of 7 scored categories. Tencent Cloud TokenHub leads on payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Tencent Cloud TokenHub and Together AI Inference need an API key?\n\nBoth need an API key.\n\n### Can an agent call Tencent Cloud TokenHub and Together AI Inference without installing anything?\n\nYes. Tencent Cloud TokenHub has a hosted endpoint at https://tokenhub.tencentmaas.com/v1 and Together AI Inference at https://api.together.ai/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.json, and with the fewest tokens: https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"tencent-tokenhub\", \"b\": \"together-inference\"}`. From a terminal: `anchor compare tencent-tokenhub together-inference`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json and https://www.anchorterminal.com/api/v1/tools/together-inference.json\n\n## Other comparisons with Tencent Cloud TokenHub or Together AI Inference\n\n- [Claude API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.md)\n- [Claude API vs Together AI Inference](https://www.anchorterminal.com/compare/anthropic-api-vs-together-inference.md)\n- [Antseed vs Together AI Inference](https://www.anchorterminal.com/compare/antseed-vs-together-inference.md)\n- [BlockRun.AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.md)\n- [BlockRun.AI vs Together AI Inference](https://www.anchorterminal.com/compare/blockrun-ai-vs-together-inference.md)\n- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.md)\n- [Cerebras Inference vs Together AI Inference](https://www.anchorterminal.com/compare/cerebras-inference-vs-together-inference.md)\n- [Cloudflare AI Gateway vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub.md)\n- [Cloudflare AI Gateway vs Together AI Inference](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-together-inference.md)\n- [Cloudflare Workers AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub.md)\n- [Cloudflare Workers AI vs Together AI Inference](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-together-inference.md)\n- [Cohere Chat API (Command models) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.md)\n- [Cohere Chat API (Command models) vs Together AI Inference](https://www.anchorterminal.com/compare/cohere-chat-vs-together-inference.md)\n- [DeepInfra vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.md)\n- [DeepInfra vs Together AI Inference](https://www.anchorterminal.com/compare/deepinfra-vs-together-inference.md)\n- [DeepSeek API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.md)\n- [DeepSeek API vs Together AI Inference](https://www.anchorterminal.com/compare/deepseek-api-vs-together-inference.md)\n- [Glimpse vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.md)\n- [Glimpse vs Together AI Inference](https://www.anchorterminal.com/compare/elorian-glimpse-vs-together-inference.md)\n- [Fireworks AI Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.md)\n- [Fireworks AI Inference vs Together AI Inference](https://www.anchorterminal.com/compare/fireworks-inference-vs-together-inference.md)\n- [Gemini Developer API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.md)\n- [Gemini Developer API vs Together AI Inference](https://www.anchorterminal.com/compare/gemini-api-vs-together-inference.md)\n- [GroqCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.md)\n- [GroqCloud vs Together AI Inference](https://www.anchorterminal.com/compare/groq-vs-together-inference.md)\n- [Jais 3 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.md)\n- [Jais 3 vs Together AI Inference](https://www.anchorterminal.com/compare/jais-3-vs-together-inference.md)\n- [Meta Model API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.md)\n- [Meta Model API vs Together AI Inference](https://www.anchorterminal.com/compare/meta-model-api-vs-together-inference.md)\n- [MiniMax API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.md)\n- [MiniMax API vs Together AI Inference](https://www.anchorterminal.com/compare/minimax-api-vs-together-inference.md)\n- [Mistral AI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.md)\n- [Mistral AI API vs Together AI Inference](https://www.anchorterminal.com/compare/mistral-api-vs-together-inference.md)\n- [Muse Spark Open vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.md)\n- [Muse Spark Open vs Together AI Inference](https://www.anchorterminal.com/compare/muse-spark-open-vs-together-inference.md)\n- [Novita AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.md)\n- [Novita AI vs Together AI Inference](https://www.anchorterminal.com/compare/novita-ai-vs-together-inference.md)\n- [OpenAI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.md)\n- [OpenAI API vs Together AI Inference](https://www.anchorterminal.com/compare/openai-api-vs-together-inference.md)\n- [OpenRouter vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.md)\n- [OpenRouter vs Together AI Inference](https://www.anchorterminal.com/compare/openrouter-vs-together-inference.md)\n- [Prism Inference vs Together AI Inference](https://www.anchorterminal.com/compare/prism-inference-vs-together-inference.md)\n- [Router.com (Ramp Router) vs Together AI Inference](https://www.anchorterminal.com/compare/ramp-router-vs-together-inference.md)\n- [Beam 1.0 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.md)\n- [Beam 1.0 vs Together AI Inference](https://www.anchorterminal.com/compare/reflection-beam-vs-together-inference.md)\n- [RouterPlus vs Together AI Inference](https://www.anchorterminal.com/compare/routerplus-vs-together-inference.md)\n- [SambaCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.md)\n- [SambaCloud vs Together AI Inference](https://www.anchorterminal.com/compare/sambanova-vs-together-inference.md)\n- [SiliconFlow vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.md)\n- [SiliconFlow vs Together AI Inference](https://www.anchorterminal.com/compare/siliconflow-vs-together-inference.md)\n- [Simplismart vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.md)\n- [Simplismart vs Together AI Inference](https://www.anchorterminal.com/compare/simplismart-vs-together-inference.md)\n- [StepFun API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.md)\n- [StepFun API vs Together AI Inference](https://www.anchorterminal.com/compare/stepfun-api-vs-together-inference.md)\n- [Together AI Inference vs Vercel AI Gateway](https://www.anchorterminal.com/compare/together-inference-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- [Nemotron 3.5 Super VL vs Together AI Inference](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-together-inference.md)\n- [Prism Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.md)\n- [Antseed vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.md)\n- [Router.com (Ramp Router) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.md)\n- [RouterPlus vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Vercel AI Gateway](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-02", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Tencent Cloud TokenHub vs Together AI Inference", "url": "" } ], "description": "Together AI Inference scores 67.8 (B) to Tencent Cloud TokenHub's 59.5 (C) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Tencent Cloud TokenHub C 59.5", "Together AI Inference B 67.8", "scores" ], "h1": "Tencent Cloud TokenHub vs Together AI Inference", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/tencent-tokenhub-vs-together-inference", "published": "2026-10-01", "section": "tools", "title": "Tencent Cloud TokenHub vs Together AI Inference for AI agents (2026)", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference" }, "tokens": { "markdown": 6100, "slim": 2880 }, "version": 1 }