Tencent Hy4 vs MiniMax API

Tencent Hy4 71

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. Bearer keys limited by model, service, IP range and token quota, long-lived with no rotation (26 of 30). The terms say inputs aren't used to train Tencent Cloud's own models, and Hy4 is first party, so no third party's terms apply (14 of 20). Retention only as long as the service needs, no periods (7 of 15). Per-call audit logs and optional full logs to the customer's CLS (14 of 15). No security.txt; Tencent's TSRC bounty covers Tencent Cloud; no certification checked (10 of 20). 26 + 14 + 7 + 14 + 10 = 71.

MiniMax API 30

Model reading (credential, training, retention, operator visibility, programme). One bearer key per account on the pay-as-you-go side and a separate Subscription Key for M Plan, with no scopes found. MiniMax says it may disable keys that leak publicly (20 of 30). The terms, effective 30 March 2026 and unchanged on 4 November, say MiniMax may use input and generated content to provide, maintain, develop and improve its services, and no opt-out was found. The privacy policy says only that personal data isn't used for training to profile or target consumers (0 of 20). Data is kept as long as necessary for its purpose, with no period stated and no zero-retention route (5 of 15). A usage page and balance alerts, no audit log found (5 of 15). No security.txt on platform.minimax.io (404 again on 4 November) or api.minimax.io (per the 19 October check), and no bug bounty or certification found (0 of 20). Total 30.

Tencent Hy4 46

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. No public status page (0) and so no incident record to read (5 of 30). Per-model rate limits only in the console and DescribeModelQuota (8 of 15). Six 429 codes, Retry-After and backoff advice (13 of 15). The TokenHub SLA promises 99.5% a month, and Hy4 is Tencent's own model, so the third-party exclusion doesn't apply (10). Released as hy4 on 4 November, a separate id from hy4-preview, with no preview label (10). 0 + 5 + 8 + 13 + 10 + 10 = 46.

MiniMax API 75

Atlassian Statuspage at status.minimax.io with Large Language Models, Text-to-Speech and Video Generation components (20). Its history pages, re-read on 4 November, now cover the whole 90 days from 6 August. They list 212 incidents on the LLM component, every one titled 'Elevated errors on Large Language Models (LLM)' and labelled major, and none states a full outage. The longest ran 65 minutes (01:15 to 02:20 UTC on 20 October, 'We are currently investigating this issue' and then resolved), and the rest closed within the hour. This run reads elevated errors with no fuller scope as partial, so minor only, frequent as they are (20). The rate-limits page publishes 200 requests and 10,000,000 tokens a minute for M3.1 Flash and M3 (15). The Anthropic-format OpenAPI file documents 429 for rate limits and 529 as an overload that can be retried, and the error-code page says to retry later on 1002, 2064 and other codes, with no Retry-After header or backoff schedule found (10). No SLA found (0). M3.1 Flash and M3 are generally available (10). Total 75.

Tencent Hy4 73

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. Added on 4 November 2026 per the release notes; the model list and price page were updated on 9 November (30). Retirement notices of 21 to 33 days, no minimum written (7 of 12). Heavy retirement churn on the platform (3 of 8). Dated release notes and announcements, round-the-clock support (13 of 15). CLI replies not sampled (3 of 10). Control-plane SDKs and CLI, no inference SDK of its own (12 of 15). CLI runtime stated, CI not checked (5 of 10). 30 + 7 + 3 + 13 + 3 + 12 + 5 = 73. The model is a week old, so these lines are TokenHub's habits more than Hy4's record.

MiniMax API 45

