Model comparison

Kimi K3.1 Pro vs Kimi K3 API price, context and cost.

Kimi K3.1 Pro (Moonshot) and Kimi K3 (Moonshot) side by side: per-1M prices, cached-input rates, context, output limits and capability flags from the live RouterPlex catalog, with three worked costs. A coding-agent session costs $2.10 on Kimi K3.1 Pro and $3.82 on Kimi K3. Both run on one prepaid key with the same OpenAI-compatible request.

Catalog rates17 November 2026
Kimi K3.1 Pro$2.00 / $10.00
Kimi K3$3.00 / $15.00
Input / output per 1M tokens

Side by side

Catalog fields, one row each.

Catalog fieldKimi K3.1 ProKimi K3
ProviderMoonshotMoonshot
Model IDkimi-k3.1-prokimi-k3
Input / 1M$2.00$3.00
Output / 1M$10.00$15.00
Cached input / 1M$0.19$0.70
Context window1M (1,048,576 tokens)1M (1,048,576 tokens)
Max output131K tokens131K tokens
Image inputYesYes
Tool callingYesYes
ReasoningYesYes
Long-prompt tierNoneNone
Price basisVendor list price, 0% markupVendor list price, 0% markup
  • Kimi K3: RouterPlex bills $3 input / $15 output per 1M tokens, Moonshot's list price. Cached prompt tokens are billed at $0.70 per 1M, not Moonshot's published $0.30 cache-hit rate: our cache price is set from what our upstream charges us for a cached token, so it does not follow the lab's rate.

What the catalog says

Kimi K3.1 Pro is 33% cheaper on input ($2.00 against $3.00 per 1M tokens). Kimi K3.1 Pro is 33% cheaper on output ($10.00 against $15.00 per 1M tokens). Kimi K3.1 Pro is 73% cheaper on cached input ($0.19 against $0.70 per 1M tokens). On the coding-agent session below, Kimi K3.1 Pro costs $2.10 against $3.82 for Kimi K3. Both accept a 1M context window.

Generated from catalog prices, limits and capability flags. Price does not measure output quality.

Worked cost examples

Same workload, both bills.

Each line multiplies the catalog rate per 1M tokens by the tokens shown. Cached tokens use the route's cached-input rate, or the full input rate when it has no cache discount. Reasoning tokens bill as output, so a model that thinks at length raises the output line beyond these figures.

Coding-agent session

40 requests of 50K prompt tokens, 80% of each prompt a cache hit, 2.5K output each.

Kimi K3.1 Pro$2.10

0.4M input x $2.00 + 1.6M cached x $0.19 + 0.1M output x $10.00 = $2.10

Kimi K3$3.82

0.4M input x $3.00 + 1.6M cached x $0.70 + 0.1M output x $15.00 = $3.82

Chat app, one month

10,000 conversations of 2K prompt tokens and 500 output tokens, no caching.

Kimi K3.1 Pro$90.00

20M input x $2.00 + 5M output x $10.00 = $90.00

Kimi K3$135

20M input x $3.00 + 5M output x $15.00 = $135

Long-document Q&A batch

200 requests of 150K prompt tokens and 2K output tokens, no caching.

Kimi K3.1 Pro$64.00

30M input x $2.00 + 0.4M output x $10.00 = $64.00

Kimi K3$96.00

30M input x $3.00 + 0.4M output x $15.00 = $96.00

Switching

One key, one line.

Both models sit behind the same RouterPlex key and the same OpenAI-compatible endpoint. Keep the request shape and change the model string. Claude Code and the Anthropic SDK use the same ids on https://api.routerplex.com.

Read the quickstart
OpenAI SDK (Python)
import os
from openai import OpenAI
 
client = OpenAI(
base_url="https://api.routerplex.com/v1",
api_key=os.environ["ROUTERPLEX_API_KEY"],
)
reply = client.chat.completions.create(
model="kimi-k3.1-pro", # switch: "kimi-k3"
messages=[{"role": "user", "content": "Hello!"}],
)
print(reply.choices[0].message.content)
curl /chat/completions
# Kimi K3.1 Pro
curl https://api.routerplex.com/v1/chat/completions \
-H "Authorization: Bearer $ROUTERPLEX_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "kimi-k3.1-pro", "messages": [{"role": "user", "content": "Hello!"}]}'
 
# Kimi K3: same request, one field changed
curl https://api.routerplex.com/v1/chat/completions \
-H "Authorization: Bearer $ROUTERPLEX_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "kimi-k3", "messages": [{"role": "user", "content": "Hello!"}]}'

Questions

Before you pick one of the two.

Answers computed from the catalog
01Is Kimi K3.1 Pro cheaper than Kimi K3?+

Kimi K3.1 Pro costs $2.00 input and $10.00 output per 1M tokens on RouterPlex; Kimi K3 costs $3.00 and $15.00. On a coding-agent session (40 requests of 50K prompt tokens, 80% of each prompt a cache hit, 2.5K output each) Kimi K3.1 Pro comes to $2.10 and Kimi K3 to $3.82, so Kimi K3.1 Pro is cheaper for that workload. A chat app month (10,000 conversations of 2K prompt tokens and 500 output tokens, no caching) costs $90.00 on Kimi K3.1 Pro and $135 on Kimi K3.

02Which has the larger context window, Kimi K3.1 Pro or Kimi K3?+

They match: both accept 1M tokens of context on RouterPlex. Maximum output is 131K for Kimi K3.1 Pro and 131K for Kimi K3.

03Do Kimi K3.1 Pro and Kimi K3 support image input and tool calling?+

Per the RouterPlex catalog, Kimi K3.1 Pro: image input, tool calling, reasoning. Kimi K3: image input, tool calling, reasoning. These flags come from the labs' published model metadata, not from a quality test.

04How do I switch from Kimi K3.1 Pro to Kimi K3?+

Change one string. Both run on the same RouterPlex key and the same OpenAI-compatible endpoint (https://api.routerplex.com/v1), so the request stays identical and only model changes from "kimi-k3.1-pro" to "kimi-k3". The same ids work on the Anthropic-compatible /v1/messages endpoint for Claude Code.

05When is Kimi K3 worth the higher price?+

Not on price, context or catalog capabilities: Kimi K3.1 Pro matches or beats it on each. The reason to pay more would be output you prefer on your own prompts; this page does not rank quality, so run both in the RouterPlex Arena before moving traffic.

Try both

Both models behind one key.

Top up from $5 with no subscription, then send the same prompt to each.