Kimi Open Platform

AI servicemoonshot-kimi-api

Hosted Kimi models from Moonshot AI with recharge-based rate-limit tiers.

Provider: default
Kind: AI service
Category: Compute
Official docs: https://platform.kimi.ai/docs/pricing/limits
Also known as: Kimi API, Moonshot AI

Properties · 6 set by this component

property	type	values	required	kind default	this component
auth	enum	api-key \| oauth \| iam \| none	no	—	▸ api-key
contentFiltering	boolean	—	no	—	inherited
customerManagedKeys	boolean	—	no	—	inherited
dataResidency · advanced	enum	us \| eu \| asia \| global	no	—	inherited
dataRetentionDays	integer	—	no	—	inherited
keyStore	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
maxConcurrency · component property	integer	—	no	1	inherited
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ multimodal
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	inherited
rateLimitRpm · advanced	integer	—	no	—	▸ 3
rateLimitTpm · advanced	integer	—	no	—	▸ 500000
tier · component property	enum	tier0 \| tier1 \| tier2 \| tier3 \| tier4 \| tier5	no	tier0	inherited
tokensPerDay · component property	integer	—	no	1500000	inherited
viaGateway	boolean	—	no	false	inherited

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

AI API key not managedwarning

ai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

— all of these hold:
— the node's `auth` is "api-key"
— the node's `keyStore` is false
— the node has at least one incoming edge from an app-server, worker or client
— this does not hold:
— the design contains a node of kind key-management

Stateful node without zone redundancyerror

stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

— all of these hold:
— the node's `stateless` is false
— the node sits inside exactly 1 availability-zone group
— this does not hold:
— the node sits inside at least one cell group

Use it in a design

nodes:
  - { id: "moonshot-kimi-api", component: "moonshot-kimi-api" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Kimi Open Platform (Moonshot AI): hosted Kimi model API with OpenAI-compatible chat over a public endpoint.
3# Per "Recharge and Rate Limiting", tiers follow cumulative recharge; Tier0 ($1 recharge) allows 1 concurrent
4# request, 3 RPM, 500,000 TPM and 1,500,000 tokens per day, rising with each tier up to Tier5.
5schemaVersion: "1"
6type: "component"
7id: "moonshot-kimi-api"
8kind: "ai-service"
9provider: "default"
10docs: "https://platform.kimi.ai/docs/pricing/limits"
11aliases: ["Kimi API", "Moonshot AI"]
12defaults:
13  auth: "api-key"
14  managed: true
15  modality: "multimodal"
16  publicEndpoint: true
17  rateLimitRpm: 3
18  rateLimitTpm: 500000
19properties:
20  tier:
21    type: "enum"
22    values: ["tier0", "tier1", "tier2", "tier3", "tier4", "tier5"]
23    default: "tier0"
24  maxConcurrency:
25    type: "integer"
26    default: 1
27  tokensPerDay:
28    type: "integer"
29    default: 1500000

The same page as markdown, for an agent: /catalogue/components/moonshot-kimi-api.md