Model reading. MiniMax-M3.1-Flash shipped on 19 October 2026, dated on the model release page, which has no newer entry on 4 November (16 days, 30). No stated notice policy. The M2.5 and M2.7 families closed to new users on 19 October and retire on 18 November, 30 days later, and from 19 October M Plan and Token Plan requests to them are served by M3.1 Flash under the old names. We couldn't find when that notice was first posted, and the page carries the same notice on 4 November (3 of 12). Churn is high. M2.5 (February 2026) and M2.7 (March 2026) retire within nine months of release, M2.1 and M2 are already retired, and the model list still calls M2.5 and M2.7 retired on 4 November while the notice on the same page gives 18 November (2 of 8). A dated release page, support email addresses on the contact and model pages, a Discord server and GitHub issues on the model repositories. We didn't test whether they answer (10 of 15). No official SDK (0 of 15, 0 of 10). Total 45.

Tencent Hy4 86

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. Function calling is marked for hy4 in the model list (18 of 20). Structured output marked (13 of 15). Cache-hit price published, ¥0.3 against ¥6 input (14 of 15). 1M-token context with 960K input and 64K output (15). Batch at half price covered Hy3 and Hy4 preview on 1 November; whether it covers hy4 wasn't re-read (3 of 10). OpenAI and Anthropic SDKs with a changed base URL, plus Tencent Cloud's SDK and CLI for the control plane (8 of 10). Errors with code, messages, upstream status and request ID (15 of 15). 18 + 13 + 14 + 15 + 3 + 8 + 15 = 86.

MiniMax API 59

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use on all three formats, with tool_choice on the Anthropic format only (17 of 20). No JSON Schema output mode documented on any format (0 of 15). Caching is automatic, with cache reads at a tenth of the input price on M3.1 Flash and a token-count endpoint for sizing a request (15). 1,000,000-token context and up to 524,288 output tokens (15). No batch API found (0). No official SDK. The docs point to the Anthropic and OpenAI SDKs and the AI SDK (0). Typed error bodies with a request id on the Anthropic format and a code table, though stop_sequences is ignored without an error (12 of 15). M3.1 Flash can't turn thinking off and defaults to the deepest effort, which costs output tokens unless the caller lowers it. Total 59.

Tencent Hy4 45

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. No machine payment protocol (0). The price page, updated 9 November, lists ¥6 input, ¥0.3 cached and ¥18 output per million tokens, with Hy4 billed at 50% until 31 December 2026 (20). TokenHub's campaign of 1M free tokens per language model, read on 1 November, isn't confirmed for hy4 on the price page, so half (10 of 20, a judgement call). A person signs up with real-name verification (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

MiniMax API 30

No x402, MPP or L402 (0). Per-token prices for M3.1 Flash and M3 are published without a login, unchanged on 4 November (20). No free tier found for the text models (0). A person signs up in a browser and tops up a balance or buys an M Plan before the first call (0). Total 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Tencent Hy4 52

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. Closed service under the TokenHub terms, but Tencent's release headline calls Hy4 open source while the weights and system card are only promised 'in the coming days', with no licence stated, and tencent/Hy4 didn't answer on Hugging Face on 11 November (14 of 30). Terms and FAQ agree inputs aren't used for training; the privacy policy renders only with JavaScript and wasn't read (15 of 30). Dated retirement notices and shutdown fields (13 of 20). Processing generally in mainland China for the China site, Singapore for the international one (13 of 20). Every benchmark in the release is Tencent's own or a partner's. 14 + 15 + 13 + 13 = 55.

MiniMax API 65

Closed service with clear terms under Singapore law and SIAC arbitration. MiniMax-M3's weights, and since 23 October 2026 MiniMax-M3.1-Flash's, are on Hugging Face under the MiniMax community licence, which isn't an OSI licence and doesn't change the hosted service (15). The terms and privacy policy, both still dated 30 March 2026 on 4 November, agree on the contracting entity, that inputs and outputs are processed and may be used to improve services, and that data sits in a United States data centre, but give no retention period and no DPA was read (10 of 30). A dated retirement notice for M2.5 and M2.7 and a retired-models table, undercut by the table contradicting the notice and API release notes a year stale (12 of 20). Data location stated as the United States and an EU representative named, with third parties named only by category (10 of 20). MiniMax publishes an EU AI Act training-data summary for M3. Total 47.