Tencent Hy4 vs Router.com (Ramp Router)

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.

Router.com (Ramp Router) 22

Hosted reading. No status page found. status.router.com still does not resolve on 4 November, router.com/status answers 404, and neither the docs nor router.com link one (0). No readable incident history (5). No request or token rate limits are published. The docs say limits vary by model and list only technical limits, a 100 MiB body, 15 candidates and 100 keys per user (0). The errors page passes through provider retry-after and retry-after-ms, tells clients to respect them, gives a retry or fallback action for every 4xx and 5xx code, says retrying a 501 unchanged won't help and that a failed fallback candidate is not retried, and the fallbacks guide says truncated attempts are billed on top of later attempts. No idempotency key exists for the generation call that starts billing, so this is safe-retry guidance without keys (12). No SLA found in the docs or on router.com (0). The public API carries no beta label in the docs, and the docs llms.txt, re-read on 4 November, still says to treat 'beta pricing, limits, and enterprise controls as subject to change'. A 27 October reading of Ramp's product schedule came from the legal site's script and is no longer counted, so the line keeps its earlier partial value (5 of 10). 0 + 5 + 0 + 12 + 0 + 5 = 22.

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. No OpenAPI file for inference; field pages for the OpenAI and Anthropic formats as TokenHub implements them (12 of 25). llms.txt with Markdown copies (10). The model list, updated 9 November, gives hy4's context, input and output limits and marks thinking, structured output, function calling, caching and image understanding; computer use, which Tencent's release names, isn't marked (13 of 20). Typed field pages (10 of 15). Examples in five languages and an error page of 30 codes (14 of 15). Dated release notes, with hy4 added on 4 November (14 of 15). 12 + 10 + 13 + 10 + 14 + 14 = 73.

Router.com (Ramp Router) 58

Router, scored on the API lines. No OpenAPI or other machine-readable contract found. /openapi.json on docs.router.com returns the docs app shell. The API follows the OpenAI and Anthropic wire formats, which this checklist doesn't credit to a router, the same reading as RouterPlus (0 of 25). llms.txt and a Markdown copy of every page at the same path with .md (10). Pages say which endpoint to prefer and why, what isn't served (embeddings, files, batches), which Chat Completions controls return 501, and which workload suits which job (17 of 20). Router-only fields are tabled with types and bounds, the route selector rules are stated (model or models but never both, 1 to 15 candidates), over-limit timeouts are a 400 naming the maximum, and the model list documents a typed router object with a schema_version. Request bodies otherwise follow the upstream formats (12 of 15). curl, OpenAI SDK, Anthropic SDK, LangChain, Vercel AI SDK, LlamaIndex and Pydantic AI examples, and an error reference with a status, code and action for each case (15). Paths sit under /v1 and the model object is versioned, but no API changelog or dated release notes were found (4 of 15).

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.

Router.com (Ramp Router) 60

No x402, MPP or L402 in any of the 41 docs pages. Calls draw on account credit (0). Per-token prices for every model are public at router.com/models and in the supported-models page without a login (20). Router.com says routing is free through 2026 and the first $26 of credits are free, and BYOK requests carry no Router charge. We did not sign up to confirm that no card is asked for (20). A person signs up in the browser with a US business email or Sign in with Ramp, and the CLI creates keys only after browser approval (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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.

Router.com (Ramp Router) 59

Router, read on the model lines for a closed service. The Ramp CLI that ships the router commands tagged v0.2.91 on 3 November 2026, a release that changes router.py and router_credentials.py, one of 81 tags since 6 August (30). Models carry a deprecated status and the docs list deprecated and retired models, but no notice period is stated, and the Baseten retirement note gives no date and says requests aren't redirected (4 of 12). Provider-specific Baseten ids and several Fireworks models were retired without dates. The API host moved from router-api.ramp.com to api.router.com, and the old host still answers (3 of 8). No public API changelog. Support is a dashboard button and router@ramp.com, not tested (5 of 15). ramp-cli issue replies were not read, because GitHub's API wasn't available to this session (3 of 10). No API SDK. The Ramp CLI (MIT, npm @ramp/router and @ramp/cli, tagged v0.2.91 in the repository, Homebrew; npm itself not read) sets up agents and keys (7 of 15). The CLI repository has CI, build, npm and router-integration workflows and a tests folder, with 46 commit days since 29 July. ci.yml runs cargo test and pytest on pushes to main, and the results were not readable (7 of 10).

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.

Router.com (Ramp Router) 64

Closed service. The Router Terms of Service, Router Privacy Notice and Provider Schedule render only with JavaScript. Their 27 October readings came from the legal site's script and are no longer counted, so the lines resting on them are held, as on ramp. The CLI is MIT (16 of 30). The docs FAQ states the one-year default recording, the opt-out and the PII step, and links Ramp's general privacy policy. Every link to the Router Privacy Notice answers 301 to that general policy (16 of 30). No deprecation policy found, and model retirements in the docs carry no dates (5 of 20). The docs FAQ names the providers whose infrastructure runs the models, says all models run on US infrastructure and points to the Provider Schedule for provider retention terms. No Router subprocessor list was found (13 of 20).

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.

Router.com (Ramp Router) 77

Router, read on the model lines (tool use, structured output, caching, context, batch, SDKs, errors). Tools pass through on Responses, Messages and Chat Completions, and GET /v1/models reports tools.supported and parallel per model, with null where Router doesn't know. Behaviour depends on the model (16 of 20). The docs say JSON Schema output is expected to work across providers subject to model support, and each model carries a structured_outputs flag. A request the provider can't represent is a 501 (12 of 15). Cache read and write prices per model, a prompt_cache_key session lease of 5 or 30 minutes that keeps a session on the provider with a warm cache, and cache_control on Messages (14 of 15). Contexts up to 1,050,000 tokens on GPT-6.1 Sol and 1,048,576 on Kimi K3, a judgement call since a router has no default model (15). No batch route; the docs say Router doesn't serve batches (0 of 10). No SDK of its own. The OpenAI and Anthropic SDKs work with a changed base URL, framework setups are documented, and the MIT Ramp CLI configures six coding agents (5 of 10). Typed codes for every error, a limit object naming the cap and who set it, an all-candidates-failed summary, request and trace ids on every response and the serving provider in a header (15).