Gemini 4 Carbon vs Tencent Hy4
Which one, when
Base output costs $10 vs $2.501 per million tokens (gemini-4-carbon vs hy4). Choose gemini-4-carbon for direct audio or video input and budget for its scheduled price change. Against gemini-4-carbon, consider hy4 for long Chinese or English documents with embedded screenshots.
Benchmarks
Tencent Hy4: the vendor has not published benchmark scores.
Vendor-published: Google
Pricing
| Gemini 4 Carbon | Tencent Hy4 | Δ | |
|---|---|---|---|
| Input / 1M tokens | $2 | $0.834 | 2.4× |
| Output / 1M tokens | $10 | $2.501 | 4× |
| Cache read / 1M tokens | $0.1 | $0.042 | 2.4× |
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
| Gemini 4 Carbon | Tencent Hy4 | |
|---|---|---|
| Tool calling | yes | yes |
| Thinking control | always on | yes (vendor dial not published) |
| Structured output | yes | - |
| Prompt caching | implicit (automatic) | implicit (automatic) |
| Cache lifetime | not published | not published |
| Minimum cached prefix | 4,096 tokens | not published |
Specs
| Gemini 4 Carbon | Tencent Hy4 | |
|---|---|---|
| Input modalities | text image audio video | text image |
| Output modalities | text | text |
| Released | 2026-11-10 | 2026-11-04 |
| Knowledge cutoff | 2026-03 | - |
| Context window | 1,048,576 | 1,048,576 |
| Max output | 65,536 | 65,536 |
| Thinking parameter | thinking_level | - |
| Accepted values | thinking_level
"minimal" and thinking_budget return 400 | - |
| Default | medium | - |
Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: Gemini 4 Carbon · Tencent Hy4
One prompt, both models, measured through the gateway
Gemini 4 Carbon passed · 3 sentences
Enabling reasoning instructs the AI to generate a lengthy, behind-the-scenes "thought process" to verify its logic before delivering a final answer. Because our vendor bills us based on total output volume, we are charged for all of that invisible scratchpad work in addition to the visible response, effectively doubling the compute consumed per query. Moving forward, we can control this cost by restricting reasoning strictly to complex, high-stakes workflows where higher accuracy justifies the premium, while routing routine tasks back to standard, lower-cost models.
out 908 tok (+799 thinking) latency 18.0 s
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
Instruction following (exactly three sentences, so countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.
Gemini 4 Carbon 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 best = max(best, cur) else: cur = 1 return best ``` The original function counts the number of matching adjacent *transitions* rather than the number of *elements* in a run because `best` and `cur` are initialized and reset to `0` instead of `1`. Because a single item on its own already forms a run of length `1`, starting at `0` causes every non-empty result to be short by one: single-element lists (where the loop never executes) and lists with no duplicates return `0` instead of `1`, and any run of $k$ equal items—including one ending at the last index—only increments `cur` $k - 1$ times, making it appear as though the final element of the run was missed. […]
out 1411 tok (+1131 thinking) latency 32.7 s
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
Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.
Gemini 4 Carbon passed · 5/5 fields, guidance null
```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": null, "growth_pct": null, "guidance": null } ```
out 3338 tok (+3281 thinking) latency 61.6 s
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
Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.
Gemini 4 Carbon passed · 120 words, 0 banned, 1 question
Are your engineering teams paying multiple AI vendors to generate identical responses? Today, we are introducing Universal Prompt Caching for our flagship API Gateway. When applications route traffic across providers like OpenAI, Anthropic, and Mistral, duplicate queries drain budgets and degrade user experiences. Our new unified caching layer intercepts incoming prompts directly at the network edge. If an identical request was previously fulfilled by any connected model, the gateway delivers the stored response in milliseconds, completely bypassing external API calls. This practical upgrade cuts monthly token expenses substantially while accelerating overall application speed. Best of all, deployment requires zero complex code changes. Simply activate this capability inside your gateway configuration dashboard today to start reducing latency and infrastructure costs immediately.
out 2620 tok (+2480 thinking) latency 31.1 s
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
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="gemini-4-carbon",
# model="hy4", # 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: "gemini-4-carbon",
// model: "hy4", // 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": "gemini-4-carbon",
# "model": "hy4", # 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: "gemini-4-carbon",
// Model: "hy4", // 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("gemini-4-carbon")
// .model("hy4") // 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, Gemini 4 Carbon or Tencent Hy4?
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 Gemini 4 Carbon against Tencent Hy4 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 Gemini 4 Carbon and Tencent Hy4 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.