Free to start

deepseek-ai/DeepSeek-V3.1 vs Tencent: Hy4 preview

Try both on us. Starter credit covers your first requests, then one key routes deepseek-ai/DeepSeek-V3.1 and Hy4 preview. Switch by changing the model name.

Compare routesProviders, price, context, and policy posture in one view.

Use auto when uptime mattersKeep a primary model and let fallback handle provider failures.

Same API shapeUse the OpenAI client and set the model you want.

Practical read

Monthly evidence

deepseek-ai/DeepSeek-V3.1 has the lower published input-plus-output rate. Tencent: Hy4 preview has more Credits provider routes and the larger context window. There is not enough recent probe data to compare speed.

$1.266/1Mdeepseek-ai/DeepSeek-V3.1 cheapest route

$3.483242/1MTencent: Hy4 preview cheapest route

4068 msdeepseek-ai/DeepSeek-V3.1 fastest measured p50 TTFT via sambanova

not enough dataTencent: Hy4 preview fastest measured p50 TTFT

The price comparison adds each route's rate for one million input tokens and one million output tokens; your cost depends on your input/output mix. Prices and live route measurements can change. Use the monthly reports when you need a stable evidence window, then run a small task-specific eval before choosing a production default.

deepseek-ai/DeepSeek-V3.1Tencent: Hy4 preview

Model iddeepseek/deepseek-v3.1tencent/hy4-preview

Publisher DeepSeek Tencent Cloud TokenHub

AI IQ IQ 98#134 IQ 112#70

Context163,840 tokens1,048,576 tokens

Credits provider routes45

Cheapest route$1.266/1M$3.483242/1M

Cached input$0.13715/1M to $0.241595/1M$0.04431/1M to $0.435536/1M

Privacy postureprovider posture variesprovider posture varies

Fastest measured p50 TTFT4068 ms via sambanovanot enough data

Highest measured throughputnot enough datanot enough data

Recent route uptime range66.67% to 100.00%100.00%

Modes chat chat

deepseek-ai/DeepSeek-V3.1 routes

Overview4 Credits routes
PricingInput, cached input, and output rates
ProvidersAll serving providers

Tencent: Hy4 preview routes

Overview5 Credits routes
PricingInput, cached input, and output rates
ProvidersAll serving providers

Related comparisons

Browse every comparison

Tencent: Hy4 preview vs Z.ai: GLM 5.238 combined provider routes
Tencent: Hy4 preview vs Z.ai: GLM 5.338 combined provider routes
deepseek-ai/DeepSeek-V3.1 vs Z.ai: GLM 5.237 combined provider routes
deepseek-ai/DeepSeek-V3.1 vs Z.ai: GLM 5.337 combined provider routes
Tencent: Hy4 preview vs Z.ai: GLM 5.3 Flash37 combined provider routes
deepseek-ai/DeepSeek-V3.1 vs Z.ai: GLM 5.3 Flash36 combined provider routes
MoonshotAI: Kimi K3 vs Tencent: Hy4 preview33 combined provider routes
deepseek-ai/DeepSeek-V3.1 vs MoonshotAI: Kimi K332 combined provider routes

Production choice

Pick a default model. Keep fallback enabled.

TrustedRouter is useful when you know the model you want, but still need provider rollover, budget limits, usage records, and a prompt path you can verify.

OpenAI clientPython

client = OpenAI(
    base_url="https://api.trustedrouter.com/v1",
    api_key="sk-tr-v1-..."
)

response = client.chat.completions.create(
    model="deepseek/deepseek-v3.1",
    messages=messages,
)

Questions

Which should I use, deepseek-ai/DeepSeek-V3.1 or Tencent: Hy4 preview?

Is deepseek-ai/DeepSeek-V3.1 or Tencent: Hy4 preview cheaper?

The current cheapest TrustedRouter route is $1.266/1M for deepseek-ai/DeepSeek-V3.1 and $3.483242/1M for Tencent: Hy4 preview. The comparison uses current catalog prices and updates as provider pricing changes.

Is deepseek-ai/DeepSeek-V3.1 or Tencent: Hy4 preview faster?

Current measured p50 time to first token is 4068 ms for deepseek-ai/DeepSeek-V3.1 and not enough data for Tencent: Hy4 preview. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test deepseek-ai/DeepSeek-V3.1 and Tencent: Hy4 preview with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between deepseek/deepseek-v3.1 and tencent/hy4-preview. This makes side-by-side evals possible without maintaining two provider integrations.