Moonshot (Kimi) · Flagship · 1M context window

Kimi K3 pricing for blog writing

$0.1230 per call at 1,000 input / 8,000 output tokens.

Per call

$0.1230

10K calls/mo

$1,230

Cache savings

90% off input

Batch savings

0% off all

Calculate your Kimi K3 costs

Adjust token counts, volume, and discount toggles to model your blog writing spend. Prices verified daily against provider pricing pages.

Configure your usage

1,000
100100K
8,000
5050K
10,000
1001M

Estimated cost

Monthly cost
$1,230
10,000 calls/month
Cost per call$0.123
Daily cost$41
Input rate$3.00/MTok
Output rate$15.00/MTok
Analyze your real spend

Quick start

Call Kimi K3 with the OpenAI Python SDK pointed at api.moonshot.cn:

import os
from openai import OpenAI

client = OpenAI(
    base_url="https://api.moonshot.cn/v1",
    api_key=os.environ["MOONSHOT_API_KEY"],
)
response = client.chat.completions.create(
    model="kimi-k3",
    max_tokens=8000,
    messages=[{"role": "user", "content": "Your prompt here"}]
)
# Cost: ~$0.1230 per call at standard rates
# Input:  $3.00/MTok
# Output: $15.00/MTok

What drives blog writing cost

The most output-heavy use case tracked here. A brief of a few hundred tokens produces an article of several thousand, so output pricing is essentially the entire cost and input rate is noise. Generating section by section rather than whole-article gives you more control over both quality and spend, at the cost of more calls.

For Kimi K3 specifically, that means output tokens cost 5.0x more than input, at $15.00 vs $3.00 per MTok. At this use case’s 1,000/8,000 token split, output accounts for 98% of the $0.1230 per-call cost.

Complete Kimi K3 pricing breakdown

Standard token rates

Direction$/MTokTokens per call
Input$3.001,000
Output$15.008,000

Prompt caching: 90% off input tokens

Caching drops input cost from $3.00 to $0.30/MTok. For repeated system prompts, that saves $0.002700 per call.

Batch API: 0% off all tokens

Submit requests asynchronously and receive 0% off all token costs. This works best for offline pipelines where latency requirements are flexible.

Monthly cost projections

Monthly volumeCost per callStandard monthlyCached monthlyYou save with caching
10,000 calls$0.1230$1,230$1,203$27
50,000 calls$0.1230$6,150$6,015$135
100,000 calls$0.1230$12,300$12,030$270
500,000 calls$0.1230$61,500$60,150$1,350
1,000,000 calls$0.1230$123,000$120,300$2,700

Kimi K3 quality benchmarks for blog writing

Benchmark data for blog writing is pending for Kimi K3. Test against your own evaluation suite before moving to production.

Benchmark data is not yet available for Kimi K3. We recommend testing against your own evaluation criteria.

Alternative models for blog writing

11 models score 80+ on blog writing benchmarks, sorted by input rate. Cheapest: Gemini 3.6 Flash (75% less, 76/100 quality).

ModelProviderInput $/MTokOutput $/MTokQualityPer callvs Kimi
Gemini 3.6 FlashGemini$0.75$3.7576/100$0.030775% cheaper
Gemini 3.7 FlashGemini$0.75$3.7582/100$0.030775% cheaper
Gemini 3.8 FlashGemini$0.75$3.7583/100$0.030775% cheaper
Gemini 3.5 FlashGemini$1.50$9.0075/100$0.073540% cheaper
Gemini 3.1 ProGemini$2.00$12.0077/100$0.098020% cheaper
Grok 4.6Grok$2.00$6.0078/100$0.050059% cheaper
Grok 4.7Grok$2.00$6.0075/100$0.050059% cheaper
GPT 5.4GPT$2.50$15.0079/100$0.1225same cost
GPT 5.6 SolGPT$4.00$20.0076/100$0.164033% more
Claude Opus 4.8Claude$5.00$25.0081/100$0.205067% more
Claude Fable 5.1Claude$10.00$50.0078/100$0.4100233% more

About Kimi K3

Provider

Moonshot (Kimi)

Tier

Flagship

Context

1M tokens

Released

Not published

Prices from platform.kimi.ai (read 2026-10-11). Cache hit: $0.30/MTok input. Kimi K3 is a 2.8T-parameter open-weight MoE model. No batch discount published yet. Not yet benchmarked, so never recommended.

Other models from Moonshot (Kimi)

ModelTierInput $/MTokOutput $/MTokContext
Kimi K2Mid-tier$0.95$4.00256K

You can compare Kimi K3 head-to-head against any other model on our model comparison pages, or track how pricing has changed over time on the pricing history tracker.

Frequently asked questions

How much does Kimi K3 cost for blog writing per API call?

A typical blog writing call using Kimi K3 costs about $0.1230 per call. This estimate uses 1,000 input tokens and 8,000 output tokens at standard rates. Standard rates are $3.00 per million input tokens and $15.00 per million output tokens.

Is Kimi K3 the best model for blog writing?

Our benchmark data does not yet include a blog writing ranking for Kimi K3. We recommend testing it against your own evaluation criteria before production usage.

What is the cheapest model for blog writing with good quality?

The most affordable model for blog writing above 80/100 quality is Gemini 3.6 Flash. It comes from Gemini at $0.75 per million input tokens. Output costs $3.75 per million tokens with a quality score of 76/100. Switching from Kimi K3 to Gemini 3.6 Flash saves about 75% per API call.

How can I reduce my Kimi K3 costs for blog writing?

Three strategies lower Kimi K3 costs for this task type effectively. Prompt caching gives a 90% discount on input tokens when reusing system prompts. The batch API gives 0% off all tokens for asynchronous processing workloads. Prompt optimization reduces token counts through more concise instructions and context windows. Combining caching with batching brings your cost from $0.1230 to about $0.0123 per call.

How does Kimi K3 pricing compare to other Moonshot (Kimi) models?

Moonshot (Kimi) has 1 other models alongside Kimi K3 today: Kimi K2 at $0.95/$4.00 per million tokens (mid-tier). The right choice depends on whether your blog writing workload prioritizes quality, cost, or speed.

What context window does Kimi K3 support?

Kimi K3 supports a context window of 1M tokens per API call. This sets the maximum combined length of your input prompt and generated response. For blog writing, typical calls use 1,000 input and 8,000 output tokens. That is well within this limit, leaving room for longer prompts or multi-turn conversations.

Track what you spend on AI

This calculator estimates costs based on published rates only. Connect your API usage to see where your money goes and which models drive your spend.