{ "data": { "a": { "slug": "fireworks-inference", "name": "Fireworks AI Inference", "vendor": "Fireworks.ai, Inc.", "vendorUrl": "https://fireworks.ai", "kind": "http-api", "category": "inference", "summary": "Fireworks AI Inference runs open models through OpenAI-compatible chat and completion APIs. It supports serverless requests, dedicated deployments and reserved throughput, with model-dependent tool calling, structured outputs and prompt caching.", "url": "https://www.anchorterminal.com/tools/fireworks-inference", "markdownUrl": "https://www.anchorterminal.com/tools/fireworks-inference.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fireworks-inference.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fireworks-inference.json", "dns": "fireworks-inference.grade.anchorterminal.com", "repo": "https://github.com/fw-ai-external/python-sdk", "license": "Proprietary hosted service. The official Python SDK is Apache-2.0; served models retain their own licences.", "transports": [ "http" ], "remoteUrl": "https://api.fireworks.ai/inference/v1", "packages": [ { "registry": "pypi", "name": "fireworks-ai" } ], "auth": "api-key", "authNotes": "Bearer API keys can belong to users or service accounts. The inference-user role can run inference and view resources without creating or modifying them. An administrator can create and manage service-account keys.", "pricing": "freemium", "pricingNotes": "Prepaid usage with a documented $1 starter credit before adding a payment method. Standard DeepSeek V4.1 Flash is $0.30 input, $0.006 cached input and $1.20 output per million tokens. Batch is half price, and Priority, Fast, US-only and dedicated rates differ. GPT OSS 120B leaves serverless on 7 November 2026.", "priceSummary": "Freemium", "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.fireworks.ai", "llmsTxt": "https://docs.fireworks.ai/llms.txt", "openapi": "https://docs.fireworks.ai/text-completion.openapi.yaml", "capabilities": [ "inference.llm", "inference.open-weights" ], "tags": [ "official", "http-api", "inference", "api-key", "openapi", "llms-txt", "freemium" ], "lastRelease": "2026-10-27", "graded": true, "anchor": { "graded": true, "score": 69.3, "grade": "B", "agentReady": false, "rank": 202, "ranked": true, "rankOf": 1260, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 65, "payments": 40, "reliability": 70, "schema": 93, "security": 77, "transparency": 69 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -3, "negativeNotes": [ "On 2026-08-27 Fireworks removed MiniMax M2.7, GPT OSS 20B, Kimi K2.6 Turbo and Fast, Kimi K2.7 Code Fast and DeepSeek V4 Pro from serverless 'effective August 27, 2026', in a changelog entry posted that day, against its own stated minimum of two weeks' notice (https://docs.fireworks.ai/updates/changelog)" ], "verdict": "Inference-only service accounts, published per-token prices, zero retention for chat inference and terms that rule out training on customer content support production use. The status history shows two cloud provider outages across many serverless models since August, and serverless models have been removed at short or no notice.", "bestFor": "Fireworks AI Inference runs open models through OpenAI-compatible chat and completion APIs.", "strengths": [ "An inference-user role limits service accounts to calling models, with no rights to create or change resources", "Chat inference keeps no prompts or outputs by default, and the terms rule out training on customer content", "Public OpenAPI 3.1, per-model prices, and 429 guidance that names Retry-After and backoff with jitter", "Prompt caching on by default for every serverless model, and batch at half price" ], "weaknesses": [ "Cloud provider outages on 11 August and 14 October hit many serverless models for hours", "Five serverless models were removed on 27 August the day the change was posted, despite a stated two-week minimum", "The Responses API stores conversations for up to 30 days by default unless store is false", "No security.txt, disclosure policy or bug bounty found, and the trust centre needs JavaScript" ], "agentNotes": [ "Use an inference-user service account and keep FIREWORKS_API_KEY in a secrets manager.", "Use https://api.fireworks.ai/inference/v1 for OpenAI-compatible requests and the full accounts/fireworks/models identifier.", "Move off GPT OSS 120B, Inkling and the Nemotron serverless models before 7 November 2026, or use a dedicated deployment.", "Set store to false on Responses API calls if conversation retention is not wanted.", "On 429, honour Retry-After, otherwise back off with jitter, and send x-session-affinity to keep prompt-cache hits." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 4.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": 69.3 } ], "editorialScores": { "ergonomics": 80, "maintenance": 65, "payments": 40, "reliability": 70, "schema": 93, "security": 77, "transparency": 65 }, "provenanceScore": 73, "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.fireworks.ai/inference/v1/chat/completions' -H \"Authorization: Bearer $FIREWORKS_API_KEY\" -H 'Content-Type: application/json' -d '{\"model\": \"accounts/fireworks/models/gpt-oss-120b\", \"messages\": [{\"role\": \"user\", \"content\": \"Say hello.\"}], \"max_tokens\": 128}'" }, "letme": { "capability": "https://letme.dev/inference.llm", "tool": "https://letme.dev/fireworks-inference" }, "sameCompany": [ "fireworks-fine-tuning" ], "area": "models", "unitPrices": [ { "item": "DeepSeek V4.1 Flash input", "unit": "1m-tokens", "usd": 0.3, "note": "Serverless standard rate, per million tokens, checked 1 November 2026" }, { "item": "DeepSeek V4.1 Flash output", "unit": "1m-tokens", "usd": 1.2, "note": "Serverless standard rate, per million tokens, checked 1 November 2026" } ], "provenance": { "legalEntity": "Fireworks.ai, Inc.", "domain": "fireworks.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://fireworks.ai/terms-of-service", "privacy": "https://fireworks.ai/privacy-policy", "statusPage": "https://status.fireworks.ai", "changelog": "https://docs.fireworks.ai/updates/changelog", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "Legal identity from the terms of service (last updated 10 July 2026), which name Fireworks.ai, Inc. and Delaware law, read on 1 November 2026. Domain registration was not checked.", "The SDK repository is not the source for the hosted inference service.", "fireworks.ai/.well-known/security.txt returned 404 on 1 November 2026." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/fireworks-inference.json", "live": { "slug": "fireworks-inference", "probe": { "target": "https://api.fireworks.ai/inference/v1", "method": "get", "lastAt": "2026-11-02T00:56:04.390676232Z", "lastOk": true, "lastStatus": 404, "lastMs": 6, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 12, "p95ms24h": 57, "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": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "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.fireworks.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-02T01:00:49.208430698Z" }, "versions": [ { "registry": "github", "name": "fw-ai-external/python-sdk", "version": "v1.2.30", "released": "2026-10-21", "seenAt": "2026-11-01T16:59:16.103653087Z" }, { "registry": "pypi", "name": "fireworks-ai", "version": "1.2.30", "released": "2026-10-21", "seenAt": "2026-11-01T16:59:15.989299007Z" } ], "githubStars": 11, "pypiWeekly": 367886, "securityTxt": { "url": "https://fireworks.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:42:03.024485038Z" }, "llmsTxt": { "url": "https://docs.fireworks.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:13:50.048948451Z" }, "domain": { "domain": "fireworks.ai", "registered": "2020-03-11", "source": "https://rdap.identitydigital.services/rdap/domain/fireworks.ai", "checkedAt": "2026-11-01T14:15:39.714966536Z" }, "github": { "repo": "fw-ai-external/python-sdk", "checkedAt": "2026-10-26T07:04:25.904865648Z", "stars": 10, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-23T18:19:52Z", "openIssues": 2, "openPRs": 2, "issuesOpened90d": 1, "issuesClosed90d": 0, "prsMerged90d": 26, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-21T21:12:19Z" }, "replies": { "sampled": 3, "unanswered": 2, "medianDays": 17.9 } }, "updatedAt": "2026-11-02T01:00:49.208430698Z" } }, "answer": "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 \u0026 community.", "b": { "slug": "tencent-tokenhub", "name": "Tencent Cloud TokenHub", "vendor": "Tencent Cloud", "vendorUrl": "https://cloud.tencent.com", "kind": "router", "category": "inference", "summary": "Tencent Cloud TokenHub is a hosted model gateway serving Tencent's Hy models and third-party models such as DeepSeek, Kimi, GLM and MiniMax through OpenAI-compatible and Anthropic-compatible endpoints in Guangzhou and Singapore, with per-key scopes and quotas.", "url": "https://www.anchorterminal.com/tools/tencent-tokenhub", "markdownUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json", "dns": "tencent-tokenhub.grade.anchorterminal.com", "repo": "https://github.com/TencentCloud/THCLI", "license": "Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://tokenhub.tencentmaas.com/v1", "packages": [ { "registry": "npm", "name": "tencent-tokenhub-cli" } ], "auth": "api-key", "authNotes": "Bearer API key from the TokenHub console, or `x-api-key` on the Anthropic-style `/v1/messages`. Keys are long-lived, belong to one region (Guangzhou or Singapore), can be limited to chosen models and inference services, up to 200 IP ranges and token quotas, and can be disabled or deleted. They can also be created through the CreateApiKey control-plane call with signed Tencent Cloud credentials, or by `thcli auth login`. The account needs real-name verification first.", "pricing": "usage", "pricingNotes": "Pay per token in CNY, billed hourly. Hy4 preview costs 6 CNY in, 18 CNY out and 0.3 CNY cached per 1M tokens, Hy3 1, 4 and 0.25 CNY. DeepSeek models double at weekday peak hours. Batch is half price for Hy3 and Hy4 preview. Each account gets 1M free tokens per language model for a year, in a campaign to 31 December 2026. Token Plan subscriptions run from 28 to 599 CNY a month (https://cloud.tencent.com/document/product/1823/130055, checked 2026-11-01).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs table of contents, the billing pages or the API usage page. Payment is from a Tencent Cloud account balance, billed hourly (checked 2026-11-01).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 204, "pypiWeekly": null, "asOf": "2026-11-01" }, "docsUrl": "https://cloud.tencent.com/document/product/1823/130058", "rateLimitsUrl": "https://cloud.tencent.com/document/product/1823/136028", "llmsTxt": "https://cloud.tencent.com/document/product/1823/llms.txt", "capabilities": [ "inference.router", "inference.llm", "inference.open-weights", "embed.text", "embed.multimodal", "image.generate", "video.generate", "speech.tts", "speech.stt", "audio.music", "translate.text", "web.search", "obs.gateway" ], "tags": [ "hosted", "router", "usage-based", "free-credit", "openai-compatible", "anthropic-compatible", "llms-txt", "cli", "sla", "batch", "bug-bounty", "no-status-page", "regional-endpoints", "singapore", "chinese", "subscription" ], "lastRelease": "2026-10-24", "graded": true, "anchor": { "graded": true, "score": 59.5, "grade": "C", "agentReady": false, "rank": 646, "ranked": true, "rankOf": 1260, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 73, "payments": 35, "reliability": 46, "schema": 73, "security": 71, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -3, "negativeNotes": [ "2026-10-17. -3, a breaking change without notice. DeepSeek-V4.1-Flash (directly supplied) was moved to its 1017 version under the same model ids and prices on 17 October 2026, and the notice came two days later (https://cloud.tencent.com/announce/detail/2516). Callers pinned to the id got a different model's behaviour with no warning. One term at the floor: the API didn't change. The founder's decision, 1 November 2026." ], "verdict": "Keys can be limited to chosen models, source IPs and token quotas, errors name their source and code, and a 99.5% SLA covers paid use of models Tencent runs. Sign-up needs a Tencent Cloud account with real-name verification, prices are in CNY, no public status page was found, and 18 model retirement notices ran from April to October 2026.", "bestFor": "Teams in or near Tencent Cloud that want one key and bill for Tencent's Hy models and Chinese open-weight models (DeepSeek, Kimi, GLM, MiniMax, Qwen, MiMo) with per-key limits and CNY billing.", "strengths": [ "API keys can be limited to chosen models and inference services, up to 200 source IP ranges, and daily, monthly or total token quotas", "One base URL answers OpenAI Chat Completions, OpenAI Responses and Anthropic Messages calls, and `GET /v1/models` marks models due to retire as `pre-offline`", "Error bodies carry a six-digit code, English and Chinese messages, the source (client, gateway or upstream) and a request ID, and 429s can carry `Retry-After`", "A published SLA promises 99.5% monthly availability with voucher credits of 10 to 50 per cent of the month's fee, for paid use of models Tencent runs", "Per-call audit logs (request ID, key, client IP, status, tokens, latency) can be delivered to the customer's own Tencent Cloud CLS log service" ], "weaknesses": [ "Sign-up needs a Tencent Cloud account with real-name verification. The international site answered with a bot check, so access from outside China was not established", "No public status page was found. A four-hour outage of DeepSeek's directly supplied models on 15 October 2026 appears only as a compensation notice", "18 model retirement notices from 21 April to 22 October 2026. Those read gave 21 to 33 days, and eligible callers are switched to a successor at its price", "DeepSeek's directly supplied models send inputs to DeepSeek under its own terms, and the TokenHub SLA does not cover them", "Per-model RPM and TPM limits for chat models are shown in the console and the quota API, not in the public docs" ], "agentNotes": [ "Use `https://tokenhub.tencentmaas.com/v1` with keys made for Guangzhou and `https://tokenhub-intl.tencentmaas.com/v1` with keys made for Singapore. Keys do not work across the two", "Send the key as `Authorization: Bearer` on the OpenAI paths and as `x-api-key` on `/v1/messages`", "Parse `error.code` as a string or a number, since 429 codes can come back as integers, and wait for `Retry-After` before retrying", "Take model ids from `GET /v1/models` and watch for `pre-offline`. The quickstart's `deepseek-v3` example is not in the current model list", "Expect DeepSeek prices to double on weekdays from 9am to noon and 2pm to 6pm Beijing time, when the peak rate applies" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.5 } ], "editorialScores": { "ergonomics": 83, "maintenance": 73, "payments": 35, "reliability": 46, "schema": 73, "security": 71, "transparency": 59 }, "provenanceScore": 49, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm i -g tencent-tokenhub-cli", "http": "curl https://tokenhub.tencentmaas.com/v1/models \\\n -H \"Authorization: Bearer $TOKENHUB_API_KEY\"", "claudeCode": "{\n \"env\": {\n \"ANTHROPIC_BASE_URL\": \"https://tokenhub.tencentmaas.com\",\n \"ANTHROPIC_AUTH_TOKEN\": \"YOUR_API_KEY\",\n \"ANTHROPIC_MODEL\": \"hy3\"\n }\n}" }, "letme": { "capability": "https://letme.dev/inference.router", "tool": "https://letme.dev/tencent-tokenhub" }, "area": "models", "provenance": { "legalEntity": "Tencent Cloud Computing (Beijing) Co., Ltd. (腾讯云计算（北京）有限责任公司)", "domain": "tencentmaas.com", "domainRegistered": "2026-03-13", "endpointOnVendorDomain": false, "terms": "https://cloud.tencent.com/document/product/301/129852", "privacy": "https://privacy.qq.com/document/preview/91d5fd3c98ce4468ae462ac59233bba2", "statusPage": "", "changelog": "https://cloud.tencent.com/document/product/1823/130675", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "The TokenHub Terms of Service (effective 14 September 2026), the SLA (effective 23 April 2026) and the special note on third-party deployed models (effective 14 September 2026) name 腾讯云计算（北京）有限责任公司. The docs footer also names 深圳市腾讯计算机系统有限公司 as ICP licence holder.", "The TokenHub privacy policy is linked from the docs to privacy.qq.com, which renders only with JavaScript, so it was not read. privacy.qq.com has no robots.txt (404).", "No public status page was found. status.cloud.tencent.com did not answer, and the Tencent Cloud health dashboard documentation answered with a bot check.", "security.txt answered 404 on cloud.tencent.com, www.tencent.com and tokenhub.tencentmaas.com. Tencent's bug bounty policy at en.security.tencent.com lists Tencent Cloud in scope.", "RDAP at Verisign gives tencentmaas.com a registration date of 13 March 2026 with no registrant. The API answers at tokenhub.tencentmaas.com and tokenhub-intl.tencentmaas.com, named in Tencent Cloud's API usage page.", "cloud.tencent.com allows these docs in robots.txt. Its pages answered some requests with a JavaScript bot check, which was not passed. The pages were read when a later plain request returned them. www.tencentcloud.com answered robots.txt with a bot check, so the international site was not read." ], "score": 49 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tencent-tokenhub.json", "live": { "slug": "tencent-tokenhub", "probe": { "target": "https://tokenhub.tencentmaas.com/v1", "method": "get", "lastAt": "2026-11-02T00:56:24.101434531Z", "lastOk": true, "lastStatus": 404, "lastMs": 795, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 826, "p95ms24h": 1067, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-11-01", "probes": 18, "ok": 18 }, { "date": "2026-11-02", "probes": 10, "ok": 10 } ] }, "updatedAt": "2026-11-02T00:56:24.101434531Z" } }, "edges": [ { "by": 24, "category": "reliability", "leads": "fireworks-inference", "name": "Reliability", "reasons": { "a": "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.", "b": "Hosted reading. No public status page was found. status.cloud.tencent.com did not answer and the Tencent Cloud health dashboard documentation answered with a bot check (0). With no page there is no incident record to read (5 of 30). The announcements carry one incident, DeepSeek's directly supplied models unavailable from 9:06 to 13:04 Beijing time on 15 October 2026 after a fault at DeepSeek, compensated with vouchers. Rate limits are per model, shown in the console and returned by DescribeModelQuota. The public docs give numbers only for batch jobs (20 created a minute, 10 active), image models (5 concurrent) and DeepSeek V4 Flash and Pro (2,500 and 500 concurrent), with the rules for self-serve increases (8 of 15). Six 429 codes separate RPM, TPM, TPD, concurrency and upstream capacity, 429s may carry `Retry-After` and the docs advise exponential backoff. No idempotency guidance, though inference calls are not writes (13 of 15). The TokenHub SLA promises 99.5% monthly availability with vouchers of 10, 25 or 50 per cent of the month's fee. It excludes free use and third-party deployed models such as DeepSeek's directly supplied ones (10). Generally available since 7 April 2026, with some models marked preview (10)." }, "scores": { "a": 70, "b": 46 } }, { "by": 20, "category": "schema", "leads": "fireworks-inference", "name": "Schema \u0026 documentation", "reasons": { "a": "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).", "b": "Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use `deepseek-v3`, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry `/v1`, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15)." }, "scores": { "a": 93, "b": 73 } }, { "by": 15, "category": "transparency", "leads": "fireworks-inference", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Closed service under the TokenHub Terms of Service (effective 14 September 2026), the SLA (23 April 2026), a special note on third-party deployed models and the Tencent Cloud Service Agreement, naming Tencent Cloud Computing (Beijing) Co., Ltd. The CLI is Apache-2.0 (18 of 30). The terms and the FAQ agree that inputs are processed on the customer's instructions and not used for training, and clause 2.14 limits retention to what the service needs without periods. The TokenHub privacy policy on privacy.qq.com renders only with JavaScript and was not read (15 of 30). Dated retirement notices, shutdown dates in the model list, a `pre-offline` status in `/v1/models` and a `DiscontinuedAt` field in the control API. Clause 6.3 refunds paid, unused tokens when a third-party model is removed. No minimum notice period is written (13 of 20). Clause 2.13 places processing generally in mainland China for the China site and in Singapore for the international site, and the third-party model list names DeepSeek's Hangzhou company with a link to its terms. No subprocessor list was found (13 of 20)." }, "scores": { "a": 69, "b": 54 } }, { "by": 8, "category": "maintenance", "leads": "tencent-tokenhub", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q\u0026A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and `tencent-tokenhub-cli` 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10)." }, "scores": { "a": 65, "b": 73 } }, { "by": 6, "category": "security", "leads": "fireworks-inference", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Router, read on the model lines. Bearer keys can be limited to chosen models and inference services, up to 200 source IP ranges and daily, monthly or total token quotas, can be disabled or deleted, and can be created in code through CreateApiKey with signed Tencent Cloud credentials. Keys are long-lived with no expiry setting or built-in rotation (26 of 30). Clause 2.17 of the terms says inputs are not used to train Tencent Cloud's own models, and the FAQ says data is not used for training. Inputs to third-party deployed models (DeepSeek's directly supplied ones) go to DeepSeek under its terms (14 of 20). Clause 2.14 keeps data only as long as the service needs, with no periods stated. When a customer asks for generated content without AI labels, Tencent Cloud keeps logs of who received it for at least six months. No zero-retention option was found (7 of 15). Per-call audit logs (request ID, key, client IP, status, tokens, latency) and optional full call logs go to the customer's CLS, billed separately, with usage by key and a monitoring dashboard (14 of 15). No security.txt on cloud.tencent.com, www.tencent.com or tokenhub.tencentmaas.com (404). Tencent's bug bounty through TSRC lists Tencent Cloud in scope. No certification for TokenHub was checked (10 of 20)." }, "scores": { "a": 77, "b": 71 } }, { "by": 5, "category": "payments", "leads": "fireworks-inference", "name": "Payments \u0026 pricing", "reasons": { "a": "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).", "b": "No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by `thcli auth login`, but only from that account (0)." }, "scores": { "a": 40, "b": 35 } } ], "facts": [ { "a": "HTTP API", "b": "Model router", "name": "Kind" }, { "a": "Fireworks.ai, Inc.", "b": "Tencent Cloud", "name": "Vendor" }, { "a": "https://api.fireworks.ai/inference/v1", "b": "https://tokenhub.tencentmaas.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service. The official Python SDK is Apache-2.0; served models retain their own licences.", "b": "Proprietary service under the TokenHub Terms of Service, the TokenHub SLA and the Tencent Cloud Service Agreement, with a special note for third-party deployed models. The `tencent-tokenhub-cli` package is Apache-2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-27", "b": "2026-10-24", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no date given", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "10 stars", "b": "204 npm/wk", "name": "Popularity" }, { "a": "4.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 community.", "question": "Which is better for AI agents, Fireworks AI Inference or Tencent Cloud TokenHub?" }, { "answer": "Both need an API key.", "question": "Do Fireworks AI Inference and Tencent Cloud TokenHub need an API key?" }, { "answer": "Yes. Fireworks AI Inference has a hosted endpoint at https://api.fireworks.ai/inference/v1 and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.", "question": "Can an agent call Fireworks AI Inference and Tencent Cloud TokenHub without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 46", "Schema \u0026 documentation, 93 against 73", "Security \u0026 auth, 77 against 71", "Payments \u0026 pricing, 40 against 35", "Transparency \u0026 trust, 69 against 54" ], "also": null, "goodFor": "Fireworks AI Inference runs open models through OpenAI-compatible chat and completion APIs.", "slug": "fireworks-inference", "watchFor": "Cloud provider outages on 11 August and 14 October hit many serverless models for hours" }, { "aheadOn": [ "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" } ], "history": { "fireworks-inference": [ { "causes": [ "evidence", "correction", "event" ], "date": "2026-11-01", "delta": -4.2, "from": 73.5, "fromGrade": "BB", "to": 69.3, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-28", "delta": 0, "from": 73.5, "fromGrade": "BB", "to": 73.5, "toGrade": "BB" } ], "tencent-tokenhub": null }, "job": { "capability": "inference.llm", "name": "LLM inference" }, "others": [ { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-fireworks-inference.json", "title": "Claude API vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-fireworks-inference" }, { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.json", "title": "Claude API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-fireworks-inference.json", "title": "Antseed vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/antseed-vs-fireworks-inference" }, { "json": "https://www.anchorterminal.com/compare/blockrun-ai-vs-fireworks-inference.json", "title": "BlockRun.AI vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-fireworks-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/cerebras-inference-vs-fireworks-inference.json", "title": "Cerebras Inference vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-fireworks-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/cloudflare-ai-gateway-vs-fireworks-inference.json", "title": "Cloudflare AI Gateway vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-fireworks-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-workers-ai-vs-fireworks-inference.json", "title": "Cloudflare Workers AI vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-fireworks-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/cohere-chat-vs-fireworks-inference.json", "title": "Cohere Chat API (Command models) vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-fireworks-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/deepinfra-vs-fireworks-inference.json", "title": "DeepInfra vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-fireworks-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/deepseek-api-vs-fireworks-inference.json", "title": "DeepSeek API vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-fireworks-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/elorian-glimpse-vs-fireworks-inference.json", "title": "Glimpse vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-fireworks-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/fireworks-inference-vs-gemini-api.json", "title": "Fireworks AI Inference vs Gemini Developer API", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-gemini-api" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-groq.json", "title": "Fireworks AI Inference vs GroqCloud", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-groq" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-jais-3.json", "title": "Fireworks AI Inference vs Jais 3", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-jais-3" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-meta-model-api.json", "title": "Fireworks AI Inference vs Meta Model API", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-meta-model-api" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-minimax-api.json", "title": "Fireworks AI Inference vs MiniMax API", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-minimax-api" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-mistral-api.json", "title": "Fireworks AI Inference vs Mistral AI API", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-mistral-api" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-muse-spark-open.json", "title": "Fireworks AI Inference vs Muse Spark Open", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-muse-spark-open" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-nemotron-3-5-super-vl.json", "title": "Fireworks AI Inference vs Nemotron 3.5 Super VL", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-nemotron-3-5-super-vl" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-novita-ai.json", "title": "Fireworks AI Inference vs Novita AI", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-novita-ai" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-openai-api.json", "title": "Fireworks AI Inference vs OpenAI API", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-openai-api" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-openrouter.json", "title": "Fireworks AI Inference vs OpenRouter", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-openrouter" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-prism-inference.json", "title": "Fireworks AI Inference vs Prism Inference", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-prism-inference" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-ramp-router.json", "title": "Fireworks AI Inference vs Router.com (Ramp Router)", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-ramp-router" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-reflection-beam.json", "title": "Fireworks AI Inference vs Beam 1.0", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-reflection-beam" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-routerplus.json", "title": "Fireworks AI Inference vs RouterPlus", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-sambanova.json", "title": "Fireworks AI Inference vs SambaCloud", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-sambanova" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-siliconflow.json", "title": "Fireworks AI Inference vs SiliconFlow", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-siliconflow" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-simplismart.json", "title": "Fireworks AI Inference vs Simplismart", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-stepfun-api.json", "title": "Fireworks AI Inference vs StepFun API", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-stepfun-api" }, { "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/fireworks-inference-vs-vercel-ai-gateway.json", "title": "Fireworks AI Inference vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-vercel-ai-gateway" }, { "json": "https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.json", "title": "Gemini Developer API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.json", "title": "GroqCloud vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.json", "title": "Jais 3 vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.json", "title": "Meta Model API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.json", "title": "MiniMax API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.json", "title": "Mistral AI API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.json", "title": "Muse Spark Open vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.json", "title": "Novita AI vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.json", "title": "OpenAI API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.json", "title": "OpenRouter vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.json", "title": "Beam 1.0 vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.json", "title": "SambaCloud vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.json", "title": "SiliconFlow vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.json", "title": "Simplismart vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.json", "title": "StepFun API vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.json", "title": "Tencent Cloud TokenHub vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub.json", "title": "Nemotron 3.5 Super VL vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.json", "title": "Prism Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.json", "title": "Antseed vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.json", "title": "Router.com (Ramp Router) vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.json", "title": "RouterPlus vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.json", "title": "Tencent Cloud TokenHub vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway" } ], "panel": null, "scores": [ { "by": 24, "edge": "fireworks-inference", "fireworks-inference": 70, "key": "reliability", "name": "Reliability", "tencent-tokenhub": 46, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 20, "edge": "fireworks-inference", "fireworks-inference": 93, "key": "schema", "name": "Schema \u0026 documentation", "tencent-tokenhub": 73, "weight": 13 }, { "by": 3, "edge": "tencent-tokenhub", "fireworks-inference": 80, "key": "ergonomics", "name": "Agent ergonomics", "tencent-tokenhub": 83, "weight": 13 }, { "by": 6, "edge": "fireworks-inference", "fireworks-inference": 77, "key": "security", "name": "Security \u0026 auth", "tencent-tokenhub": 71, "weight": 14 }, { "by": 5, "edge": "fireworks-inference", "fireworks-inference": 40, "key": "payments", "name": "Payments \u0026 pricing", "tencent-tokenhub": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "edge": "tencent-tokenhub", "fireworks-inference": 65, "key": "maintenance", "name": "Maintenance \u0026 community", "tencent-tokenhub": 73, "weight": 7 }, { "by": 15, "edge": "fireworks-inference", "fireworks-inference": 69, "key": "transparency", "name": "Transparency \u0026 trust", "tencent-tokenhub": 54, "weight": 7 } ], "summary": "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 \u0026 community. Both do llm inference.", "tasks": null, "tutorials": [], "verdicts": { "fireworks-inference": "Inference-only service accounts, published per-token prices, zero retention for chat inference and terms that rule out training on customer content support production use. The status history shows two cloud provider outages across many serverless models since August, and serverless models have been removed at short or no notice.", "tencent-tokenhub": "Keys can be limited to chosen models, source IPs and token quotas, errors name their source and code, and a 99.5% SLA covers paid use of models Tencent runs. Sign-up needs a Tencent Cloud account with real-name verification, prices are in CNY, no public status page was found, and 18 model retirement notices ran from April to October 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub", "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.min.md" }, "markdown": "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 \u0026 community. Both do llm inference.\n\n- Fireworks AI Inference: grade B, 69.3/100, rank #202 of 1260. Markdown https://www.anchorterminal.com/tools/fireworks-inference.md · JSON https://www.anchorterminal.com/api/v1/tools/fireworks-inference.json\n- Tencent Cloud TokenHub: grade C, 59.5/100, rank #646 of 1260. Markdown https://www.anchorterminal.com/tools/tencent-tokenhub.md · JSON https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n- Best model APIs and inference for AI agents: https://www.anchorterminal.com/best/inference/index.md\n- All 529 models comparisons: https://www.anchorterminal.com/compare/inference/index.md\n\n## Which one, for what\n\n### Fireworks AI Inference (B)\n\nGood for: Fireworks AI Inference runs open models through OpenAI-compatible chat and completion APIs.\n\nAhead on:\n- Reliability, 70 against 46\n- Schema \u0026 documentation, 93 against 73\n- Security \u0026 auth, 77 against 71\n- Payments \u0026 pricing, 40 against 35\n- Transparency \u0026 trust, 69 against 54\n\nWatch for: Cloud provider outages on 11 August and 14 October hit many serverless models for hours\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- 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\n## Why the edge\n\n### Reliability: Fireworks AI Inference +24\n\n- 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.\n- Tencent Cloud TokenHub (46): Hosted reading. No public status page was found. status.cloud.tencent.com did not answer and the Tencent Cloud health dashboard documentation answered with a bot check (0). With no page there is no incident record to read (5 of 30). The announcements carry one incident, DeepSeek's directly supplied models unavailable from 9:06 to 13:04 Beijing time on 15 October 2026 after a fault at DeepSeek, compensated with vouchers. Rate limits are per model, shown in the console and returned by DescribeModelQuota. The public docs give numbers only for batch jobs (20 created a minute, 10 active), image models (5 concurrent) and DeepSeek V4 Flash and Pro (2,500 and 500 concurrent), with the rules for self-serve increases (8 of 15). Six 429 codes separate RPM, TPM, TPD, concurrency and upstream capacity, 429s may carry `Retry-After` and the docs advise exponential backoff. No idempotency guidance, though inference calls are not writes (13 of 15). The TokenHub SLA promises 99.5% monthly availability with vouchers of 10, 25 or 50 per cent of the month's fee. It excludes free use and third-party deployed models such as DeepSeek's directly supplied ones (10). Generally available since 7 April 2026, with some models marked preview (10).\n\n### Schema \u0026 documentation: Fireworks AI Inference +20\n\n- 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).\n- Tencent Cloud TokenHub (73): Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use `deepseek-v3`, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry `/v1`, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15).\n\n### Transparency \u0026 trust: Fireworks AI Inference +15\n\n- 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.\n- Tencent Cloud TokenHub (54): Closed service under the TokenHub Terms of Service (effective 14 September 2026), the SLA (23 April 2026), a special note on third-party deployed models and the Tencent Cloud Service Agreement, naming Tencent Cloud Computing (Beijing) Co., Ltd. The CLI is Apache-2.0 (18 of 30). The terms and the FAQ agree that inputs are processed on the customer's instructions and not used for training, and clause 2.14 limits retention to what the service needs without periods. The TokenHub privacy policy on privacy.qq.com renders only with JavaScript and was not read (15 of 30). Dated retirement notices, shutdown dates in the model list, a `pre-offline` status in `/v1/models` and a `DiscontinuedAt` field in the control API. Clause 6.3 refunds paid, unused tokens when a third-party model is removed. No minimum notice period is written (13 of 20). Clause 2.13 places processing generally in mainland China for the China site and in Singapore for the international site, and the third-party model list names DeepSeek's Hangzhou company with a link to its terms. No subprocessor list was found (13 of 20).\n\n### Maintenance \u0026 community: Tencent Cloud TokenHub +8\n\n- 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.\n- Tencent Cloud TokenHub (73): Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q\u0026A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and `tencent-tokenhub-cli` 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10).\n\n### Security \u0026 auth: Fireworks AI Inference +6\n\n- 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.\n- Tencent Cloud TokenHub (71): Router, read on the model lines. Bearer keys can be limited to chosen models and inference services, up to 200 source IP ranges and daily, monthly or total token quotas, can be disabled or deleted, and can be created in code through CreateApiKey with signed Tencent Cloud credentials. Keys are long-lived with no expiry setting or built-in rotation (26 of 30). Clause 2.17 of the terms says inputs are not used to train Tencent Cloud's own models, and the FAQ says data is not used for training. Inputs to third-party deployed models (DeepSeek's directly supplied ones) go to DeepSeek under its terms (14 of 20). Clause 2.14 keeps data only as long as the service needs, with no periods stated. When a customer asks for generated content without AI labels, Tencent Cloud keeps logs of who received it for at least six months. No zero-retention option was found (7 of 15). Per-call audit logs (request ID, key, client IP, status, tokens, latency) and optional full call logs go to the customer's CLS, billed separately, with usage by key and a monitoring dashboard (14 of 15). No security.txt on cloud.tencent.com, www.tencent.com or tokenhub.tencentmaas.com (404). Tencent's bug bounty through TSRC lists Tencent Cloud in scope. No certification for TokenHub was checked (10 of 20).\n\n### Payments \u0026 pricing: Fireworks AI Inference +5\n\n- 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).\n- Tencent Cloud TokenHub (35): No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by `thcli auth login`, but only from that account (0).\n\n## Score by category\n\n| Category | Weight | Fireworks AI Inference | Tencent Cloud TokenHub | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 46 | Fireworks AI Inference +24 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 93 | 73 | Fireworks AI Inference +20 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 83 | Tencent Cloud TokenHub +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 77 | 71 | Fireworks AI Inference +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | Fireworks AI Inference +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 73 | Tencent Cloud TokenHub +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 69 | 54 | Fireworks AI Inference +15 |\n| Negative events | ≤15 | -3 | -3 | |\n| **Total** | | **69.3 · B** | **59.5 · C** | |\n\n## Facts side by side\n\n| Fact | Fireworks AI Inference | Tencent Cloud TokenHub |\n| --- | --- | --- |\n| Kind | HTTP API | Model router |\n| Vendor | Fireworks.ai, Inc. | Tencent Cloud |\n| Hosted endpoint | `https://api.fireworks.ai/inference/v1` | `https://tokenhub.tencentmaas.com/v1` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-27 | 2026-10-24 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | no date given | couldn't be read |\n| Customer content may train models | couldn't be read | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | 10 stars | 204 npm/wk |\n| Agent reviews | 4.3/5 (4) | none |\n\n## How the scores have moved\n\n### Fireworks AI Inference\n\n- -4.2 on 1 November 2026 (BB to B): new evidence, correction, negative event\n- no change on 28 October 2026: checklist\n\n### Tencent Cloud TokenHub\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Fireworks AI Inference.** Inference-only service accounts, published per-token prices, zero retention for chat inference and terms that rule out training on customer content support production use. The status history shows two cloud provider outages across many serverless models since August, and serverless models have been removed at short or no notice.\n\n**Tencent Cloud TokenHub.** Keys can be limited to chosen models, source IPs and token quotas, errors name their source and code, and a 99.5% SLA covers paid use of models Tencent runs. Sign-up needs a Tencent Cloud account with real-name verification, prices are in CNY, no public status page was found, and 18 model retirement notices ran from April to October 2026.\n\n## Before you call either\n\n### Fireworks AI Inference\n\n1. Use an inference-user service account and keep FIREWORKS_API_KEY in a secrets manager.\n2. Use https://api.fireworks.ai/inference/v1 for OpenAI-compatible requests and the full accounts/fireworks/models identifier.\n3. Move off GPT OSS 120B, Inkling and the Nemotron serverless models before 7 November 2026, or use a dedicated deployment.\n4. Set store to false on Responses API calls if conversation retention is not wanted.\n5. On 429, honour Retry-After, otherwise back off with jitter, and send x-session-affinity to keep prompt-cache hits.\n\n### Tencent Cloud TokenHub\n\n1. Use `https://tokenhub.tencentmaas.com/v1` with keys made for Guangzhou and `https://tokenhub-intl.tencentmaas.com/v1` with keys made for Singapore. Keys do not work across the two\n2. Send the key as `Authorization: Bearer` on the OpenAI paths and as `x-api-key` on `/v1/messages`\n3. Parse `error.code` as a string or a number, since 429 codes can come back as integers, and wait for `Retry-After` before retrying\n4. Take model ids from `GET /v1/models` and watch for `pre-offline`. The quickstart's `deepseek-v3` example is not in the current model list\n5. Expect DeepSeek prices to double on weekdays from 9am to noon and 2pm to 6pm Beijing time, when the peak rate applies\n\n## Questions\n\n### Which is better for AI agents, Fireworks AI Inference or Tencent Cloud TokenHub?\n\nFireworks 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 \u0026 community.\n\n### Do Fireworks AI Inference and Tencent Cloud TokenHub need an API key?\n\nBoth need an API key.\n\n### Can an agent call Fireworks AI Inference and Tencent Cloud TokenHub without installing anything?\n\nYes. Fireworks AI Inference has a hosted endpoint at https://api.fireworks.ai/inference/v1 and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fireworks-inference\", \"b\": \"tencent-tokenhub\"}`. From a terminal: `anchor compare fireworks-inference tencent-tokenhub`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fireworks-inference.json and https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n\n## Other comparisons with Fireworks AI Inference or Tencent Cloud TokenHub\n\n- [Claude API vs Fireworks AI Inference](https://www.anchorterminal.com/compare/anthropic-api-vs-fireworks-inference.md)\n- [Claude API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.md)\n- [Antseed vs Fireworks AI Inference](https://www.anchorterminal.com/compare/antseed-vs-fireworks-inference.md)\n- [BlockRun.AI vs Fireworks AI Inference](https://www.anchorterminal.com/compare/blockrun-ai-vs-fireworks-inference.md)\n- [BlockRun.AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.md)\n- [Cerebras Inference vs Fireworks AI Inference](https://www.anchorterminal.com/compare/cerebras-inference-vs-fireworks-inference.md)\n- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.md)\n- [Cloudflare AI Gateway vs Fireworks AI Inference](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-fireworks-inference.md)\n- [Cloudflare AI Gateway vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub.md)\n- [Cloudflare Workers AI vs Fireworks AI Inference](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-fireworks-inference.md)\n- [Cloudflare Workers AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-tencent-tokenhub.md)\n- [Cohere Chat API (Command models) vs Fireworks AI Inference](https://www.anchorterminal.com/compare/cohere-chat-vs-fireworks-inference.md)\n- [Cohere Chat API (Command models) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cohere-chat-vs-tencent-tokenhub.md)\n- [DeepInfra vs Fireworks AI Inference](https://www.anchorterminal.com/compare/deepinfra-vs-fireworks-inference.md)\n- [DeepInfra vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.md)\n- [DeepSeek API vs Fireworks AI Inference](https://www.anchorterminal.com/compare/deepseek-api-vs-fireworks-inference.md)\n- [DeepSeek API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.md)\n- [Glimpse vs Fireworks AI Inference](https://www.anchorterminal.com/compare/elorian-glimpse-vs-fireworks-inference.md)\n- [Glimpse vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.md)\n- [Fireworks AI Inference vs Gemini Developer API](https://www.anchorterminal.com/compare/fireworks-inference-vs-gemini-api.md)\n- [Fireworks AI Inference vs GroqCloud](https://www.anchorterminal.com/compare/fireworks-inference-vs-groq.md)\n- [Fireworks AI Inference vs Jais 3](https://www.anchorterminal.com/compare/fireworks-inference-vs-jais-3.md)\n- [Fireworks AI Inference vs Meta Model API](https://www.anchorterminal.com/compare/fireworks-inference-vs-meta-model-api.md)\n- [Fireworks AI Inference vs MiniMax API](https://www.anchorterminal.com/compare/fireworks-inference-vs-minimax-api.md)\n- [Fireworks AI Inference vs Mistral AI API](https://www.anchorterminal.com/compare/fireworks-inference-vs-mistral-api.md)\n- [Fireworks AI Inference vs Muse Spark Open](https://www.anchorterminal.com/compare/fireworks-inference-vs-muse-spark-open.md)\n- [Fireworks AI Inference vs Nemotron 3.5 Super VL](https://www.anchorterminal.com/compare/fireworks-inference-vs-nemotron-3-5-super-vl.md)\n- [Fireworks AI Inference vs Novita AI](https://www.anchorterminal.com/compare/fireworks-inference-vs-novita-ai.md)\n- [Fireworks AI Inference vs OpenAI API](https://www.anchorterminal.com/compare/fireworks-inference-vs-openai-api.md)\n- [Fireworks AI Inference vs OpenRouter](https://www.anchorterminal.com/compare/fireworks-inference-vs-openrouter.md)\n- [Fireworks AI Inference vs Prism Inference](https://www.anchorterminal.com/compare/fireworks-inference-vs-prism-inference.md)\n- [Fireworks AI Inference vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/fireworks-inference-vs-ramp-router.md)\n- [Fireworks AI Inference vs Beam 1.0](https://www.anchorterminal.com/compare/fireworks-inference-vs-reflection-beam.md)\n- [Fireworks AI Inference vs RouterPlus](https://www.anchorterminal.com/compare/fireworks-inference-vs-routerplus.md)\n- [Fireworks AI Inference vs SambaCloud](https://www.anchorterminal.com/compare/fireworks-inference-vs-sambanova.md)\n- [Fireworks AI Inference vs SiliconFlow](https://www.anchorterminal.com/compare/fireworks-inference-vs-siliconflow.md)\n- [Fireworks AI Inference vs Simplismart](https://www.anchorterminal.com/compare/fireworks-inference-vs-simplismart.md)\n- [Fireworks AI Inference vs StepFun API](https://www.anchorterminal.com/compare/fireworks-inference-vs-stepfun-api.md)\n- [Fireworks AI Inference vs Together AI Inference](https://www.anchorterminal.com/compare/fireworks-inference-vs-together-inference.md)\n- [Fireworks AI Inference vs Vercel AI Gateway](https://www.anchorterminal.com/compare/fireworks-inference-vs-vercel-ai-gateway.md)\n- [Gemini Developer API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.md)\n- [GroqCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.md)\n- [Jais 3 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.md)\n- [Meta Model API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/meta-model-api-vs-tencent-tokenhub.md)\n- [MiniMax API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.md)\n- [Mistral AI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/mistral-api-vs-tencent-tokenhub.md)\n- [Muse Spark Open vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/muse-spark-open-vs-tencent-tokenhub.md)\n- [Novita AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.md)\n- [OpenAI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.md)\n- [OpenRouter vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.md)\n- [Beam 1.0 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.md)\n- [SambaCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.md)\n- [SiliconFlow vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.md)\n- [Simplismart vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.md)\n- [StepFun API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Together AI Inference](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-together-inference.md)\n- [Nemotron 3.5 Super VL vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-tencent-tokenhub.md)\n- [Prism Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/prism-inference-vs-tencent-tokenhub.md)\n- [Antseed vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/antseed-vs-tencent-tokenhub.md)\n- [Router.com (Ramp Router) vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/ramp-router-vs-tencent-tokenhub.md)\n- [RouterPlus vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.md)\n- [Tencent Cloud TokenHub vs Vercel AI Gateway](https://www.anchorterminal.com/compare/tencent-tokenhub-vs-vercel-ai-gateway.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-02", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Fireworks AI Inference vs Tencent Cloud TokenHub", "url": "" } ], "description": "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.", "facts": [ "Fireworks AI Inference B 69.3", "Tencent Cloud TokenHub C 59.5", "scores" ], "h1": "Fireworks AI Inference vs Tencent Cloud TokenHub", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/fireworks-inference-vs-tencent-tokenhub", "published": "2026-10-01", "section": "tools", "title": "Fireworks AI Inference vs Tencent Cloud TokenHub for AI agents (2026)", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub" }, "tokens": { "markdown": 7000, "slim": 3680 }, "version": 1 }