Claude Sonnet 5 vs Kimi K2.7 Code
Which one, when — curated verdict, not a benchmark table
Pick claude-sonnet-5 when you need room to work: its 1000000-token context is nearly 4x the 256000 of kimi-k2.7-code, it can emit up to 128000 tokens against 32768, and its thinking mode can be disabled, which kimi-k2.7-code does not allow. Pick kimi-k2.7-code to cut per-token spend on text and image work — $0.95 input and $4 output versus $2 and $10, roughly 2.1x and 2.5x cheaper — and it is the only one of the two that accepts video input. Cache reads are effectively a wash at $0.19 versus $0.2.
Pricing
| Claude Sonnet 5 | Kimi K2.7 Code | Δ | |
|---|---|---|---|
| Input / 1M tokens | $2 | $0.95 | 2.1× |
| Output / 1M tokens | $10 | $4 | 2.5× |
| Cache read / 1M tokens | $0.2 | $0.19 | 1.1× |
| Cache write | 1.25x (5m) / 2x (1h) | — | — |
Rates from the live catalog at build time; each model page carries the current card.
Where they sit — input price per 1M tokens across all 63 chat models on this billing unit (log scale)
Capabilities
| Claude Sonnet 5 | Kimi K2.7 Code | |
|---|---|---|
| Tool use | yes | yes |
| Thinking control | configurable | always on |
| Structured output | yes | — |
| Prompt caching | explicit (you mark the prefix) | implicit (automatic) |
| Cache lifetime | 5m default, 1h option | not published |
| Minimum cached prefix | 1024 tokens | not published |
Specs
| Claude Sonnet 5 | Kimi K2.7 Code | |
|---|---|---|
| Input modalities | text image | text image video |
| Output modalities | text | text |
| Released | 2026-06-30 | 2026-06 |
| Knowledge cutoff | 2026-01 | — |
| Context window | 1M | 256K |
| Max output | 128K | 33K |
| Thinking parameter |
|
|
| Accepted values | thinking.type
effort
"enabled" returns 400 | type
keep
|
| Default | thinking on (adaptive) effort
| thinking on with Preserved Thinking on |
Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: Claude Sonnet 5 · Kimi K2.7 Code
One prompt, both models — measured through the gateway
Claude Sonnet 5 passed · 3 sentences
Reasoning mode works by having the model generate extended internal "thinking" steps before producing its final answer, and since we're billed on total tokens, that hidden reasoning text adds significantly to what we pay for—even though you never see it in the output. This is different from simply getting longer visible responses; the model is essentially "showing its work" behind the scenes, and complex prompts can trigger thousands of extra reasoning tokens per request. The upside is improved accuracy on complex tasks, but if we want to control costs, we should selectively enable reasoning only for queries that truly need it, rather than applying it universally.
out 194 tok latency 4.3 s
Kimi K2.7 Code passed · 3 sentences
Enabling reasoning mode causes the model to generate an internal chain-of-thought before producing each answer, and that hidden reasoning text is billed like any other output. Those extra reasoning tokens typically add up to much more than the final response itself, so every API call now costs significantly more than before. Because our overall usage volume did not change, the doubled bill reflects that each query consumes roughly twice as many billable tokens.
out 259 tok (+174 thinking) latency 5.4 s
Instruction following (exactly three sentences — countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.
Claude Sonnet 5 passed · 8/8 cases
## The Bug The function has two related off-by-one issues rooted in the same cause: `cur` and `best` are initialized to `0` instead of `1`, treating run lengths as the number of *matches* between adjacent elements rather than the number of *elements* in the run. This means a single-element input never enters the loop (since `range(1, 1)` is empty) and returns `0` instead of the correct answer of `1`. It also means that for any input, the run length is undercounted by exactly one — a run of 3 equal elements only produces 2 "match" increments, so `best` ends up as 2 instead of 3. The claim that it "misses runs that end at the last index" is actually a symptom of this same undercount: the logic does update `best` correctly on every iteration (including the last), but because it's counting matches instead of elements, the final reported value is always one less than the true longest run. […]
out 536 tok latency 7.1 s
Kimi K2.7 Code 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 bug is that the function counts *transitions* between equal neighbors instead of counting the items themselves, so a single-element list never enters the loop and returns `0` instead of `1`. Likewise, resetting `cur` to `0` on a mismatch forgets the current item that starts a new run, which causes runs that end at the last index to be undercounted. Initializing both `best` and `cur` to `1` and resetting `cur` to `1` fixes both issues.
out 410 tok (+222 thinking) latency 9.4 s
Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.
Claude Sonnet 5 passed · 5/5 fields, guidance null
```json { "company": "Meridian Robotics", "quarter": "Q3", "revenue_usd_m": 412, "growth_pct": 11.5, "guidance": null } ```
out 348 tok latency 5.3 s
Kimi K2.7 Code passed · 5/5 fields, guidance "withheld pending the Q4 close"
```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": "withheld pending the Q4 close" } ```
out 721 tok (+663 thinking) latency 13.2 s
Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.
Claude Sonnet 5 passed · 123 words, 0 banned, 1 question
## Introducing Cross-Provider Prompt Caching We're rolling out a new caching layer for our API gateway that works across every major LLM provider you connect through it. Instead of resending identical prompts and paying full price each time, the gateway recognizes repeated requests and serves cached responses in milliseconds—regardless of whether you're routing to OpenAI, Anthropic, or Google. What does this mean for your bill and your latency? Both drop, often significantly, especially for teams running high-volume, repetitive workloads like customer support bots or batch content generation. The cache is configurable per route, with adjustable TTLs and invalidation rules, so you stay in control of freshness versus cost. Available now for all Pro and Enterprise plans. Check your dashboard to enable it today.
out 259 tok latency 4.8 s
Kimi K2.7 Code passed · 120 words, 0 banned, 1 question
We're introducing Prompt Cache for our API Gateway, a new capability that stores prompt responses across multiple AI providers. By caching replies, you reduce redundant calls, lower latency, and cut costs without changing how you build. Teams using several model providers can now reuse identical prompt results instantly, keeping traffic consistent and budgets predictable. Responses are keyed by provider, model, and exact prompt, so you always get the right result. Configure TTL, hit thresholds, and eviction rules from a single dashboard. It fits into your existing routing and requires no code changes. Setup takes minutes and works with your current endpoints. Want to see how much latency and spend you can trim? Check the docs to enable Prompt Cache today.
out 2375 tok (+2235 thinking) latency 38.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="claude-sonnet-5",
# model="kimi-k2.7-code", # 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: "claude-sonnet-5",
// model: "kimi-k2.7-code", // 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": "claude-sonnet-5",
# "model": "kimi-k2.7-code", # 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: "claude-sonnet-5",
// Model: "kimi-k2.7-code", // 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("claude-sonnet-5")
// .model("kimi-k2.7-code") // 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, Claude Sonnet 5 or Kimi K2.7 Code?
Kimi K2.7 Code is cheaper on input / 1m tokens ($0.95 vs $2, 2.1× apart). Other rows may point the other way — the table above carries the full card, and real cost depends on your mix.
Can I A/B test Claude Sonnet 5 against Kimi K2.7 Code without two integrations?
Yes. Both are served through the same OpenAI-compatible endpoint with one API key — switching is a one-line model-string change, so you can route a fraction of traffic to each and compare bills directly.
Do Claude Sonnet 5 and Kimi K2.7 Code support prompt caching?
Yes — both bill cached 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.