Skip to main content

Kimi Developer Guide

What is this about?

Kimi is not just a chat app. For developers, it currently spans the Kimi product surface, Kimi Code for coding agents, and the Kimi API Platform for product integration. This guide maps those surfaces, explains where each fits, and summarizes the pricing details that could be verified from official sources.

Source scope as of June 26, 2026

Based on official Kimi and Moonshot sources: kimi.com/en, www.kimi.com/code/docs/en/, and platform.kimi.ai/docs. One notable freshness detail: the public Kimi homepage still presents K2.6, while the Kimi API Platform pricing docs already publish Kimi K2.7 Code pricing. Treat the stack as fast-moving and re-check live pages before making procurement or architecture decisions.

1. The mental model​

SurfaceWhat it is forBest fit
Kimi appEnd-user workspace for research, websites, docs, sheets, slides, and agent-style task flowsKnowledge work and prompt-driven creation
Kimi CodeCoding agent experience through CLI, VS Code, and third-party coding toolsPersonal development workflows and agentic coding
Kimi API PlatformPay-as-you-go API access for models and application integrationProduct teams and production integrations

Rule of thumb:

  • Use Kimi app when the task is primarily interactive and user-facing.
  • Use Kimi Code when you want a coding agent in terminal, editor, or another agent framework.
  • Use Kimi API Platform when you are embedding Kimi in your own software.

2. What Kimi currently emphasizes​

The current official Kimi homepage positions the product around:

  • better coding,
  • smarter agents,
  • full-stack website generation,
  • agent swarm workflows,
  • turning documents into reusable skills,
  • document and office-style work across PDFs, Word, Excel, and related formats.

That makes Kimi interesting if you want one ecosystem that spans both general AI work and coding-heavy workflows.

3. Developer surfaces​

Kimi Code​

Kimi Code is the developer-facing coding layer and can be used through:

  • the Kimi Code CLI,
  • a VS Code extension,
  • third-party coding agents and frameworks via API compatibility.

Official docs describe Kimi Code as part of Kimi membership benefits, not as a separate pay-as-you-go API product.

Kimi API Platform​

The Kimi API Platform is the separate programmatic surface for product integration. This is where Moonshot publishes model pricing and API docs.

The key split is:

  • Kimi Code Platform: membership subscription, shared coding quota, rate limiting
  • Kimi API Platform: pay-as-you-go model billing

4. Interoperability details that matter​

Kimi Code exposes compatibility for existing coding-agent tooling:

ProtocolBase URLCommon endpoint example
OpenAI-compatiblehttps://api.kimi.com/coding/v1https://api.kimi.com/coding/v1/chat/completions
Anthropic-compatiblehttps://api.kimi.com/coding/https://api.kimi.com/coding/v1/messages

Other important operational details from the official Kimi Code docs:

  • the stable model ID for third-party coding tools is kimi-for-coding
  • Kimi members can create up to 5 API keys
  • CLI, VS Code, and API keys share the same account quota
  • quota refreshes every 7 days
  • there is also a rolling 5-hour rate window

The current Kimi Code overview page also states:

  • approximately 300 to 1,200 requests per 5-hour window
  • up to 30 concurrent requests
  • output speed up to 100 tokens/s

5. Pricing​

Kimi API Platform: verified current coding-model pricing​

The official Kimi API Platform currently publishes the following prices for Kimi K2.7 Code:

ModelUnitInput (cache hit)Input (cache miss)OutputContext
kimi-k2.7-code1M tokens$0.19$0.95$4.00262,144 tokens
kimi-k2.7-code-highspeed1M tokens$0.38$1.90$8.00262,144 tokens

The same page notes that:

  • prices exclude applicable taxes,
  • 1M means 1,000,000,
  • K2.7 Code supports automatic context caching, tool calls, JSON mode, and partial mode.

Kimi Code membership pricing​

The official Kimi Code docs are clear that Kimi Code is bundled into Kimi membership and billed as monthly or annual subscription, not pay-as-you-go.

What I could verify directly from official public pages on June 26, 2026:

  • there is a free plan plus paid membership tiers,
  • the pricing UI supports monthly and annual billing cycles,
  • Kimi Code usage is tied to membership quota and shared with the main Kimi membership account.

What I could not verify cleanly from the public static HTML:

  • the exact current public membership plan names,
  • the exact current public membership prices by region/currency.

So for procurement or documentation that quotes end-user subscription amounts, use the live pricing page directly:

6. Best practices​

  • Start with Kimi Code if your goal is agentic coding in a terminal or editor.
  • Use the Kimi API Platform if you are building a real product and need explicit usage-based billing.
  • Prefer the stable model ID kimi-for-coding instead of pinning to a transient backend display name.
  • Design around the fact that Kimi Code quota is shared across clients and API keys.
  • Treat the 5-hour rate window as a real operational limit for team workflows and automation bursts.
  • If you plug Kimi Code into third-party tools, keep the tool's real client identity intact; the official docs warn that tampering with the client identifier can violate the terms.

7. When Kimi is a strong choice​

Choose Kimi when you want:

  • one ecosystem that spans general AI work and coding,
  • coding-agent interoperability with OpenAI- and Anthropic-style clients,
  • a membership-backed personal coding workflow,
  • a separate pay-as-you-go API path for product integration.

It is especially attractive if you already work across both document-heavy and code-heavy tasks.