Ethical Stack.

Moonshot API

Developer API platform for calling Kimi models through chat-completions, responses, or messages interfaces.

Score calculation

(3 + 4 + 2 + 1 + 7) ÷ 5 = 3.4

5 of six dimensions rated. Unrated dimensions are excluded from the average.

Full scoring method ↗
Setup details

Moonshot API service and selected model endpoint; no inference-region or model-specific training data assumptions.

What fits your needs

Direct Moonshot API access; pricing and available model IDs can change. Check endpoint, API terms, region and current model list.

API access

The platform documents chat completions, Responses API, Messages API, and SDK-compatible access.

See the evidence
Tradeoffs to expect

Model and route

API access does not make the model weights or serving stack open; each request uses a selected Moonshot endpoint.

See the evidence
How to switch

Try the endpoint

Create a key, choose a model ID, and configure the documented base URL and SDK.

See the evidence
Practical questions

Usage costs

Review current model pricing and any account-specific terms before production use.

See the evidence

Pricing and retention

The platform lists pay-as-you-go token prices; OpenPlatform policy describes Singapore storage and account-linked retention but no exact request deletion window.

See the evidence

Energy practices

3/10↑

For the Moonshot API chat-completions endpoint boundary, public documentation establishes the service or route but not its request-level physical footprint. The API documents model selection and a maximum completion-token parameter; these cap/configure requested output, but no measured physical savings are reported. Electricity sourcing is not mapped to this route.

See the evidence

This practices/transparency assessment covers the Moonshot API chat-completions endpoint boundary. The sources establish how the service or endpoint is exposed and provide the request controls described in the demand component; they do not give a measured per-request energy, emissions or water value. The disclosure point reflects the stated operating boundary, not a product footprint, and company-wide electricity reporting is not attributed to this route.

1 + 1 reporting + 0 electricity + 1 controls = 3/10. This grades documented practices and transparency.

The reviewed sources don’t confirm request-level electricity, emissions or water; the actual serving facility and its power mix are also not mapped to Moonshot API chat-completions endpoint.

Reporting1/3
The reviewed documentation defines the Moonshot API chat-completions endpoint boundary. It gives an operating-scope description, not a dated quantitative energy, carbon or water report for this route.
Electricity sourcing0/3
No reviewed source maps Moonshot API chat-completions endpoint to a disclosed electricity mix or time-and-location-matched clean-power supply. The route's actual electricity use and emissions therefore remain unestablished.
Resource controls1/3
The API documents model selection and a maximum completion-token parameter; these cap/configure requested output, but no measured physical savings are reported.

Water disclosure

Water reporting has not been assessed for this choice.

Training data

—Depends on the model↑

The API is model-selectable. Prompt-use terms and training-data rights are distinct; use the model/version and any third-party route selected by the customer.

See the evidence

User prompts, model-improvement settings, and the original training data are different evidence questions. The reviewed product documentation does not identify a fixed model version and complete training-data rights record for Moonshot API service and selected model endpoint; no inference-region or model-specific training data assumptions., so this assessment remains unscored.

Exact model selection, release version, source inventory, permissions, post-training data, and creator-remedy scope remain unresolved.

Your data & privacy

4/10↑

OpenPlatform policy covers API service content, permits use to improve the service, describes Singapore storage, and retains account/input information while the account is active; it does not give a precise API request-retention period.

See the evidence

The API is a separate business/developer service governed by OpenPlatform terms and privacy policy. Those sources say content may be used to develop or improve the service, describe Singapore storage, and state account/input data is retained while the account is active; no precise endpoint-specific deletion window is specified.

Service-improvement use and active-account retention are disclosed, and Singapore storage is described, but the exact API endpoint and deletion timing remain unclear.

Current model-specific data controls, API logging, retention windows, region selection, and account opt-in settings remain uncertain.

Openness

2/10↑

This is a hosted service with a public interface but no documented self-hostable product runtime or weights in the reviewed sources.

See the evidence

The service provides a hosted product or API interface, while the reviewed product material does not expose the serving implementation and current model weights for independent deployment. This rates this service scope, not separately released model weights.

The score reflects service-level inspectability and control, not usefulness or model quality.

SDKs, APIs, or model families may have separate licenses and do not make this service itself self-hostable.

Worker protections

1/10↑

Moonshot’s reviewed Kimi terms, company site and model pages do not disclose workforce conditions, labor grievance mechanisms or supplier audit outcomes.

See the evidence

The sources reviewed provide product, terms, or corporate information but no qualifying disclosure about conditions for data annotators, evaluators, moderators, or infrastructure workers. This is a disclosure gap within the checked materials, not evidence that workers are mistreated or that no labor policy exists. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

1 + 0 pay & conditions + 0 worker voice & remedy + 0 evidence & follow-through = 1/10. This grades documented worker safeguards, not a measured rate of mistreatment.

Worker counts, locations, pay, labor protections, worker voice mechanisms, supplier coverage, and independent audit or remediation outcomes were not established in the sources reviewed.

Pay & conditions0/3
Reviewed sources provide no qualifying disclosure of worker conditions; this zero is limited to the checked material and is not an exhaustive claim.
Worker voice & remedy0/3
No qualifying worker-voice mechanism or documented worker grievance outcomes were disclosed in the reviewed material.
Evidence & follow-through0/3
No independent labor audit results, worker-level corroboration, or remediation outcomes were disclosed in the reviewed material.
Workers rubric ↗

Military ties

7/10Not established↑

No Moonshot defense contract or military deployment is identified in the reviewed company and model sources.

See the evidence

Moonshot’s reviewed Kimi terms, company disclosures and model repository do not name a defense customer, contract or deployment. Third-party availability of its models doesn’t show Moonshot’s own military relationship; the public material reviewed does not supply a customer-complete accounting. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

7 base + 0 safeguard adjustment = 7/10 (0 of 9 safeguard points; every 3 adds 1). No military relationship was established in the cited sources. This ranks above known defense ties without claiming a verified clean record.

Complete contract texts, undisclosed customers, end-use restrictions, actual workload deployment, and independent compliance or outcome reports are unavailable in the reviewed public material.

Use restrictions0/4
The reviewed terms or policy material contains no qualifying military-use restriction beyond general lawfulness/export compliance; this zero is limited to the reviewed source set.
Enforcement & oversight0/3
No military-specific review, enforcement, or remedy mechanism was disclosed in the sources reviewed.
Relationship disclosure0/2
No military-specific relationship or military-specific transparency policy was disclosed in the materials reviewed; this is a scoped disclosure finding.

The reviewed Kimi platform terms and Moonshot model materials do not identify a defense contract or military deployment. Model availability through third parties or permissive downstream deployment doesn’t confirm Moonshot’s own government or military customer relationship.

Military rubric ↗

BDS targets

Not listed↑

We did not find Moonshot AI among the named targets in the two official BNC campaign lists. This is a limited list check, not BDS approval.

See the evidence

Moonshot AI is not a named target in the checked lists, but BDS uses selective campaigns, so absence cannot establish a clean record. Running downloaded weights locally is a different decision from paying the developer or a cloud host; check the host as well. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

This review covers the named targets in the BNC consumer/pressure guide and No Tech campaign, not every BDS campaign, local group, investment or supplier. Lists and ownership can change. A company’s absence from these lists is not an endorsement or proof that it has no relevant relationships.

More from Moonshot AI

All sources

Side by side