Kimi products, prices and documentation change quickly. Kimi AI Guide links important claims to their sources, records verification dates and invites readers to report errors with evidence.
To suggest a correction, email [email protected].
Sources we prefer
We begin with first-party evidence:
- Kimi API documentation and changelog;
- official Kimi and Moonshot AI product pages;
- official Kimi Help Center articles;
- official model reports, repositories and release announcements;
- current account or product interfaces; and
- our own reproducible tests.
Independent research can add context, but it does not replace an available primary source for a current price, model identifier or product rule.
What a source citation means
A citation shows where a claim came from. It does not automatically prove that:
- the feature is enabled for every account or region;
- the source is internally consistent with every other Kimi page;
- a marketing claim has been independently reproduced; or
- the information will remain current after the verification date.
We state “Kimi says” or “official documentation lists” when the evidence is vendor-published. We reserve “we observed” and “we measured” for completed work documented under our Testing Methodology.
How we handle conflicting official sources
When Kimi pages disagree, we use the following order:
- the most specific current documentation for the product and action;
- the current live product or billing interface, when safely verifiable;
- a current official help article;
- a general product or marketing page; and
- an older announcement or search result.
We also consider the page date, language, region and whether a table is loaded dynamically. If the conflict remains unresolved, we publish both figures with an explanation instead of hiding the disagreement.
Current example: Kimi web-search API fee
Checked August 5, 2026:
- the Open Platform WebSearch guide lists $0.005 per triggered call; while
- Kimi’s current API pricing Help Center article lists $0.004 per invocation.
Neither page resolves the other, and we have no paid billing observation that establishes which figure applies to this account and endpoint. Our pricing page and calculator therefore retain both figures and show a $0.004-$0.005 scenario range instead of silently choosing one. A single rate should be restored only when the official pages agree or a dated live billing record resolves the conflict.
Current example: Kimi Business price
Checked August 4, 2026:
- the English Kimi Business Help Center table lists $600 per seat per year, a five-seat minimum and a $3,000 minimum annual purchase; while
- the Kimi Business marketing page has been rendered or indexed with $599 per seat per year and a $2,995 minimum, and its visible price block has not appeared consistently across page renderings.
Our pricing hub uses the current English Help Center table because it is the more specific purchase reference. Readers should still confirm the live checkout total before paying.
How to submit a useful correction
Email [email protected] with:
- the Kimi AI Guide page URL;
- the exact sentence, table row or image you believe is wrong;
- the corrected information;
- a direct source URL or original evidence;
- the date you viewed or captured it; and
- any relevant account type, plan, language or region.
Do not send passwords, API keys, complete payment records, government identification or unnecessary personal data. Redact private information from screenshots.
What happens after a report
We review the affected page and the supplied evidence, then check the strongest available primary source. A report can lead to:
- a factual correction;
- a clarification or stronger limitation;
- an updated source or verification date;
- a new live test; or
- no change when the published text is supported by stronger evidence.
We may reply to request context, but submission does not guarantee publication or a personal response.
Material and minor corrections
A material correction changes a reader’s understanding or decision—for example, a wrong price, model capability, plan requirement, API parameter or test result. We update the page and add a correction note describing the change.
A minor correction fixes spelling, grammar, formatting or a broken link without changing the meaning. These fixes may be made without a public correction note.
Page dates
Where relevant, pages distinguish:
- Published: when the page first became public;
- Updated: when substantive content changed; and
- Verified: when high-change claims or a live test were last checked.
Updating an existing page should preserve its URL, original publication date, category and featured image unless a separate editorial decision requires a change.
Source suggestions
We also welcome official releases, documentation changes, reproducible test fixtures and archived evidence that can strengthen an existing page. Send them to [email protected] with a short explanation of why they matter.
For broader standards, read our Editorial Policy. For general enquiries, use the Contact page.