Tencent: Hy3
Try Hy3 on us. Starter credit covers your first requests, then one key reaches all 4 provider routes with automatic failover.
tencent/hy3
| Publisher | Tencent Cloud TokenHubtencent |
|---|---|
| AI IQ | IQ 99 #133 on AI IQ |
| Context | 262,144 tokens |
| Providers | |
| Credits routes | 4 provider routes |
| Modes | chat US providers |
| Billing | Credits |
Current route evidence
Live leaderboardRecent provider-route uptime spans 100.00% across 4 routes and 4 providers. Price comes from the current Credits catalog. Speed and uptime come from routed probes rather than vendor claims.
Providers serving this model
Sorted by lowest combined prompt and completion price. Use
"provider": {"sort": "throughput"} in the request body
(or append :nitro to the model id) to route to the
fastest provider instead.
Trust boundary: TR router attestation verifies the TrustedRouter gateway only. Provider policy separately describes the upstream model host's retention, confidential compute, and E2EE posture. Company country is separate from inference location. Weight formats are source-backed declarations, not per-request proofs.
| Provider | Input | Cached input | Output | Weight format | Provider policy | Company / inference location | Measured speed |
|---|---|---|---|---|---|---|---|
| SiliconFlowsiliconflow | $0.13926/1M | $0.034815/1M | $0.55704/1M | Unknown |
privacy unknown
Retention detailsNo provider-ZDR claim is tracked here. SiliconFlow's privacy policy source is linked for retention and interaction-data terms. |
Operator country: SG
Location detailsHeadquarters / registered office: Singapore (international API operator). Company location source (reviewed 2026-09-27). Inference: Inference countries unconfirmed; no verified country-specific residency commitment. TrustedRouter uses api.siliconflow.com. Neither its hostname nor the provider's Singapore legal jurisdiction establishes the DeepSeek V4.1 Flash GPU location. No exhaustive route-specific country list verified. Region pinning through TR: Not supported by the current TrustedRouter integration. Reviewed 2026-09-26. |
TTFT: insufficient data
Speed: insufficient data
Last sample:
|
| Tencent Cloud TokenHubtencent | $0.13926/1M | $0.034815/1M | $0.55704/1M | Unknown |
privacy unknown
Retention detailsTokenHub's Singapore API uses global resource scheduling, not a Singapore-only inference guarantee. Only canaried chat routes with matching regional USD prices are enabled. No verified contractual ZDR, confidential-compute, or upstream E2EE claim is tracked. |
Operator country: Not verified
Location detailsHeadquarters / registered office: Not verified. Inference: Global, dynamically scheduled inference; no fixed-country residency commitment. The Singapore TokenHub ingress uses global resource scheduling. Ingress location is not GPU residency. Region pinning through TR: Not supported by the current TrustedRouter integration. Reviewed 2026-09-29. |
TTFT: insufficient data
Speed: insufficient data
Last sample:
|
| Novita AInovita | $0.1477/1M | $0.036925/1M | $0.6119/1M | Unknown |
privacy unknown
Retention detailsNo provider-ZDR claim is tracked here. Novita's privacy policy says personal information is not used for model training; customer-content processing is governed by customer agreements. |
Operator country: US
Location detailsHeadquarters / registered office: San Francisco, California, United States. Company location source (reviewed 2026-09-27). Inference: Shared inference API; processing countries unconfirmed, no fixed-region commitment. No exhaustive inference-country list verified for the shared model API. Novita publishes worldwide GPU rental regions, but that separate product does not establish shared serverless model placement. Region pinning through TR: Not supported by the current TrustedRouter integration. Reviewed 2026-10-28. |
TTFT: insufficient data
Speed: insufficient data
|
| Atlas Cloudatlas-cloud | $0.211/1M | $0.05275/1M | $0.844/1M | Unknown |
privacy unknown
Retention detailsAtlas Cloud publishes a platform zero-retention policy, while its aggregated model routes can involve downstream providers. TrustedRouter keeps the public route tier conservative pending downstream-path contractual verification. |
Operator country: US
Location detailsHeadquarters / registered office: Not verified. Inference: Inference location not verified; no country-specific residency commitment. No inference-location declaration has been verified for this provider. Region pinning through TR: No verified provider-specific location pin documented here. |
TTFT: insufficient data
Speed: insufficient data
Last sample:
|
Speed is the median (p50) from TR's recent measured requests for this exact model and provider, refreshed from the cached leaderboard. At least two timing samples are required; workload and network conditions affect results. Performance details
Endpoint JSON: https://api.trustedrouter.com/v1/models/tencent/hy3/endpoints
Compare Tencent: Hy3
All comparisons- Tencent: Hy3 vs Z.ai: GLM 5.337 combined provider routes
- Tencent: Hy3 vs Z.ai: GLM 5.236 combined provider routes
- Tencent: Hy3 vs Z.ai: GLM 5.3 Flash36 combined provider routes
- MoonshotAI: Kimi K3 vs Tencent: Hy332 combined provider routes
- DeepSeek: DeepSeek V4 Flash 0731 vs Tencent: Hy330 combined provider routes
- DeepSeek: DeepSeek V4.1 Flash vs Tencent: Hy328 combined provider routes
Questions
What model ID should I use for Tencent: Hy3?
Use tencent/hy3 as the model field with the TrustedRouter OpenAI-compatible API. Credits routing and provider fallback happen behind that model ID.
Which providers serve Tencent: Hy3?
TrustedRouter currently lists Novita AI, SiliconFlow, Tencent Cloud TokenHub, and Atlas Cloud for Tencent: Hy3. Provider availability and routing eligibility can change as catalog and health data update.
How much does Tencent: Hy3 cost through TrustedRouter?
The current lowest Credits input price is $0.13926/1M and the lowest Credits output price is $0.55704/1M. Prices are per one million tokens and come from the current route catalog.
How do I require zero data retention for Tencent: Hy3?
Set provider.min_privacy to zdr on the request. TrustedRouter considers only routes with a recorded zero-data-retention posture and fails closed if no eligible route remains.