Meta Model API vs Tencent Cloud TokenHub

Meta Model API 46

Model reading. Muse Wonder launched on 12 October 2026 (30). No deprecation policy or notice period found. All three Muse Spark versions are still served, so no retirement has tested one (0 of 12). Three dated launches in the last 90 days that we read, Muse Spark 1.2 on 5 August, Muse Code out of beta on 31 August and Muse Wonder on 12 October (8 of 8). No Model API changelog. A help centre with support tickets, answered 'typically within two business days' by Meta's own account, which we didn't test (8 of 15). No SDK of Meta's own for the API (0 of 15, 0 of 10).

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).

Meta Model API 20

No machine payment protocol (0). Per-token prices for Muse Wonder and Muse Spark, and per-image, per-hour and per-frame prices for the other models, published without a login (20). No free API allowance found. Billing needs a card, and Playground requests count towards usage (0). Browser sign-up with email, phone, Facebook, Google or GitHub (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).

Meta Model API 60

No OpenAPI or similar machine-readable contract found. The reference is Markdown pages with schema sections, and /openapi.json paths on dev.meta.ai return 404 (0). llms.txt at dev.meta.ai/llms.txt, and every docs page has a Markdown copy (10). The models page says when to choose Muse Wonder and when Muse Spark, and the tool-calling and structured-output guides state their limits, such as tool_choice only accepting auto and which schema keywords strict allows (16 of 20). JSON Schema tools and output, reasoning_effort an enum from minimal to max, a strict subset that returns 400 when violated, though tool_choice has one value (12 of 15). Curl, Python and TypeScript examples on each page and an error guide covering 400 to 504 with the error envelope, codes and a fix for each (15). Versioned model IDs (muse-spark-1.1 to 1.3, muse-wonder-1.0) and dated launch posts on the developer blog, but no API changelog (7 of 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).

Meta Model API 75

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool calls on all three endpoints, parallel calls, tool search with deferred loading, built-in web search and a computer-use tool, but tool_choice accepts only auto, so a call can't be forced or forbidden (15 of 20). Output constrained to the JSON Schema on every surface (15). Automatic prompt caching with no setup, and cached input at 5 per cent of the input price on Muse Wonder (15). 1,048,576-token context on Muse Wonder and every Muse Spark version, with no long-context premium (15). No batch endpoint or discount found. Background responses run asynchronously at the normal price (0). No SDK of Meta's own. The docs use the OpenAI and Anthropic SDKs against compatible endpoints, the same reading as StepFun (0). OpenAI-style error envelope with type and code, per-status fixes and named retryable codes (15).

Tencent Cloud TokenHub 83

Router, read on the model lines. Function calling is marked on most chat models in the model list, with behaviour depending on the model routed (14 of 20). Structured output is marked per model and missing on the MiniMax and Qwen models, and an unsupported response_format returns code 400006 (12 of 15). Cache-hit prices are published per model, Kimi K3.1 Pro lists five-minute and one-hour cache writes, and a guide covers prompt_cache_key and the X-Session-ID header for instance affinity (14 of 15). Most listed chat models have contexts of one million tokens, a judgement call since a router has no default model (15). Batch at half price covers only Hy3 and Hy4 preview, reads and writes JSONL in the customer's own COS bucket and is documented for the Guangzhou endpoint (5 of 10). No TokenHub inference SDK. The OpenAI and Anthropic SDKs work with a changed base URL, and Tencent Cloud SDK 3.0 and the thcli CLI cover the control plane (8 of 10). Errors return a code, English and Chinese messages, the source, the upstream code and status and a request ID, and stream errors arrive as SSE error frames (15 of 15).

Meta Model API 64

Model reading. Bearer keys per team, named, shown once and revoked by deletion, with rotation advice. No scopes, read-only keys or per-key limits found (20 of 30). The terms say Meta will not use Content submitted to the Standard Services to train Meta Models, and training applies only to the -contributor model IDs a caller picks. Content may still be used to develop and improve safety and security systems (17 of 20). Retention is 'as needed' for the service, the law, flagged violations and safety review, with no period stated. Zero data retention for qualified accounts through sales, with flagged content kept up to 2 years (10 of 15). The usage dashboard shows tokens and requests per day by model, with no per-key or per-call log found (5 of 15). No security.txt on dev.meta.ai. Meta's bug bounty at bugbounty.meta.com is named in the Muse Code SDK's security policy, and a security commitments page describes TLS 1.2 or later, PCI-DSS card handling and an ISMS, with no named certification for the API (12 of 20).

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).

Meta Model API 40

No status page with component history. The error guide's link to dev.meta.ai/status redirects to the home page, and GET /v1/status reports only the current state, operational when we called it on 12 October (0). No readable incident history (5). Rate limits published per team and per model, 3,000 RPM and 4,000,000 TPM for muse-wonder-1.0, 150 RPM for the contributor variants, 600 background submissions a minute (15). 429 and 503 carry Retry-After (60 seconds for service_overloaded and backend_unavailable), with backoff-with-jitter guidance, rate-limit headers on every token response and a documented mid-stream server_shutting_down event to retry (15). No SLA found, and the terms let Meta throttle or suspend access without notice (0). Muse Wonder is labelled a preview. Muse Spark 1.3 carries no preview label, but the API opened on 8 July 2026 as a public preview and we found no general-availability notice, so half (5 of 10, a departure from the all-or-nothing line).

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).