Kimi K2.7 Code vs Gemini 2.5 Flash
Kimi K2.7 Code is an open-weight chat model you can call on this endpoint; Gemini 2.5 Flash is a closed model from Google. Below: what each costs for three realistic workloads, the limits that apply, and when to choose which.
Google figures are public list prices and documented limits, checked 2026-09-16 against the provider page. Inference APIs prices are read live from the price list.
- Cost: Gemini 2.5 Flash is cheaper in all three workloads, by 45–61%.
- Limits: Google: Free tier has per-model daily request quotas and returns 429 RESOURCE_EXHAUSTED when they are used; paid tier is self-serve. Here: no per-minute or per-day caps.
Side by side
| Kimi K2.7 Code | Gemini 2.5 Flash | |
|---|---|---|
| Served by | Inference APIs | |
| Model author | Moonshot AI | |
| Model id | moonshotai/Kimi-K2.7-Code | gemini-2.5-flash |
| Input price | $0.89 / 1M tokens | $0.30 / 1M tokens |
| Output price | $4.42 / 1M tokens | $2.50 / 1M tokens |
| Context window | 262K tokens | 1M tokens |
| Capabilities | Chat, Reasoning, Coding, Tool calling | Chat, Reasoning, Vision, Tool calling, JSON mode |
| Weights | Open | Closed |
| Status | Available | Available |
| Limits | No per-minute or per-day request or token caps; usage draws on a prepaid balance | Free tier has per-model daily request quotas and returns 429 RESOURCE_EXHAUSTED when they are used; paid tier is self-serve. |
| Time to first token | 0.87 s | not measured by us |
| Output speed | 40.7 tokens / s | not measured by us |
What three workloads cost
List prices applied to the same work. The cheaper side of each row is in bold.
| Workload | Kimi K2.7 Code | Gemini 2.5 Flash | Difference |
|---|---|---|---|
| Chat assistant — 10,000 turns of 800 tokens in, 300 out | $20.38 | $9.90 | 51% |
| Long prompts or RAG — 10,000 requests of 8,000 in, 500 out | $93.30 | $36.50 | 61% |
| Generation-heavy — 10,000 requests of 500 in, 2,000 out | $92.85 | $51.50 | 45% |
Gemini 2.5 Flash is cheaper in all three workloads, by 45–61%. Reasoning models bill their thinking as output tokens, so real output counts run higher than the visible answer; treat the generation-heavy row as a floor for them.
When to choose which
- You want open weights: the same model can be moved to another host or self-hosted later
- Coding agents: it is the coding-tuned model of Moonshot's Kimi family
- Your workload is output-heavy; output tokens are the expensive side of its price
- You need more than 262K tokens of context (it takes 1M)
- You need to send images; Kimi K2.7 Code is text-only
- Cost is the deciding factor; it is cheaper in every workload above
- You need multimodal input (images, audio, video)
- A free tier for development matters to you
Price, context and speed are measurable; answer quality on your task is not something a table can settle. Both take the same request, so the honest test is to run your own prompts through each.
Measured speed
Medians of three streamed runs on 2026-09-17, public endpoint, a prompt that asks for about 120 words. Time to first token is the first token of any kind, reasoning included; output speed counts every generated token from that point. Reasoning models then think before the visible answer starts: Kimi K2.7 Code began answering after 37.34 s at default settings, which you can shorten with the reasoning controls on each model page. Expect ±30% with time of day. We did not measure Google and do not quote other people's numbers; read "not measured" as unknown, not slow. Method and raw numbers: speed measurements.
Switching from Google
Both speak the OpenAI wire format. The edit is the base URL, the key and the model id; then re-run your own prompts, because it is a different model.
import os
from openai import OpenAI
# before: Google
# client = OpenAI(base_url="https://generativelanguage.googleapis.com/v1beta/openai/", api_key=os.environ["GOOGLE_API_KEY"])
# MODEL = "gemini-2.5-flash"
# after: Inference APIs
client = OpenAI(base_url="https://api.inferenceapis.com/v1", api_key=os.environ["INFERENCE_API_KEY"])
MODEL = "moonshotai/Kimi-K2.7-Code"
resp = client.chat.completions.create(model=MODEL, messages=[{"role": "user", "content": "Hello"}], max_tokens=500)More detail, including Node, LangChain and LiteLLM: switching OpenAI-compatible providers.
FAQ
Which is cheaper, Kimi K2.7 Code or Gemini 2.5 Flash?
Gemini 2.5 Flash is cheaper in all three workloads, by 45–61%. The table above uses list prices: Kimi K2.7 Code $0.89 / 1M tokens input, $4.42 / 1M tokens output; Gemini 2.5 Flash $0.30 / 1M tokens input, $2.50 / 1M tokens output.
Can I switch from Gemini 2.5 Flash to Kimi K2.7 Code without rewriting code?
Yes, if you call it through an OpenAI-compatible client. Change the base URL to https://api.inferenceapis.com/v1, swap the API key, and set the model to moonshotai/Kimi-K2.7-Code. Because it is a different model, re-run your prompts and evaluations before moving production traffic.
What limits apply to Gemini 2.5 Flash?
Free tier has per-model daily request quotas and returns 429 RESOURCE_EXHAUSTED when they are used; paid tier is self-serve. On Inference APIs there are no per-minute or per-day request or token caps; usage draws on a prepaid balance.
Why does Kimi K2.7 Code use more output tokens than the visible answer?
It is a reasoning model: it thinks before it answers and the thinking is billed as output tokens. Budget for that in output-heavy workloads, and set max_tokens to a few hundred or more so the answer is not cut off.
Spotted a price or limit that has changed? Tell us and we will re-check the provider page.