How to Run Kimi K2.5 via API in 2026 (Hosts Compared)

You can run Kimi K2.5 through any OpenAI-compatible API by changing two lines: the base URL and the API key. Moonshot AI's reference pricing is about $0.60 per million input tokens and $3.00 per million output tokens (as of 2026-08-20). This guide compares every host serving K2.5 and shows the exact code.

Key takeaways

• Kimi K2.5's reference API pricing is roughly $0.60 per million input tokens and $3.00 per million output tokens (as of 2026-08-20), or about $12 for a workload of 10M input plus 2M output tokens.
• K2.5 is served by first-party and third-party hosts: inference clouds, an aggregator, and a decentralized inference marketplace, nearly all behind OpenAI-compatible endpoints.
• Switching hosts is a two-line change (base_url + api_key); the model ID is the only other thing that sometimes differs.
• Hosted K2.5 typically costs a fraction of frontier-API rates such as GPT-5.2's; verify current numbers on each provider's pricing page before committing.
• List prices move frequently. Each provider's pricing page is the source of truth, and DeAI's cheapest LLM API roundup tracks them in one place.

What is Kimi K2.5?

Kimi K2.5 is Moonshot AI's open-weight entry in the Kimi K2 line. Because the weights are published through Moonshot AI's Hugging Face organization, you are not locked to one vendor: Moonshot runs a first-party API, and multiple independent hosts serve the same weights over their own infrastructure. Moonshot positions the K2 family at chat, coding, and agentic tool-use workloads; for architecture details and exact license terms, the model card is the authoritative source.

That open distribution is what makes host-shopping worthwhile. It's also why "the Kimi K2.5 API" is really several APIs with different prices, rate limits, and data terms. If you're evaluating the newer generation, our guide to running Kimi K3 via API covers the same ground for K3.

How much does the Kimi K2.5 API cost?

Moonshot AI's reference pricing for K2.5 is roughly $0.60 per million input tokens and $3.00 per million output tokens (as of 2026-08-20). A worked example: a workload of 10M input tokens and 2M output tokens costs about (10 × $0.60) + (2 × $3.00) = $12 at reference rates.

Third-party hosts set their own rates, and the billing models differ:

• Serverless hosts bill per token, usually with separate input and output rates.
• Dedicated deployments bill per GPU-hour, which can make sense at sustained volume.
• Aggregators pass through upstream pricing, sometimes with a fee on top.
• Marketplaces let rates float with provider supply.

We only republish figures we can verify against a canonical source. As of 2026-08-20, the reference rate above is the confirmed number, and third-party list prices for K2.5 move often enough that the pricing pages linked below are the reliable place to check. Also look past the headline per-token figure: prompt caching, batch discounts, and context-tier pricing can change your effective rate materially.

Which hosts serve Kimi K2.5?

The table below lists the main places to get a K2.5 endpoint as of 2026-08-20. Availability changes, so confirm on each provider's model list before you build.

A few notes on reading the table:

• "Reference" pricing is Moonshot's first-party rate. Third parties price independently of it, in either direction.
• OpenRouter is one API key over multiple upstream providers; its K2.5 model page shows which upstreams are live and what each charges per token.
• Morpheus is structured differently from the rest: it is a decentralized inference marketplace where independent providers bid to serve requests, so per-token rates and data-handling terms are set per provider rather than by a single company.
• Throughput and uptime figures on provider sites are self-reported claims; treat them as such until you can measure latency on your own prompts.

How do you call the Kimi K2.5 API?

Almost every K2.5 host exposes an OpenAI-compatible chat-completions endpoint. If your code already talks to an OpenAI-style API, you're changing configuration, not code.

1. Get an API key

Sign up with your chosen host, create a key in its dashboard, and note two things: the base URL and the exact model ID for K2.5. Model IDs are not standardized across hosts: one may use a short name, another a namespaced ID. Copy it from the host's docs rather than guessing.

2. Call it with the OpenAI Python SDK

The OpenAI Python SDK works against any compatible endpoint:

from openai import OpenAI

client = OpenAI(
    base_url="https://YOUR-HOST-ENDPOINT/v1",  # the host's OpenAI-compatible URL
    api_key="YOUR_API_KEY",                     # from the host's dashboard
)

