Kimi
Try Kimi on us. Starter credit covers your first requests, then one key reaches all 4 Kimi models, with the privacy posture shown on every route.
Kimikimi
These privacy labels describe Kimi, the upstream model provider. Confidential requires all three: verified provider compute, end-to-end encryption and explicit zero data retention. Account and billing metadata are outside the content-retention claim.
| Provider | Kimi |
|---|---|
| API operator country | SG Legal home of the API operator, not an inference-location guarantee. |
| Headquarters | Not verified |
| Routing status | Active |
| Provider website | https://www.kimi.com/ |
| Models | 4 public models |
| Credits routes | 4 |
| Zero data retention | not claimed |
| Verified confidential inference | Not verified |
| Policy note | No provider-ZDR claim is tracked here. Kimi/Moonshot policy source is linked for users who need to review API retention and processing terms. Policy source |
Inference locations
Provider API declarations are also available on each model's endpoint API. Direct chat and Responses replies separate advertised availability from serving location in usage.inference_location; the actual serving region remains unknown when not reported.
usage.provider_usage.gateway_region identifies the TrustedRouter gateway, not the provider's inference location. A value such as europe-west4 does not mean the model ran in Europe. usage.inference_location.serving_region remains null when the provider has not reported it. Older gateways may return the gateway-only field as provider_usage.region.
Where the upstream GPUs execute the model, not the provider's headquarters, API ingress, or data storage. ZDR and confidential inference do not by themselves restrict geography.
- Declared countries or regions
- Not verified
No inference-location declaration has been verified for this provider. - Can locations change?
- Not verified. Do not assume that the serving location is fixed.
- Provider region pinning
- Not verified.
- Pinning through TrustedRouter
- No verified provider-specific location pin documented here.
- Infrastructure declaration
- Inference location not verified; no country-specific residency commitment.
- Evidence
- Not yet reviewed.
Provider selection alone is not a region pin. TrustedRouter's US provider filter selects company jurisdiction, not GPU location. A regional gateway hostname does not pin a downstream GPU. For a binding residency requirement, confirm the model, region, failover scope and enforced controls before sending sensitive data.
Measured performance
32 samplesContinuously sampled across Kimi's routed models: p50 TTFT, effective throughput, and success rate. Effective throughput uses provider-reported output tokens over complete request time. Unsupported route and probe-configuration rows are separated from provider downtime. No prompt or output content stored.
| p50 TTFT | 2282 ms |
|---|---|
| Effective throughput | 43 tok/s n=5 |
| Uptime | 100.00% |
| Model | p50 TTFT | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|
| moonshotai/kimi-k2.6 | 1859 ms | 43 tok/s n=2 | 100.00% | — | 10 |
| moonshotai/kimi-k2.7-code-highspeed | 2282 ms | — | 100.00% | — | 8 |
| moonshotai/kimi-k2.7-code | 2698 ms | 33 tok/s n=1 | 100.00% | — | 7 |
| moonshotai/kimi-k3 | 3761 ms | 56 tok/s n=2 | 100.00% | — | 7 |
Kimi performance history · Full provider & model leaderboard.
Models served by Kimi.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|---|---|---|---|---|
moonshotai/kimi-k2.6MoonshotAI: Kimi K2.6 |
IQ 114#58 | 262,144 | $1.00225/1M | $0.1688/1M | $4.22/1M |
moonshotai/kimi-k2.7-codeMoonshotAI: Kimi K2.7 Code |
IQ 111#73 | 262,144 | $1.00225/1M | $0.20045/1M | $4.22/1M |
moonshotai/kimi-k2.7-code-highspeedmoonshotai/Kimi: K2.7-Code-Highspeed |
— | 262,144 | $2.0045/1M | $0.4009/1M | $8.44/1M |
moonshotai/kimi-k3MoonshotAI: Kimi K3 |
IQ 127#21 | 1,048,576 | $3.165/1M | $0.3165/1M | $15.825/1M |
Questions
Does Kimi have zero data retention?
TrustedRouter does not currently mark Kimi as provider-level zero data retention. Use trustedrouter/zdr or provider.min_privacy=zdr to select a different eligible route, and review the linked policy source for changes.
Is Kimi end-to-end encrypted?
TrustedRouter does not currently mark Kimi as end-to-end encrypted at the provider boundary. The TrustedRouter gateway is still attested, but the selected provider normally receives the request in order to run the model. Use trustedrouter/e2e for the stronger route requirement.
Which Kimi models are available through TrustedRouter?
This page currently lists 4 public Kimi models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.