Eden AI vs Tencent Cloud TokenHub

Eden AI 58

Closed service, read on the model lines. The docs repository changed on 5 and 6 November 2026, including retiring Nova Reel and Veo from video generation, and the terms were updated 22 October (30). No public changelog, so dated API changes in the last 90 days come only from docs commits (12 of 20). Chat support within 48 working hours, no public changelog (8). No SDK of its own, and the MCP server isn't in the official MCP registry (5). Nothing to judge package health by beyond the docs repository (3). 30+12+8+5+3 = 58.

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

Eden AI 33

Router, read on the hosted lines. No status page is linked from the site or docs, and status.edenai.co didn't resolve for us on 6 November 2026 (0). No incident history to read (5). The rate-limits page gives 10 requests a second per account, shared across keys, while the plans page gives 7 a second, raisable to 15, so the figure is documented but inconsistent (10). Fallback retries the next model or provider on a 429 or error inside one request, but no client-facing 429 or Retry-After guidance was found (8). No SLA published; 'Dedicated support & SLA' is listed only for the custom Advanced plan, and the pricing page's '99.99%' uptime is a claim without a status page behind it (0). The v3 API is GA (10). 0+5+10+8+0+10 = 33.

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

Eden AI 82

Router, read on the model lines. Bearer keys with per-key budgets, expiry and attribution, a key management API, and deny-by-default guardrails that limit models per member, role or key (25). The data retention page says request and response content isn't stored and data isn't used to train models by default (18). Content logging is opt-in, async results are deleted after 7 days, and an organisation can enforce Zero Data Retention and region rules; the EU endpoint refuses non-EU models with 451 (13). Cost and provider per response, and a monitoring dashboard by key (12). The security page says Eden AI is SOC 2 and ISO 27001 certified and links a trust centre; /.well-known/security.txt returns 404 and no disclosure policy was found (14). 25+18+13+12+14 = 82.

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

Eden AI 81

Router, scored on the API lines. OpenAPI 3.1 document for v3 (version 3.0.0, 46 paths) at api.edenai.run/v3/docs/openapi.json, plus a management API spec (25). llms.txt on the site and in the docs, llms-full.txt and Markdown pages (10). llms.txt states when to use Eden AI and when not to, and the docs separate chat models from expert models (17). Requests follow the OpenAI shape, and expert-model tools on the MCP server carry JSON Schema inputs (12). Examples throughout, but the spec documents only 200, 201, 202, 302 and 422, while llms.txt names 401 and 451 for region refusals (10). Versioned /v3 path, but no public changelog was found (7). 25+10+17+12+10+7 = 81.

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

Eden AI 75

Router, read on the model lines. Chat completions, Responses and an Anthropic Messages route in the OpenAI shape, with tool calling depending on the routed model (14 of 20) and structured output likewise (10 of 15). Caching is named in the terms as part of the service, without a per-model price table we read (8 of 15). Context depends on the model; the keyless /v3/models catalogue lists capabilities, prices and regions per model so an agent can choose (12 of 15). A Batches API (10 of 10). No SDK of its own; the docs use the OpenAI Python and TypeScript SDKs, and a hosted MCP server exposes about 40 expert-model tools plus upload_file, check_job and list_models (21 of 25). 14+10+8+12+10+21 = 75.

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

Eden AI 30

No x402, MPP or L402 (0). Provider prices with no markup plus a 5.5% platform fee, published per model in the keyless catalogue (20). llms.txt says some models are billed $0 for tests, but whether a new account can call them without buying credits isn't stated (10). A person signs up in a browser and buys credits through Stripe (0). 0+20+10+0 = 30.

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