{ "data": { "a": { "slug": "simplismart", "name": "Simplismart", "vendor": "Verute Technologies Private Limited", "vendorUrl": "https://simplismart.ai", "kind": "http-api", "category": "inference", "summary": "Simplismart is an inference platform for open models. It runs 150+ models on shared pay-per-token endpoints with an OpenAI-compatible API, and handles dedicated GPU deployments, bring-your-own-cloud clusters and fine-tuning jobs.", "url": "https://www.anchorterminal.com/tools/simplismart", "markdownUrl": "https://www.anchorterminal.com/tools/simplismart.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/simplismart.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/simplismart.json", "dns": "simplismart.grade.anchorterminal.com", "license": "Proprietary hosted service. The community Pipecat integration (pipecat-simplismart, by the simpli-smart GitHub account) is BSD-2-Clause; served models keep their own licences.", "transports": [ "http" ], "remoteUrl": "https://api.simplismart.live", "packages": [ { "registry": "pypi", "name": "simplismart-sdk" } ], "auth": "api-key", "authNotes": "Bearer API keys made under Settings, API Keys. Each key has a unique name and an expiry chosen at creation; non-expiring keys need a request to support. Keys return 401 after midnight UTC on the expiry date and can be deleted at once. The Python SDK and CLI use a separate Playground token. Organisation roles are Admin, Member and Billing User, and workspaces scope models and deployments.", "pricing": "usage", "pricingNotes": "Shared endpoints are priced per 1M tokens, per image or per audio minute, such as Llama 3.1 8B at $0.13 and DeepSeek-V3 at $0.90 per 1M tokens. Dedicated GPUs run from $1.20 (T4) to $5.20 (H200) per GPU-hour. Prepaid credits at $1 each; new organisations may receive $5 of free credits.", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs (llms.txt index, billing, API keys and API reference pages) or on the pricing page, checked 28 October 2026. Credits are bought by card, UPI or netbanking, or billed postpaid.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-28" }, "docsUrl": "https://docs.simplismart.ai", "llmsTxt": "https://docs.simplismart.ai/llms.txt", "openapi": "https://docs.simplismart.ai/openapi-specs/playground/llama-8b.yaml", "capabilities": [ "inference.llm", "inference.open-weights", "speech.stt", "image.generate", "compute.endpoints", "finetune.sft", "finetune.lora", "finetune.preference", "finetune.rl" ], "tags": [ "hosted", "model", "open-weights", "usage-based", "openai-compatible", "openapi", "llms-txt", "python", "dedicated-endpoints", "byoc", "fine-tuning" ], "lastRelease": "2026-10-19", "graded": true, "anchor": { "graded": true, "score": 29.5, "grade": "F", "agentReady": false, "rank": 1186, "ranked": true, "rankOf": 1260, "categoryRank": 33, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 17, "maintenance": 42, "payments": 25, "reliability": 15, "schema": 51, "security": 35, "transparency": 29 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-28" }, "negative": 0, "verdict": "Simplismart exposes open models through an OpenAI-compatible endpoint with public per-token prices and expiring, revocable keys. Its public docs give no request rate limits, status page, retry guidance, tool-calling or structured-output reference, and its terms and privacy policy cover the website, not API data.", "bestFor": "Teams that want open models on a pay-per-token OpenAI-compatible endpoint and a path to dedicated GPUs, their own cloud or fine-tuning with one vendor, and can work without published rate limits or data-handling terms.", "strengths": [ "Public per-unit prices without a login, such as Llama 3.1 8B at $0.13 per 1M tokens and Whisper v3 Turbo at $0.0018 per audio minute", "API keys are named, carry an expiry date chosen at creation, return 401 after expiry and can be deleted at once", "Markdown docs and an llms.txt index, with OpenAPI 3.1 files for seven LLMs, Whisper and Flux", "Shared endpoints, dedicated GPU deployments and bring-your-own-cloud clusters sit on one account, with workspaces and organisation roles" ], "weaknesses": [ "No request or token rate limits, 429 handling or retry guidance found in the docs; only GPU quotas, given as 1 and as 8 H100s on two pages", "No status page, incident history or SLA document found; the 99.99% uptime figure is a homepage claim", "Tool calling, structured output, prompt caching and context lengths are not documented for the shared endpoints", "The terms (13 January 2023) and privacy policy cover the website and say nothing about prompt retention or training on API data", "The pricing page lists older models (Llama 3.1, DeepSeek-R1) and omits Gemma 4 31B, the model the quickstart uses" ], "agentNotes": [ "Point an OpenAI-compatible client at https://api.simplismart.live with SIMPLISMART_API_KEY as a Bearer token, and take model ids from the marketplace or the per-model API pages.", "Set a key expiry and rotate before midnight UTC on the expiry date, because an expired key returns 401.", "Cap retries yourself with exponential backoff, because no rate limits, 429 format or retry guidance are published.", "Check that a model supports tools or JSON output with a test call before relying on it, because neither is documented.", "Confirm the per-token price of the exact model in the console before running large jobs, because the public price list is incomplete." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 29.5 } ], "editorialScores": { "ergonomics": 17, "maintenance": 42, "payments": 25, "reliability": 15, "schema": 51, "security": 35, "transparency": 14 }, "provenanceScore": 44, "checked": { "categories": { "ergonomics": "2026-10-28", "maintenance": "2026-10-28", "payments": "2026-10-28", "reliability": "2026-10-28", "schema": "2026-10-28", "security": "2026-10-28", "transparency": "2026-10-28" }, "last": "2026-10-28", "lastMoved": "2026-10-30", "oldest": "2026-10-28", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl 'https://api.simplismart.live/chat/completions' -H 'Content-Type: application/json' -H \"Authorization: Bearer $SIMPLISMART_API_KEY\" -d '{\"model\": \"meta-llama/Meta-Llama-3.1-8B-Instruct\", \"messages\": [{\"role\": \"user\", \"content\": \"Say hello.\"}]}'" }, "letme": { "capability": "https://letme.dev/inference.llm", "tool": "https://letme.dev/simplismart" }, "area": "models", "unitPrices": [ { "item": "Llama 3.1 8B (shared)", "unit": "1m-tokens", "usd": 0.13, "note": "Single per-1M-token rate on the pricing page, checked 28 October 2026; input and output are not priced separately" }, { "item": "Llama 3.3 70B (shared)", "unit": "1m-tokens", "usd": 0.74, "note": "Pricing page, checked 28 October 2026" }, { "item": "DeepSeek-V3 (shared)", "unit": "1m-tokens", "usd": 0.9, "note": "Pricing page, checked 28 October 2026" }, { "item": "Whisper v3 Turbo (shared)", "unit": "audio-minute", "usd": 0.0018, "note": "Pricing page, checked 28 October 2026" }, { "item": "Flux Dev (shared, 1024x1024)", "unit": "image", "usd": 0.03, "note": "Pricing page, checked 28 October 2026" }, { "item": "NVIDIA H100, dedicated", "unit": "gpu-hour", "usd": 5, "note": "Pricing page table order, checked 28 October 2026; a Simplismart article gives $4.00 per hour" } ], "provenance": { "legalEntity": "Verute Technologies Private Limited", "domain": "simplismart.ai", "domainRegistered": "", "endpointOnVendorDomain": false, "terms": "https://simplismart.ai/terms-of-service", "privacy": "https://simplismart.ai/privacy-policy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-28", "notes": [ "The terms (last updated 13 January 2023) and privacy policy (effective 13 January 2023) name Verute Technologies Private Limited, Indian law and an address on Residency Road, Bengaluru. Both define the Service as the simplismart.ai website.", "The inference API answers on api.simplismart.live, a separate domain named in the docs. Domain registration was not checked.", "No status page found. The docs and site link none, and status.simplismart.ai could not be reached from our network.", "No changelog found in the docs sitemap or llms.txt. Model additions appear as blog posts.", "simplismart.ai/.well-known/security.txt answered 404." ], "score": 44 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/simplismart.json", "live": { "slug": "simplismart", "probe": { "target": "https://api.simplismart.live", "method": "get", "lastAt": "2026-11-02T00:56:21.339705885Z", "lastOk": true, "lastStatus": 405, "lastMs": 91, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 69, "p95ms24h": 211, "samples24h": 249, "samples30d": 1216, "days": [ { "date": "2026-10-28", "probes": 208, "ok": 208 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 10, "ok": 10 } ] }, "versions": [ { "registry": "pypi", "name": "simplismart-sdk", "version": "0.1.14", "released": "2026-10-07", "seenAt": "2026-11-01T17:33:56.070422389Z" } ], "pypiWeekly": 169, "securityTxt": { "url": "https://simplismart.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-01T15:43:36.305821616Z" }, "llmsTxt": { "url": "https://docs.simplismart.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-01T15:14:59.916115957Z" }, "domain": { "domain": "simplismart.ai", "registered": "2022-11-18", "source": "https://rdap.identitydigital.services/rdap/domain/simplismart.ai", "checkedAt": "2026-11-01T14:28:09.738527702Z" }, "pages": [ { "url": "https://simplismart.ai/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-01T06:52:41.603353845Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bd2d6d5ffe37" }, { "url": "https://simplismart.ai/terms-of-service", "kind": "terms", "status": 304, "checkedAt": "2026-11-01T06:52:43.665887762Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "94fe8807daf7" } ], "updatedAt": "2026-11-02T00:56:21.339705885Z" } }, "answer": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Simplismart's 29.5 (F), and leads in every scored category.", "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": 66, "category": "ergonomics", "leads": "tencent-tokenhub", "name": "Agent ergonomics", "reasons": { "a": "Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). The LiveKit guide calls the LLM API fully OpenAI-compatible, but no page documents tools or tool_choice, and the OpenAPI files allow only system, user and assistant roles (3 of 20). No structured-output or JSON mode documented (0 of 15). No prompt caching documented for shared endpoints (0 of 15). Context lengths are not stated per model; output is capped at 4,096 tokens in the API files (3 of 15). No batch API for shared endpoints (0 of 10). Inference goes through the OpenAI client; the simplismart-sdk Python package and CLI manage repositories and deployments, not inference, and a community Pipecat package exists (5 of 10). Expired keys return a documented 401, and the SDK exposes status_code, message and payload, but no error codes or bodies are listed for the inference API (6 of 15). 3+0+0+3+0+5+6 = 17.", "b": "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)." }, "scores": { "a": 17, "b": 83 } }, { "by": 36, "category": "security", "leads": "tencent-tokenhub", "name": "Security \u0026 auth", "reasons": { "a": "Model reading. Named Bearer keys with an expiry chosen at creation, a 401 after expiry and immediate deletion. No scopes or per-key limits found, keys belong to the organisation, and the SDK uses a separate Playground token (20 of 30). No statement on training on API data in the terms, the privacy policy, the AI policy or the docs (0 of 20). No retention or zero-retention statement for prompts and outputs. The privacy policy covers the website only (0 of 15). The Usage page shows request counts and a per-request timeline per model, and an LLM metrics call returns token counts and timings per request id. A Simplismart article claims exportable audit trails, not documented (8 of 15). The homepage shows GDPR, ISO 27001 v2022 and AICPA SOC 2 badges, and a Simplismart article says it holds a SOC 2 Type 2 report, available on request. No trust centre was reachable, security.txt answered 404, and no disclosure policy or bug bounty was found (7 of 20). 20+0+0+8+7 = 35.", "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": 35, "b": 71 } }, { "by": 31, "category": "reliability", "leads": "tencent-tokenhub", "name": "Reliability", "reasons": { "a": "Hosted reading. No status page found. The docs and site link none, a search found none, and status.simplismart.ai could not be reached from our network (0). No readable incident history (5). No request or token rate limits are published for shared endpoints. The docs give GPU quotas for training, compilation and private deployments only, 1 H100 and 1 L40 on the Quotas page and 8 of each on the Organisation page (0). No 429 response, Retry-After header or retry guidance found; the OpenAPI files list only 400, 401 and 500 (0). No SLA document found. The homepage claims 99.99% uptime and a Simplismart post calls its autoscaling SLA-backed, but no terms state a commitment, and the terms provide the service as is (0). Shared endpoints carry no beta label, while Muse Spark Open is in beta (10). 0+5+0+0+0+10 = 15.", "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": 15, "b": 46 } }, { "by": 31, "category": "maintenance", "leads": "tencent-tokenhub", "name": "Maintenance \u0026 community", "reasons": { "a": "Model reading for a closed service. Muse Spark Open was added in beta on 19 October 2026, and the docs sitemap shows pages changed on 7 October (30). No deprecation policy or notice period found (0 of 12). One dated model addition in the 90 days to 28 October and no recorded removals; the pricing page still lists Llama 3.1 405B and DeepSeek-R1, which the API reference doesn't cover, so the live model set is unclear (2 of 8). No public changelog or community channel. Support is support@simplismart.ai and a contact form, not tested (4 of 15). SDK issue replies not read, because github.com gave no readable robots.txt (0 of 10). simplismart-sdk for Python, documented with a CLI, and the OpenAI client for inference. No TypeScript SDK, and the PyPI page answered with a browser challenge, so the version and date are unchecked (6 of 15). CI not checked (0 of 10). 30+0+2+4+0+6+0 = 42.", "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": 42, "b": 73 } }, { "by": 25, "category": "transparency", "leads": "tencent-tokenhub", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service. The terms, last updated 13 January 2023, name Verute Technologies Private Limited and Indian law but define the Service as the website, grant Simplismart a licence to use and redistribute posted Content, bar robots and automatic access, and rule out refunds. No API or platform terms were found (8 of 30). The privacy policy, effective 13 January 2023, is a website policy that says personal data is processed in India. It says nothing about prompts, outputs, logs or training, and no DPA, retention period or subprocessor list was found. A Simplismart article claims GDPR and HIPAA support (3 of 30). No deprecation policy or dated removals (0 of 20). Data goes to India per the privacy policy, and an article says workloads are kept in approved regions by scheduling policy. No subprocessor or hosting-provider list (3 of 20). 8+3+0+3 = 14.", "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": 29, "b": 54 } }, { "by": 22, "category": "schema", "leads": "tencent-tokenhub", "name": "Schema \u0026 documentation", "reasons": { "a": "Model reading. OpenAPI 3.1 files for seven LLMs and 3.0 or 3.1 files for Whisper, Flux, an LLM metrics call and training jobs. They cover a handful of the 150+ models, omit tools and response_format, show a streaming `delta` as the non-streaming response, and several name hosts on s9t.link instead of api.simplismart.live. The Llama 4 Maverick file gives `llama3_1` as its only model id, and /api-reference/openapi.json is the Flux spec (12 of 25). llms.txt and a Markdown copy of each docs page (10). The docs say when to use shared or dedicated endpoints; model pages carry one-line descriptions (10 of 20). Roles are enums, temperature is bounded 0 to 2, max_tokens 1 to 4096, and messages and model are required (10 of 15). curl and OpenAI-client Python examples. Errors are bare 400, 401 and 500 descriptions, plus an SDK example of a 404 payload (7 of 15). No changelog. Every spec reads version 1.0.0 (2 of 15). 12+10+10+10+7+2 = 51.", "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": 51, "b": 73 } } ], "facts": [ { "a": "HTTP API", "b": "Model router", "name": "Kind" }, { "a": "Verute Technologies Private Limited", "b": "Tencent Cloud", "name": "Vendor" }, { "a": "https://api.simplismart.live", "b": "https://tokenhub.tencentmaas.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service. The community Pipecat integration (pipecat-simplismart, by the simpli-smart GitHub account) is BSD-2-Clause; served models keep 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-19", "b": "2026-10-24", "name": "Last release" }, { "a": "2023-01-13", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2023-01-13", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "204 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Simplismart's 29.5 (F), and leads in every scored category.", "question": "Which is better for AI agents, Simplismart or Tencent Cloud TokenHub?" }, { "answer": "Both need an API key.", "question": "Do Simplismart and Tencent Cloud TokenHub need an API key?" }, { "answer": "Yes. Simplismart has a hosted endpoint at https://api.simplismart.live and Tencent Cloud TokenHub at https://tokenhub.tencentmaas.com/v1.", "question": "Can an agent call Simplismart and Tencent Cloud TokenHub without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them" ], "goodFor": "Teams that want open models on a pay-per-token OpenAI-compatible endpoint and a path to dedicated GPUs, their own cloud or fine-tuning with one vendor, and can work without published rate limits or data-handling terms.", "slug": "simplismart", "watchFor": "No request or token rate limits, 429 handling or retry guidance found in the docs; only GPU quotas, given as 1 and as 8 H100s on two pages" }, { "aheadOn": [ "Reliability, 46 against 15", "Schema \u0026 documentation, 73 against 51", "Agent ergonomics, 83 against 17", "Security \u0026 auth, 71 against 35", "Payments \u0026 pricing, 35 against 25", "Maintenance \u0026 community, 73 against 42", "Transparency \u0026 trust, 54 against 29" ], "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": { "simplismart": [ { "causes": [ "method" ], "date": "2026-10-30", "delta": -0.2, "from": 29.7, "fromGrade": "F", "to": 29.5, "toGrade": "F" } ], "tencent-tokenhub": null }, "job": { "capability": "inference.llm", "name": "LLM inference" }, "others": [ { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-simplismart.json", "title": "Claude API vs Simplismart", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-simplismart" }, { "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-simplismart.json", "title": "Antseed vs Simplismart", "url": "https://www.anchorterminal.com/compare/antseed-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/blockrun-ai-vs-simplismart.json", "title": "BlockRun.AI vs Simplismart", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-simplismart" }, { "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-simplismart.json", "title": "Cerebras Inference vs Simplismart", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-simplismart" }, { "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-simplismart.json", "title": "Cloudflare AI Gateway vs Simplismart", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-simplismart" }, { "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-simplismart.json", "title": "Cloudflare Workers AI vs Simplismart", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-simplismart" }, { "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-simplismart.json", "title": "Cohere Chat API (Command models) vs Simplismart", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-simplismart" }, { "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-simplismart.json", "title": "DeepInfra vs Simplismart", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-simplismart" }, { "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-simplismart.json", "title": "DeepSeek API vs Simplismart", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-simplismart" }, { "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-simplismart.json", "title": "Glimpse vs Simplismart", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-simplismart" }, { "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-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-tencent-tokenhub.json", "title": "Fireworks AI Inference vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/gemini-api-vs-simplismart.json", "title": "Gemini Developer API vs Simplismart", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-simplismart" }, { "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-simplismart.json", "title": "GroqCloud vs Simplismart", "url": "https://www.anchorterminal.com/compare/groq-vs-simplismart" }, { "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-simplismart.json", "title": "Jais 3 vs Simplismart", "url": "https://www.anchorterminal.com/compare/jais-3-vs-simplismart" }, { "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-simplismart.json", "title": "Meta Model API vs Simplismart", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-simplismart" }, { "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-simplismart.json", "title": "MiniMax API vs Simplismart", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-simplismart" }, { "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-simplismart.json", "title": "Mistral AI API vs Simplismart", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-simplismart" }, { "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-simplismart.json", "title": "Muse Spark Open vs Simplismart", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-simplismart" }, { "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-simplismart.json", "title": "Novita AI vs Simplismart", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-simplismart" }, { "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-simplismart.json", "title": "OpenAI API vs Simplismart", "url": "https://www.anchorterminal.com/compare/openai-api-vs-simplismart" }, { "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-simplismart.json", "title": "OpenRouter vs Simplismart", "url": "https://www.anchorterminal.com/compare/openrouter-vs-simplismart" }, { "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/prism-inference-vs-simplismart.json", "title": "Prism Inference vs Simplismart", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/ramp-router-vs-simplismart.json", "title": "Router.com (Ramp Router) vs Simplismart", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/reflection-beam-vs-simplismart.json", "title": "Beam 1.0 vs Simplismart", "url": "https://www.anchorterminal.com/compare/reflection-beam-vs-simplismart" }, { "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/routerplus-vs-simplismart.json", "title": "RouterPlus vs Simplismart", "url": "https://www.anchorterminal.com/compare/routerplus-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/sambanova-vs-simplismart.json", "title": "SambaCloud vs Simplismart", "url": "https://www.anchorterminal.com/compare/sambanova-vs-simplismart" }, { "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-simplismart.json", "title": "SiliconFlow vs Simplismart", "url": "https://www.anchorterminal.com/compare/siliconflow-vs-simplismart" }, { "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-stepfun-api.json", "title": "Simplismart vs StepFun API", "url": "https://www.anchorterminal.com/compare/simplismart-vs-stepfun-api" }, { "json": "https://www.anchorterminal.com/compare/simplismart-vs-together-inference.json", "title": "Simplismart vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/simplismart-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/simplismart-vs-vercel-ai-gateway.json", "title": "Simplismart vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/simplismart-vs-vercel-ai-gateway" }, { "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-simplismart.json", "title": "Nemotron 3.5 Super VL vs Simplismart", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-simplismart" }, { "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": 31, "edge": "tencent-tokenhub", "key": "reliability", "name": "Reliability", "simplismart": 15, "tencent-tokenhub": 46, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 22, "edge": "tencent-tokenhub", "key": "schema", "name": "Schema \u0026 documentation", "simplismart": 51, "tencent-tokenhub": 73, "weight": 13 }, { "by": 66, "edge": "tencent-tokenhub", "key": "ergonomics", "name": "Agent ergonomics", "simplismart": 17, "tencent-tokenhub": 83, "weight": 13 }, { "by": 36, "edge": "tencent-tokenhub", "key": "security", "name": "Security \u0026 auth", "simplismart": 35, "tencent-tokenhub": 71, "weight": 14 }, { "by": 10, "edge": "tencent-tokenhub", "key": "payments", "name": "Payments \u0026 pricing", "simplismart": 25, "tencent-tokenhub": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 31, "edge": "tencent-tokenhub", "key": "maintenance", "name": "Maintenance \u0026 community", "simplismart": 42, "tencent-tokenhub": 73, "weight": 7 }, { "by": 25, "edge": "tencent-tokenhub", "key": "transparency", "name": "Transparency \u0026 trust", "simplismart": 29, "tencent-tokenhub": 54, "weight": 7 } ], "summary": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Simplismart's 29.5 (F), and leads in every scored category. Both do llm inference.", "tasks": null, "tutorials": [], "verdicts": { "simplismart": "Simplismart exposes open models through an OpenAI-compatible endpoint with public per-token prices and expiring, revocable keys. Its public docs give no request rate limits, status page, retry guidance, tool-calling or structured-output reference, and its terms and privacy policy cover the website, not API data.", "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/simplismart-vs-tencent-tokenhub", "json": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.min.md" }, "markdown": "Tencent Cloud TokenHub scores 59.5 (C) on agent readiness against Simplismart's 29.5 (F), and leads in every scored category. Both do llm inference.\n\n- Simplismart: grade F, 29.5/100, rank #1186 of 1260. Markdown https://www.anchorterminal.com/tools/simplismart.md · JSON https://www.anchorterminal.com/api/v1/tools/simplismart.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### Simplismart (F)\n\nGood for: Teams that want open models on a pay-per-token OpenAI-compatible endpoint and a path to dedicated GPUs, their own cloud or fine-tuning with one vendor, and can work without published rate limits or data-handling terms.\n\nAlso in its favour:\n- No incidents deducted, where Tencent Cloud TokenHub loses 3 points for them\n\nWatch for: No request or token rate limits, 429 handling or retry guidance found in the docs; only GPU quotas, given as 1 and as 8 H100s on two pages\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- Reliability, 46 against 15\n- Schema \u0026 documentation, 73 against 51\n- Agent ergonomics, 83 against 17\n- Security \u0026 auth, 71 against 35\n- Payments \u0026 pricing, 35 against 25\n- Maintenance \u0026 community, 73 against 42\n- Transparency \u0026 trust, 54 against 29\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### Agent ergonomics: Tencent Cloud TokenHub +66\n\n- Simplismart (17): Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). The LiveKit guide calls the LLM API fully OpenAI-compatible, but no page documents tools or tool_choice, and the OpenAPI files allow only system, user and assistant roles (3 of 20). No structured-output or JSON mode documented (0 of 15). No prompt caching documented for shared endpoints (0 of 15). Context lengths are not stated per model; output is capped at 4,096 tokens in the API files (3 of 15). No batch API for shared endpoints (0 of 10). Inference goes through the OpenAI client; the simplismart-sdk Python package and CLI manage repositories and deployments, not inference, and a community Pipecat package exists (5 of 10). Expired keys return a documented 401, and the SDK exposes status_code, message and payload, but no error codes or bodies are listed for the inference API (6 of 15). 3+0+0+3+0+5+6 = 17.\n- 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).\n\n### Security \u0026 auth: Tencent Cloud TokenHub +36\n\n- Simplismart (35): Model reading. Named Bearer keys with an expiry chosen at creation, a 401 after expiry and immediate deletion. No scopes or per-key limits found, keys belong to the organisation, and the SDK uses a separate Playground token (20 of 30). No statement on training on API data in the terms, the privacy policy, the AI policy or the docs (0 of 20). No retention or zero-retention statement for prompts and outputs. The privacy policy covers the website only (0 of 15). The Usage page shows request counts and a per-request timeline per model, and an LLM metrics call returns token counts and timings per request id. A Simplismart article claims exportable audit trails, not documented (8 of 15). The homepage shows GDPR, ISO 27001 v2022 and AICPA SOC 2 badges, and a Simplismart article says it holds a SOC 2 Type 2 report, available on request. No trust centre was reachable, security.txt answered 404, and no disclosure policy or bug bounty was found (7 of 20). 20+0+0+8+7 = 35.\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### Reliability: Tencent Cloud TokenHub +31\n\n- Simplismart (15): Hosted reading. No status page found. The docs and site link none, a search found none, and status.simplismart.ai could not be reached from our network (0). No readable incident history (5). No request or token rate limits are published for shared endpoints. The docs give GPU quotas for training, compilation and private deployments only, 1 H100 and 1 L40 on the Quotas page and 8 of each on the Organisation page (0). No 429 response, Retry-After header or retry guidance found; the OpenAPI files list only 400, 401 and 500 (0). No SLA document found. The homepage claims 99.99% uptime and a Simplismart post calls its autoscaling SLA-backed, but no terms state a commitment, and the terms provide the service as is (0). Shared endpoints carry no beta label, while Muse Spark Open is in beta (10). 0+5+0+0+0+10 = 15.\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### Maintenance \u0026 community: Tencent Cloud TokenHub +31\n\n- Simplismart (42): Model reading for a closed service. Muse Spark Open was added in beta on 19 October 2026, and the docs sitemap shows pages changed on 7 October (30). No deprecation policy or notice period found (0 of 12). One dated model addition in the 90 days to 28 October and no recorded removals; the pricing page still lists Llama 3.1 405B and DeepSeek-R1, which the API reference doesn't cover, so the live model set is unclear (2 of 8). No public changelog or community channel. Support is support@simplismart.ai and a contact form, not tested (4 of 15). SDK issue replies not read, because github.com gave no readable robots.txt (0 of 10). simplismart-sdk for Python, documented with a CLI, and the OpenAI client for inference. No TypeScript SDK, and the PyPI page answered with a browser challenge, so the version and date are unchecked (6 of 15). CI not checked (0 of 10). 30+0+2+4+0+6+0 = 42.\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### Transparency \u0026 trust: Tencent Cloud TokenHub +25\n\n- Simplismart (29): Closed service. The terms, last updated 13 January 2023, name Verute Technologies Private Limited and Indian law but define the Service as the website, grant Simplismart a licence to use and redistribute posted Content, bar robots and automatic access, and rule out refunds. No API or platform terms were found (8 of 30). The privacy policy, effective 13 January 2023, is a website policy that says personal data is processed in India. It says nothing about prompts, outputs, logs or training, and no DPA, retention period or subprocessor list was found. A Simplismart article claims GDPR and HIPAA support (3 of 30). No deprecation policy or dated removals (0 of 20). Data goes to India per the privacy policy, and an article says workloads are kept in approved regions by scheduling policy. No subprocessor or hosting-provider list (3 of 20). 8+3+0+3 = 14.\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### Schema \u0026 documentation: Tencent Cloud TokenHub +22\n\n- Simplismart (51): Model reading. OpenAPI 3.1 files for seven LLMs and 3.0 or 3.1 files for Whisper, Flux, an LLM metrics call and training jobs. They cover a handful of the 150+ models, omit tools and response_format, show a streaming `delta` as the non-streaming response, and several name hosts on s9t.link instead of api.simplismart.live. The Llama 4 Maverick file gives `llama3_1` as its only model id, and /api-reference/openapi.json is the Flux spec (12 of 25). llms.txt and a Markdown copy of each docs page (10). The docs say when to use shared or dedicated endpoints; model pages carry one-line descriptions (10 of 20). Roles are enums, temperature is bounded 0 to 2, max_tokens 1 to 4096, and messages and model are required (10 of 15). curl and OpenAI-client Python examples. Errors are bare 400, 401 and 500 descriptions, plus an SDK example of a 404 payload (7 of 15). No changelog. Every spec reads version 1.0.0 (2 of 15). 12+10+10+10+7+2 = 51.\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## Score by category\n\n| Category | Weight | Simplismart | Tencent Cloud TokenHub | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 46 | Tencent Cloud TokenHub +31 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 51 | 73 | Tencent Cloud TokenHub +22 |\n| Agent ergonomics | 13% (16.2 this run) | 17 | 83 | Tencent Cloud TokenHub +66 |\n| Security \u0026 auth | 14% (17.5 this run) | 35 | 71 | Tencent Cloud TokenHub +36 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 35 | Tencent Cloud TokenHub +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 42 | 73 | Tencent Cloud TokenHub +31 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 29 | 54 | Tencent Cloud TokenHub +25 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **29.5 · F** | **59.5 · C** | |\n\n## Facts side by side\n\n| Fact | Simplismart | Tencent Cloud TokenHub |\n| --- | --- | --- |\n| Kind | HTTP API | Model router |\n| Vendor | Verute Technologies Private Limited | Tencent Cloud |\n| Hosted endpoint | `https://api.simplismart.live` | `https://tokenhub.tencentmaas.com/v1` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary hosted service. The community Pipecat integration (pipecat-simplismart, by the simpli-smart GitHub account) is BSD-2-Clause; served models keep 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-19 | 2026-10-24 |\n| Terms last updated | 2023-01-13 | couldn't be read |\n| Privacy policy last updated | 2023-01-13 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\n| Popularity | none | 204 npm/wk |\n\n## How the scores have moved\n\n### Simplismart\n\n- -0.2 on 30 October 2026: checklist\n\n### Tencent Cloud TokenHub\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Simplismart.** Simplismart exposes open models through an OpenAI-compatible endpoint with public per-token prices and expiring, revocable keys. Its public docs give no request rate limits, status page, retry guidance, tool-calling or structured-output reference, and its terms and privacy policy cover the website, not API data.\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### Simplismart\n\n1. Point an OpenAI-compatible client at https://api.simplismart.live with SIMPLISMART_API_KEY as a Bearer token, and take model ids from the marketplace or the per-model API pages.\n2. Set a key expiry and rotate before midnight UTC on the expiry date, because an expired key returns 401.\n3. Cap retries yourself with exponential backoff, because no rate limits, 429 format or retry guidance are published.\n4. Check that a model supports tools or JSON output with a test call before relying on it, because neither is documented.\n5. Confirm the per-token price of the exact model in the console before running large jobs, because the public price list is incomplete.\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, Simplismart or Tencent Cloud TokenHub?\n\nTencent Cloud TokenHub scores 59.5 (C) on agent readiness against Simplismart's 29.5 (F), and leads in every scored category.\n\n### Do Simplismart and Tencent Cloud TokenHub need an API key?\n\nBoth need an API key.\n\n### Can an agent call Simplismart and Tencent Cloud TokenHub without installing anything?\n\nYes. Simplismart has a hosted endpoint at https://api.simplismart.live 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/simplismart-vs-tencent-tokenhub.json, and with the fewest tokens: https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"simplismart\", \"b\": \"tencent-tokenhub\"}`. From a terminal: `anchor compare simplismart tencent-tokenhub`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/simplismart.json and https://www.anchorterminal.com/api/v1/tools/tencent-tokenhub.json\n\n## Other comparisons with Simplismart or Tencent Cloud TokenHub\n\n- [Claude API vs Simplismart](https://www.anchorterminal.com/compare/anthropic-api-vs-simplismart.md)\n- [Claude API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/anthropic-api-vs-tencent-tokenhub.md)\n- [Antseed vs Simplismart](https://www.anchorterminal.com/compare/antseed-vs-simplismart.md)\n- [BlockRun.AI vs Simplismart](https://www.anchorterminal.com/compare/blockrun-ai-vs-simplismart.md)\n- [BlockRun.AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/blockrun-ai-vs-tencent-tokenhub.md)\n- [Cerebras Inference vs Simplismart](https://www.anchorterminal.com/compare/cerebras-inference-vs-simplismart.md)\n- [Cerebras Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cerebras-inference-vs-tencent-tokenhub.md)\n- [Cloudflare AI Gateway vs Simplismart](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-simplismart.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 Simplismart](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-simplismart.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 Simplismart](https://www.anchorterminal.com/compare/cohere-chat-vs-simplismart.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 Simplismart](https://www.anchorterminal.com/compare/deepinfra-vs-simplismart.md)\n- [DeepInfra vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepinfra-vs-tencent-tokenhub.md)\n- [DeepSeek API vs Simplismart](https://www.anchorterminal.com/compare/deepseek-api-vs-simplismart.md)\n- [DeepSeek API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/deepseek-api-vs-tencent-tokenhub.md)\n- [Glimpse vs Simplismart](https://www.anchorterminal.com/compare/elorian-glimpse-vs-simplismart.md)\n- [Glimpse vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/elorian-glimpse-vs-tencent-tokenhub.md)\n- [Fireworks AI Inference vs Simplismart](https://www.anchorterminal.com/compare/fireworks-inference-vs-simplismart.md)\n- [Fireworks AI Inference vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/fireworks-inference-vs-tencent-tokenhub.md)\n- [Gemini Developer API vs Simplismart](https://www.anchorterminal.com/compare/gemini-api-vs-simplismart.md)\n- [Gemini Developer API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/gemini-api-vs-tencent-tokenhub.md)\n- [GroqCloud vs Simplismart](https://www.anchorterminal.com/compare/groq-vs-simplismart.md)\n- [GroqCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/groq-vs-tencent-tokenhub.md)\n- [Jais 3 vs Simplismart](https://www.anchorterminal.com/compare/jais-3-vs-simplismart.md)\n- [Jais 3 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/jais-3-vs-tencent-tokenhub.md)\n- [Meta Model API vs Simplismart](https://www.anchorterminal.com/compare/meta-model-api-vs-simplismart.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 Simplismart](https://www.anchorterminal.com/compare/minimax-api-vs-simplismart.md)\n- [MiniMax API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/minimax-api-vs-tencent-tokenhub.md)\n- [Mistral AI API vs Simplismart](https://www.anchorterminal.com/compare/mistral-api-vs-simplismart.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 Simplismart](https://www.anchorterminal.com/compare/muse-spark-open-vs-simplismart.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 Simplismart](https://www.anchorterminal.com/compare/novita-ai-vs-simplismart.md)\n- [Novita AI vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/novita-ai-vs-tencent-tokenhub.md)\n- [OpenAI API vs Simplismart](https://www.anchorterminal.com/compare/openai-api-vs-simplismart.md)\n- [OpenAI API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openai-api-vs-tencent-tokenhub.md)\n- [OpenRouter vs Simplismart](https://www.anchorterminal.com/compare/openrouter-vs-simplismart.md)\n- [OpenRouter vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/openrouter-vs-tencent-tokenhub.md)\n- [Prism Inference vs Simplismart](https://www.anchorterminal.com/compare/prism-inference-vs-simplismart.md)\n- [Router.com (Ramp Router) vs Simplismart](https://www.anchorterminal.com/compare/ramp-router-vs-simplismart.md)\n- [Beam 1.0 vs Simplismart](https://www.anchorterminal.com/compare/reflection-beam-vs-simplismart.md)\n- [Beam 1.0 vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/reflection-beam-vs-tencent-tokenhub.md)\n- [RouterPlus vs Simplismart](https://www.anchorterminal.com/compare/routerplus-vs-simplismart.md)\n- [SambaCloud vs Simplismart](https://www.anchorterminal.com/compare/sambanova-vs-simplismart.md)\n- [SambaCloud vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/sambanova-vs-tencent-tokenhub.md)\n- [SiliconFlow vs Simplismart](https://www.anchorterminal.com/compare/siliconflow-vs-simplismart.md)\n- [SiliconFlow vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/siliconflow-vs-tencent-tokenhub.md)\n- [Simplismart vs StepFun API](https://www.anchorterminal.com/compare/simplismart-vs-stepfun-api.md)\n- [Simplismart vs Together AI Inference](https://www.anchorterminal.com/compare/simplismart-vs-together-inference.md)\n- [Simplismart vs Vercel AI Gateway](https://www.anchorterminal.com/compare/simplismart-vs-vercel-ai-gateway.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 Simplismart](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-simplismart.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": "Simplismart vs Tencent Cloud TokenHub", "url": "" } ], "description": "Tencent Cloud TokenHub scores 59.5 (C) to Simplismart's 29.5 (F) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Simplismart F 29.5", "Tencent Cloud TokenHub C 59.5", "scores" ], "h1": "Simplismart vs Tencent Cloud TokenHub", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/simplismart-vs-tencent-tokenhub", "published": "2026-10-01", "section": "tools", "title": "Simplismart vs Tencent Cloud TokenHub for AI agents (2026)", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/simplismart-vs-tencent-tokenhub" }, "tokens": { "markdown": 7150, "slim": 4080 }, "version": 1 }