Tencent Hy4 vs Kimi K3.1 Pro Highspeed
Which one, when
Both take text and image inputs. Start with hy4 for lower token rates and test kimi-k3.1-pro-highspeed if interactive response time is worth a higher rate.
Pricing
| Tencent Hy4 | Kimi K3.1 Pro Highspeed | Δ | |
|---|---|---|---|
| Input / 1M tokens | $0.834 | $4 | 0.21× |
| Output / 1M tokens | $2.501 | $20 | 0.13× |
| 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)
Capabilities
| Tencent Hy4 | Kimi K3.1 Pro Highspeed | |
|---|---|---|
| Tool calling | yes | yes |
| Thinking control | yes (vendor dial not published) | yes (vendor dial not published) |
| 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 Highspeed | |
|---|---|---|
| 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 | 131,072 |
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 Highspeed
One prompt, both models, measured through the gateway
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 Highspeed passed · 3 sentences
Enabling reasoning makes the model generate extra “thinking” tokens before each answer, so every request consumes more compute and output tokens even when the visible response stays short. Those reasoning tokens are typically billed, and the new configuration may also use a more expensive model or processing tier, raising both usage and unit cost. To control spend, we should verify reasoning-token volume and model pricing on the invoice, then cap reasoning effort and reserve it for high-value tasks.
out 410 tok (+410 thinking) latency 8.6 s
Instruction following (exactly three sentences, so countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.
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 Highspeed passed · 8/8 cases
```python def longest_run(xs): if not xs: return 0 best = 1 cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 best = max(best, cur) return best ``` The bug is counter bookkeeping, not the loop bounds: `cur` starts at zero, so the original counts equal adjacent pairs rather than items and never records a run for a single-element input. Runs are therefore reported one short, with singleton runs appearing as zero, including runs reaching the last index. The fix treats each item as a run of length one, resets `cur` to one on a mismatch, and updates `best` after every step, so a trailing run is recorded without needing a following mismatch; empty input returns `0`.
out 2102 tok (+2079 thinking) latency 31.7 s
Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.
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 Highspeed passed · 5/5 fields, guidance "Formal guidance withheld pending the Q4 "
{ "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": "Formal guidance withheld pending the Q4 close" }
out 2170 tok (+2170 thinking) latency 29.3 s
Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.
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 Highspeed passed · 120 words, 0 banned, 1 question
Introducing Cross-Provider Prompt Cache, a new API gateway feature that stores prompt responses and serves them across model providers. By reusing responses, teams can reduce latency, cut duplicate inference costs, and keep applications responsive during traffic spikes. You choose cache lifetime, scope, and eligibility rules, while provider credentials and routing policies remain under your control. Built-in metrics show hit rates, savings, and response times, helping you tune performance with confidence. Sensitive workloads can bypass caching, and entries expire according to your retention settings. Ready to spend less on repeated prompts? Enable the feature from your gateway configuration, define a cache policy, and start measuring results today. Cross-Provider Prompt Cache is available now, with documentation and examples in the developer console.
out 2161 tok (+2151 thinking) latency 23.5 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-highspeed", # uncomment this line, comment the one above
messages=[{"role": "user", "content": "Summarize this diff"}],
reasoning_effort="medium",
)
print(resp.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://synthorai.io/v1",
apiKey: "sk-syn-...",
});
const resp = await client.chat.completions.create({
model: "hy4",
// model: "kimi-k3.1-pro-highspeed", // uncomment this line, comment the one above
messages: [{ role: "user", content: "Summarize this diff" }],
reasoning_effort: "medium",
});
console.log(resp.choices[0].message.content);curl https://synthorai.io/v1/chat/completions \
-H "Authorization: Bearer sk-syn-..." \
-H "Content-Type: application/json" \
-d '{
"model": "hy4",
# "model": "kimi-k3.1-pro-highspeed", # uncomment this line, comment the one above
"messages": [{"role": "user", "content": "Hello"}],
"reasoning_effort": "medium"
}'package main
import (
"context"
"fmt"
"github.com/openai/openai-go/v3"
"github.com/openai/openai-go/v3/option"
)
func main() {
client := openai.NewClient(
option.WithBaseURL("https://synthorai.io/v1"),
option.WithAPIKey("sk-syn-..."),
)
resp, _ := client.Chat.Completions.New(context.TODO(), openai.ChatCompletionNewParams{
Model: "hy4",
// Model: "kimi-k3.1-pro-highspeed", // uncomment this line, comment the one above
Messages: []openai.ChatCompletionMessageParamUnion{
openai.UserMessage("Summarize this diff"),
},
ReasoningEffort: openai.ReasoningEffortMedium,
})
fmt.Println(resp.Choices[0].Message.Content)
}import com.openai.client.OpenAIClient;
import com.openai.client.okhttp.OpenAIOkHttpClient;
import com.openai.models.chat.completions.*;
import com.openai.models.ReasoningEffort;
OpenAIClient client = OpenAIOkHttpClient.builder()
.baseUrl("https://synthorai.io/v1")
.apiKey("sk-syn-...")
.build();
ChatCompletion resp = client.chat().completions().create(
ChatCompletionCreateParams.builder()
.model("hy4")
// .model("kimi-k3.1-pro-highspeed") // uncomment this line, comment the one above
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));FAQ
Which is cheaper, Tencent Hy4 or Kimi K3.1 Pro Highspeed?
Tencent Hy4 is cheaper on the "Input / 1M tokens" row ($0.834 vs $4, 4.8× 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 Highspeed 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 Highspeed 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.