Tencent Hy4 vs Kimi K3.1 Pro

vs

Which one, when

Both accept screenshots and long documents. Choose hy4 for lower input and output rates, or kimi-k3.1-pro when your integration requires structured output.

Pricing

Tencent Hy4 Kimi K3.1 Pro Δ
Input / 1M tokens $0.834 $2 0.42×
Output / 1M tokens $2.501 $10 0.25×
Cache read / 1M tokens $0.042 $0.2 0.21×

Rates from the live catalogue at build time; each model page carries the current rate card.

Where they sit · input price per 1M tokens across all 86 chat models on this billing unit (log scale)

Tencent Hy4 · $0.834 Kimi K3.1 Pro · $2
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

Capabilities

Tencent Hy4 Kimi K3.1 Pro
Tool calling yes yes
Thinking control yes (vendor dial not published) yes (vendor dial not published)
Structured output - yes
Prompt caching implicit (automatic) implicit (automatic)
Cache lifetime not published not published
Minimum cached prefix not published not published

Specs

Tencent Hy4 Kimi K3.1 Pro
Input modalities text image text image
Output modalities text text
Released 2026-11-04 2026-10-23
Context window 1,048,576 1,048,576
Max output 65,536 1,048,576

Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: Tencent Hy4 · Kimi K3.1 Pro

One prompt, both models, measured through the gateway

PROMPT Explain to a CFO, in exactly three sentences, why our LLM bill doubled after we enabled reasoning. CHECK exactly 3 sentences

Tencent Hy4 passed · 3 sentences

Enabling reasoning changed the unit economics of each request: the model now produces extra “reasoning tokens” and consumes more compute before it returns an answer, and those tokens are billed even if users never see them. Because our pricing is largely token-based, that extra work roughly doubled average cost per call, so flat request volume could still produce a doubled invoice. We are paying for better accuracy and less downstream rework on complex tasks, so the spend is justified only in high-value workflows and should be managed by cost per successful outcome.

out 1519 tok (+1409 thinking) latency 21.0 s

Kimi K3.1 Pro passed · 3 sentences

Enabling reasoning makes the model generate extra internal “thinking” tokens before responding, and these are typically billed at output-token rates even though users never see them. If request volume and pricing stayed flat but reasoning substantially increased tokens per request, the total bill could double. Compare pre- and post-change usage reports for reasoning tokens, then control costs with lower reasoning effort, token budgets, cheaper models, and selective use on tasks where the quality gain justifies the spend.

out 471 tok (+366 thinking) latency 14.3 s

Instruction following (exactly three sentences, so countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.

PROMPT This function is supposed to return the longest run of consecutive equal items, but callers report it is off by one on single-element inputs and misses runs that end at the last index. Fix it and explain the bug in one paragraph. CHECK fix passes tests

Tencent Hy4 passed · 8/8 cases

```python def longest_run(xs): n = len(xs) if n == 0: return 0 best = cur = 1 for i in range(1, n): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 best = max(best, cur) return best ``` The loop range already includes the last index; the real bug is that `cur` and `best` start at `0` and only increase on equal adjacent comparisons, so the function counts equality links (`L - 1` for a run of `L` equal items), not the items in the run: a single item has no link, and the first item of a final run is never counted, with no end-of-list flush to compensate. […]

out 4509 tok (+4263 thinking) latency 56.0 s

Kimi K3.1 Pro passed · 8/8 cases

```python def longest_run(xs): if not xs: return 0 best = cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: best = max(best, cur) cur = 1 return max(best, cur) ``` The original `cur` counts matching adjacent pairs rather than items: it starts at 0, so a singleton returns 0, and a run of `k` equal items is recorded as only `k - 1`. Its bookkeeping also never correctly finalizes the current run’s length at end of input. The fix starts every run at 1, records its length when a mismatch ends it, and takes a final `max` after the loop so a run ending at the last index is included; empty input returns 0.

out 2984 tok (+2785 thinking) latency 70.1 s

Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.

PROMPT Extract a JSON object with fields {company, quarter, revenue_usd_m, growth_pct, guidance} from this text. Use null for anything not stated; add no other fields. CHECK valid JSON, schema exact

Tencent Hy4 passed · 5/5 fields, guidance "withheld pending the Q4 close"

{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":"eleven and change","guidance":"withheld pending the Q4 close"}

out 9869 tok (+9827 thinking) latency 125.2 s

Kimi K3.1 Pro passed · 5/5 fields, guidance null

{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":11,"guidance":null}

out 454 tok (+410 thinking) latency 12.0 s

Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.

PROMPT Write a 120-word product announcement for an API gateway feature that caches prompts across providers. Forbidden words: "seamless", "unlock", "game-changer", "revolutionize", "empower". Exactly one sentence must be a question. CHECK 120 words, 0 banned words

Tencent Hy4 passed · 120 words, 0 banned, 1 question

Today we are introducing Cross Provider Prompt Cache for our API gateway, a feature that caches prompts and securely reuses them across all connected model providers. Teams can cut duplicate calls, reduce latency, and keep spend predictable when identical instructions appear in chat, search, agents, or batch jobs. What if one cached prompt could support traffic routed to any provider in your stack? Gateway policies control cache keys, time to live, tenant isolation, redaction, and fallback behavior, while usage metrics show hit rates and savings by application. Setup requires one configuration change, and existing client code stays intact. Cross Provider Prompt Cache is available in private beta today for enterprise plans, with general availability next month across all supported regions.

out 5744 tok (+5601 thinking) latency 57.6 s

Kimi K3.1 Pro passed · 120 words, 0 banned, 1 question

Meet Prompt Cache, our new API gateway feature for caching prompts and responses across model providers. It cuts token spend, lowers latency, and keeps applications responsive during traffic surges. Define cache keys, expiration rules, and tenant boundaries in one policy, then apply them to OpenAI, Anthropic, Gemini, or custom models without changing application code. Encryption, redaction, and immediate purges help protect sensitive data, while metrics reveal hit rates, savings, and performance by endpoint and provider. Need a faster way to handle repeated requests? Serve eligible results from cache and preserve your existing routing, fallback, and retry behavior. Available today in beta, Prompt Cache gives platform teams controls for cost, speed, and reliability, with no extra infrastructure to deploy or maintain.

out 2740 tok (+2576 thinking) latency 55.8 s

Constraint obedience (word budget, banned-word list, the single question), style fingerprint, and length control.

Switch between them with one line

Both ids are in every tab below; the highlighted pair of lines is the only edit. Same endpoint, same key, same request shape.

from openai import OpenAI

client = OpenAI(
    base_url="https://synthorai.io/v1",
    api_key="sk-syn-...",
)

resp = client.chat.completions.create(
    model="hy4",
    # model="kimi-k3.1-pro",  # uncomment this line, comment the one above
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

Get your API key →

FAQ

Which is cheaper, Tencent Hy4 or Kimi K3.1 Pro?

Tencent Hy4 is cheaper on the "Input / 1M tokens" row ($0.834 vs $2, 2.4× apart). Other rows may point the other way; the table above carries the full rate card, and real cost depends on your mix.

Can I A/B test Tencent Hy4 against Kimi K3.1 Pro without two integrations?

Yes. Both are served through the same OpenAI-compatible endpoint with one API key. Switching is a one-line change to the model id, so you can route a fraction of traffic to each and compare bills directly.

Do Tencent Hy4 and Kimi K3.1 Pro support prompt caching?

Yes. Both bill cache reads below their input rate, so warm-prefix workloads cost less than the list rates suggest. The exact cache-read rows are in the pricing table above.

Related comparisons