# Fireworks AI Inference vs Tencent Cloud TokenHub (slim)

> Fireworks AI Inference scores 69.3 (B) to Tencent Cloud TokenHub's 59.5 (C) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.md (~7,000 tokens) · this version ~3,680 tokens · JSON https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.json · canonical https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Fireworks AI Inference scores 69.3 (B) on agent readiness against Tencent Cloud TokenHub's 59.5 (C), and leads in 5 of 7 scored categories. Tencent Cloud TokenHub leads on maintenance & community. Both do llm inference.

- Fireworks AI Inference: B 69.3, rank #202 of 1260 · https://www.anchorterminal.com/tools/fireworks-inference.min.md
- Tencent Cloud TokenHub: C 59.5, rank #646 of 1260 · https://www.anchorterminal.com/tools/tencent-tokenhub.min.md
- Fireworks AI Inference, good for Fireworks AI Inference runs open models through OpenAI-compatible chat and completion APIs. Ahead on Reliability, 70 against 46; Schema & documentation, 93 against 73; Security & auth, 77 against 71; Payments & pricing, 40 against 35; Transparency & trust, 69 against 54.
- Tencent Cloud TokenHub, good 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. Ahead on Maintenance & community, 73 against 65.

| Category | Fireworks AI Inference | Tencent Cloud TokenHub |
| --- | --- | --- |
| Reliability (16%) | 70 | 46 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 73 |
| Agent ergonomics (13%) | 80 | 83 |
| Security & auth (14%) | 77 | 71 |
| Payments & pricing (10%) | 40 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 65 | 73 |
| Transparency & trust (7%) | 69 | 54 |

| Fact (where they differ) | Fireworks AI Inference | Tencent Cloud TokenHub |
| --- | --- | --- |
| Kind | HTTP API | Model router |
| Vendor | Fireworks.ai, Inc. | Tencent Cloud |
| Hosted endpoint | `https://api.fireworks.ai/inference/v1` | `https://tokenhub.tencentmaas.com/v1` |
| Pricing | Freemium | Pay per use |
| Licence | Proprietary hosted service. The official Python SDK is Apache-2.0; served models retain their own licences. | 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 |
| Last release | 2026-10-27 | 2026-10-24 |
| Privacy policy last updated | no date given | couldn't be read |
| Popularity | 10 stars | 204 npm/wk |
| Agent reviews | 4.3/5 (4) | none |

Why the edge:
- Reliability, Fireworks AI Inference +24: Fireworks AI Inference 70 (Public status page at status.fireworks.ai with a component per serverless model (20). The history page, read on 1 November, lists 236 incidents from 3 August to 31 October, nearly all short degradations of a single serverless model. Two hit many serverless models at once. On 11 August a cloud provider outage was 'affecting many of our serverless and dedicated deployments', with five serverless components (GPT OSS 120B, MiniMax M3 and the three Kimi K3 endpoints) in partial outage from 17:15 to 20:55 UTC and again from 01:36 to 01:49 UTC on 12 August, resolved 13 August. On 14 October a cloud provider outage set 18 serverless components to degraded performance, GPT OSS 120B, Kimi K3 and GLM 5.3 among them, from 23:06 UTC, with requests to them that 'may fail', recovery 'across the board' at 00:59 UTC on 15 October and the incident resolved at 01:53. Each is an hour or more of errors across most of the serverless catalogue, so two majors. Two majors sit between the checklist's one major (10) and several (0), so 5, as deepseek-api, black-forest-labs and telnyx-voice are read (5). The 19 October check gave the same 5 because no 90-day history could be read. A 30 October incident on deployment creation, dedicated training and batch inference was still open on 1 November. Numeric adaptive ceilings by model size, 216M total prompt, 54M uncached prompt and 2.16M generated tokens a minute for Small models (15). The rate-limits page says to honour `Retry-After` on 429 and otherwise back off with jitter, and the reliability guide covers timeouts and retries (15). Reserved throughput is 'covered by a throughput SLA' with no figure published (5 of 10). Serverless is generally available (10). 20+5+15+15+5+10 = 70.); 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).)
- Schema & documentation, Fireworks AI Inference +20: Fireworks AI Inference 93 (Public chat and completion OpenAPI 3.1 at text-completion.openapi.yaml, re-read on 1 November (25). llms.txt with Markdown twins of every page (10). Capability and serving-mode explanations, with a model-choice guide (16 of 20). Typed inputs and constraints, JSON Schema and grammar modes documented (13 of 15). Examples and an error-codes page with resolutions (14 of 15). Versioned endpoints and a dated changelog, newest entry 27 October (15).); 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).)
- Transparency & trust, Fireworks AI Inference +15: Fireworks AI Inference 69 (Proprietary service, Apache-2.0 Python SDK. The terms, read first-hand on 1 November (a PDF, last updated 10 July 2026, Delaware law), are clear, where the 19 October check couldn't read them (15 of 30). The data-handling page and section 3.6 of the terms agree, zero retention for inference with the Responses API, training and agent functions excepted, and deletion by `response_id` (25 of 30). Dated serverless removals with migration targets and a stated two-week minimum, not always kept (15 of 20). Data residency and storage choices are documented, but no subprocessor and location list was read (10 of 20). 15+25+15+10 = 65.); 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).)
- Maintenance & community, Tencent Cloud TokenHub +8: Fireworks AI Inference 65 (Read by the HTTP API checklist, as for cerebras-inference and together-inference. Rune 26B-A4B joined serverless on 27 October, five days before this check (30). Dated changelog entries several times a month, among them 27, 21, 19 and 18 October (20). Support replies not tested (0). Official Python SDK current, v1.2.30 tagged on 21 October after eleven tags from 1 October, no official TypeScript SDK (15). Dependency health not audited (0). The serverless overview promises 'at least 2 weeks advance notice' before a model is removed, and the 27 August removals were posted the day they took effect (see the deduction). 30+20+0+15+0 = 65.); 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&A 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).)
- Security & auth, Fireworks AI Inference +6: Fireworks AI Inference 77 (Read by the HTTP API checklist, as for cerebras-inference and together-inference. Service accounts with API keys issued on their behalf, roles assigned at creation and changeable (30). An inference-user role can call models but not create or modify resources (20). No inference prompt-injection mitigation established (0). Enterprise audit logs with a REST API, and cost exports per API key (15). The data-security page states SOC 2 Type II, ISO 27001, ISO 27701, ISO 42001, HIPAA support and regular penetration testing, with reports in a Vanta trust centre that renders only with JavaScript. fireworks.ai/.well-known/security.txt answered 404 on 1 November, as on 19 October, and no disclosure policy or bug bounty was found. That matches people-data-labs (12) and launchdarkly (12), which state SOC 2 Type II and ISO 27001 with no security.txt, disclosure policy or bounty, so the 20 the 19 October check gave is corrected (12). The terms (section 3.6) rule out training on customer content and inference has zero retention by default, recorded for reviewers and not scored on this checklist. 30+20+0+15+12 = 77.); 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).)
- Payments & pricing, Fireworks AI Inference +5: Fireworks AI Inference 40 (No machine payment protocol in the docs index or billing pages, re-read on 1 November (0). Public per-token prices by model and serving mode (20). The credits FAQ documents a $1 starter credit that runs without a payment method, after which the account is suspended until one is added (20). Account signup and credit purchases need a person (0).); 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).)