Kimi K3 (low) logo
Kimi
•

Open weights model

•

Released July 2026

Kimi K3 (low) API Provider Benchmarking & Analysis

Model Comparison

Analysis of API providers for Kimi K3 (low) across performance metrics including latency (time to first token), output speed (output tokens per second), price and others. API providers benchmarked include Kimi.

Fastest

#1
KimiKimi
33.4 t/s

Output speed

Total 1 providers

Lowest Latency

#1
KimiKimi
64.56 s

Time to first answer token

Total 1 providers

Lowest Price

#1
KimiKimi
$2.31

Blended price (per 1M tokens)

Total 1 providers

Kimi K3 (low) is available through Kimi.

Highlights

Speed

Output tokens per second · Higher is better

End-to-End Response Time

Seconds · Lower is better

Price

USD per 1M tokens (blended) · Lower is better

Update: Default performance benchmarking workload has updated to 10k input tokens to better reflect production use cases. You can still select different workloads above.

Pricing

Pricing: Cache Hit, Input, and Output

Price (USD per M Tokens) · Lower is better · 10,000 input tokens

Price per token for cached prompts (previously processed), typically offering a significant discount compared to regular input price, represented as USD per million tokens. The values shown here are the cache hit price; cache write and cache storage are billed separately and vary by provider — see "Cache pricing by provider" for detail.

Pricing: Blended Price

Blended at 7:2:1 (cache-input-output) · USD per 1M tokens (blended) · Lower is better

Price per token, shown in USD per million tokens. Price is a blend of cache hit, input, and output token prices using the selected ratio (default 7:2:1 cache-input-output).

Pricing: Cache Discount

1 - (cache hit price / input price) · Higher is better

Reduction in input token cost due to cache hit relative to input price. Formula: 1 - (Cache Hit Price per Token / Input Token Price), where cache hit price is the first-party cache hit price or the median provider cache hit price. Note that this discount figure does not account for all costs associated with cache hits, such as cache write and storage costs.

Output Speed vs. Price

Blended at 7:2:1 (cache-input-output) · Output speed: output tokens per second · USD per 1M tokens (blended)
Most attractive quadrant

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Speed

Measured by Output Speed (tokens per second)

Output Speed: Kimi K3 (low)

Output speed: output tokens per second · 10,000 input tokens

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Latency vs. Output Speed

Latency: seconds to first token received · Output speed: output tokens per second · 10,000 input tokens
Most attractive quadrant

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Latency

Measured by Time (seconds) to First Token

Time to First Answer Token

Seconds to first token received · Lower is better · 10,000 input tokens

Time to first answer token received, in seconds, after API request sent. For reasoning models, this includes the 'thinking' time of the model before providing an answer. For models which do not support streaming, this represents time to receive the completion.

End-to-End Response Time

Seconds to output 500 tokens, calculated based on time to first token, 'thinking' time for reasoning models, and output speed

End-to-End Response Time

Seconds to output 500 tokens, including reasoning model 'thinking' time · Lower is better · 10,000 input tokens

Seconds to receive a 500 token response. Key components:

  • Input time: Time to receive the first response token
  • Thinking time (only for reasoning models): Time reasoning models spend outputting tokens to reason prior to providing an answer. Amount of tokens based on the average reasoning tokens across a diverse set of 60 prompts (methodology details).
  • Answer time: Time to generate 500 output tokens, based on output speed

Key Comparison Metrics & API Features

Kimi logoKimi
1.05M
Open
$0.19
33
4.71
79.52
59.85

Frequently Asked Questions

Common questions about Kimi K3 (low) providers

Kimi K3 (low) is available through 1 API provider: Kimi. Each provider offers different performance characteristics and pricing.

Kimi K3 (low) is currently available through 1 API provider that we benchmark and track.

The fastest provider for Kimi K3 (low) by output speed is Kimi (33.4 t/s). Output speed measures how quickly tokens are generated after the model starts responding.

The provider with the lowest time to first answer token for Kimi K3 (low) is Kimi (64.56s). Lower latency means faster initial response time.

The most affordable provider for Kimi K3 (low) by blended price is Kimi ($2.31 per 1M tokens). Blended price uses a 7:2:1 cache hit/input/output token ratio.

The provider with the lowest input token pricing for Kimi K3 (low) is Kimi ($3.00 per 1M input tokens).

The provider with the lowest output token pricing for Kimi K3 (low) is Kimi ($15.00 per 1M output tokens).

All 1 providers of Kimi K3 (low) support JSON mode for structured output.

All 1 providers of Kimi K3 (low) support function calling (tool use).

Kimi leads across all key metrics for Kimi K3 (low), offering the fastest speed, lowest latency, and most competitive pricing.

When choosing a provider for Kimi K3 (low), consider: output speed (for throughput-intensive tasks), latency (for interactive applications requiring quick first responses), pricing (for cost-sensitive workloads), and API features like JSON mode or function calling.

Yes, provider performance can vary over time due to infrastructure changes, load balancing, and updates. We continuously benchmark all providers and display historical performance trends in the "Over Time" charts.

For information about Kimi K3 (low)'s intelligence, capabilities, modalities, and how it compares to other models, see the model overview page. View model overview