response = client.chat.completions.create(
    model="kimi-k2.5",  # exact model ID varies by host — check its docs
    messages=[
        {"role": "system", "content": "You are a concise assistant."},
        {"role": "user", "content": "Explain mixture-of-experts routing in one paragraph."},
    ],
    temperature=0.6,
    max_tokens=512,
)

print(response.choices[0].message.content)

3. Or use curl

curl -X POST "https://YOUR-HOST-ENDPOINT/v1/chat/completions" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "kimi-k2.5",
    "messages": [
      {"role": "system", "content": "You are a concise assistant."},
      {"role": "user", "content": "Explain mixture-of-experts routing in one paragraph."}
    ],
    "temperature": 0.6,
    "max_tokens": 512
  }'

4. Switch hosts by changing two lines

Because the API shape is identical across hosts, a multi-host setup is just configuration:

import os
from openai import OpenAI

HOSTS = {
    "host_a": {"base_url": "https://host-a.example/v1", "model": "kimi-k2.5"},
    "host_b": {"base_url": "https://host-b.example/v1", "model": "moonshotai/kimi-k2.5"},
}

cfg = HOSTS["host_a"]  # swap to "host_b" to fail over
client = OpenAI(base_url=cfg["base_url"], api_key=os.environ["HOST_API_KEY"])

This is the practical answer to price movement: keep a second host's key in your environment and you can fail over, or A/B cost and latency, without touching application code.

Kimi K2.5 vs GPT-5.2: what's the cost difference?

GPT-5.2 is OpenAI's frontier line, sold through OpenAI's first-party API; OpenAI publishes current per-token rates on its pricing page. K2.5 is open-weight and sold by many competing hosts. As a rule, hosted open-weight models land at a fraction of frontier-API per-token pricing, and K2.5's reference rate ($0.60/M input, $3.00/M output as of 2026-08-20) is consistent with that pattern.

The honest way to compare: take a representative week of your traffic (input tokens, output tokens, cache hit rate) and price it on both. Output tokens dominate most chat and agent workloads, so the output rate matters more than the input rate. Then weigh the non-price differences: K2.5 gives you multiple vendors and a self-host fallback; GPT-5.2 gives you a single first-party endpoint. On quality, don't treat anyone's benchmark table as final, including a provider's own. Run both models on a few hundred of your real prompts and score the outputs yourself.

What should you check before picking a K2.5 host?

• Exact model served. Confirm the endpoint serves K2.5, not the older K2, and note the precise model ID.
• Context and output limits actually enabled. These vary between providers serving the same weights.
• Data retention. Zero-retention and "we don't train on your data" promises are policy statements, not independently verified facts. Read each provider's terms; on aggregators and marketplaces, establish which underlying operator actually processes your request.
• Rate limits and throughput. Provider-published tokens-per-second figures are self-reported claims.
• Feature parity. Tool calling, structured outputs/JSON mode, and streaming behave differently across hosts, so test the specific features your app uses.
• Billing model. Per-token serverless versus per-hour dedicated; sustained high volume can flip which is cheaper.
• Exit cost. Prefer hosts with OpenAI-compatible endpoints (everything in the table above qualifies) so switching stays a two-line change.

FAQ

How much does the Kimi K2.5 API cost?

Moonshot AI's reference pricing is roughly $0.60 per million input tokens and $3.00 per million output tokens (as of 2026-08-20). Third-party hosts set their own rates, so confirm each provider's pricing page before committing.

Is Kimi K2.5 cheaper than GPT-5.2?

At its reference rates ($0.60/M input, $3.00/M output as of 2026-08-20), hosted K2.5 typically costs a fraction of frontier-API pricing. Check OpenAI's pricing page for current GPT-5.2 rates, and compare both on your real token mix.

Is the Kimi K2.5 API OpenAI-compatible?

Yes. Moonshot's API and most third-party hosts expose OpenAI-compatible chat-completions endpoints, so switching is usually a base-URL and API-key change. Exact model IDs vary by host, so copy the ID from your provider's docs.

Can I self-host Kimi K2.5 instead of using an API?

Yes. K2.5 is an open-weight release with weights distributed via Moonshot AI's Hugging Face organization. Self-hosting demands serious multi-GPU capacity; the model card lists hardware requirements and license terms.