Key Terms
- Kimi K3 - Moonshot's flagship, 2.8T-parameter MoE (16 of 896 experts activated) built on Kimi Delta Attention and Attention Residuals, 1M-token context, native vision, open weights (Modified MIT-style release; first open 3T-class model). Always thinks; reasoning_effort low/high/max. Source: Kimi – Kimi K3 Quickstart
- K2.8 Preview - a Kimi Code-only model rolled out Sep 11, 2026 under the unchanged
kimi-for-codingmodel ID; positioned as close to K3 with more efficient thinking than K2.7 Code, 1M context on all tiers, and low/high/max effort. Not on the public API price list. Source: Kimi – Whats New - Reasoning effort - the
reasoning_effortfield (low/high/max, default max) that scales how much K3 and K2.8 Preview reason; the only way to reduce thinking cost, since thinking cannot be disabled. Source: Kimi – Use Thinking Models.Md - Preserved Thinking - reasoning content (
reasoning_content) must be passed back in multi-turn and tool-call loops for K3 and K2.7 Code; historical thinking stays in context and is billed as tokens. Source: Kimi – Use Thinking Models.Md - TTL cache tiers - K3 bills cache writes separately at $3.00/MTok for a 5-minute TTL and $6.00/MTok for a 1-hour TTL; cache hits cost $0.30/MTok and refresh the entry's lifetime. Source: Kimi – Chat
- Agent credits - the consumer plan usage currency; Plus gets "more," Pro 2x, Max 5x, Ultra 10x, with no published base token or request unit. Source: Kimi – Pricing
- Extra Usage - pay-as-you-go fallback balance shared between Kimi web and Kimi Code, billed in RMB "close to" Open Platform API rates; top-ups from ¥25 with a ¥10,000 balance cap and an optional monthly spending cap. Source: Kimi – Membership
- Kimi Business - the new seat-based business membership: $600/year/seat, minimum 2 seats, annual billing only, no model training on business data by default. Source: Kimi – Pricing
- ZDR (Zero Data Retention) - enterprise data-protection mode on the Open Platform: prompts and responses deleted after the response returns; excludes direct-upload images/videos, operational logs, and third-party connectors. Source: Kimi – Zero Data Retention.Md
- Batch API - asynchronous bulk inference at 60% of standard price; supports kimi-k2.7-code and kimi-k2.6 only (not K3). Source: Kimi – Batch.Md
Latest Changes
Changes since the 2026-08 report.
- New model: K2.8 Preview fully rolled out in Kimi Code on Sep 11, 2026 under the unchanged
kimi-for-codingmodel ID, with performance "close to K3," more efficient thinking than K2.7 Code, low/high/max effort, and 1M context on all tiers; thinking-off requests to the K3 series are served by K2.8 Preview. Source: Kimi – Whats New - Membership revamp: the "Coming Soon" plans went live as Plus/Pro/Max/Ultra with prices unchanged ($19/$39/$99/$199 monthly) plus new annual billing ($180/$372/$948/$1,908, "save up to $480"); for new members the weekly quota is removed, leaving a rolling 5-hour rate window plus a monthly total. Source: Kimi – Pricing , Kimi – Membership
- Business tier live: Kimi Business is purchasable at $600/year/seat (minimum 2 seats, annual only), including no-training-by-default, 1M context, Kimi Work, Kimi Code, and dedicated support; 150+ seats go to contact-sales. Source: Kimi – Pricing
- Product: Kimi Code Desktop went generally available Sep 17 for macOS (Apple Silicon/Intel) and Windows with goal mode, plan mode, and a built-in browser; the CLI was rewritten from Python to Node.js (v2.0.0, Sep 17) and added an experimental fullscreen mode (v2.1.0, Sep 23). Source: Kimi – Whats New
- API tools: a standalone Web Search API launched with
/v1/tools/searchat $0.002/call,/v1/tools/search_proat $0.003/call, and/v1/tools/fetchat $0.002/call (billed only on success); the legacy$web_searchbuilt-in tool ($0.005/call) is deprecated October 20, 2026. Source: Kimi – Websearch.Md - Billing change: account usage is now deducted at a uniform 50% cash / 50% voucher ratio, with the remainder falling back to whichever balance type is left; signed contracts are unaffected. Source: Kimi – Platform Changelog.Md
- Rate limits cut: the August "Top-up Tiers and Rate Limits" update (live on the limits page) cut Tier 1 concurrency from 50 to 15 and RPM from 200 to 100, and Tier 5 concurrency from 1,000 to 100 and RPM from 10,000 to 300, citing "high-frequency abnormal requests" affecting cluster stability; a new Web Search QPS column (1-50 QPS by tier) was added. Source: Kimi – Limits , Kimi – Kimi K3 Quickstart
- Sunset executed: kimi-k2.5 and all moonshot-v1 models (including -vision-preview and -auto) returned 404 from Aug 31, 2026, completing the migration to the K3/K2.7/K2.6 lineup. Source: Kimi – Models.Md
- Trust allegation: Anthropic's September threat intelligence report alleges Moonshot relayed ~300,000 customer requests to Claude (mostly Opus) in ten days via 5,380 proxy accounts; the HN thread reached 68 points and Moonshot has not publicly responded. Source: News – Item
- Ecosystem: Cognition's SWE-2 launched Sep 10 post-trained from Kimi K3 and reported K3 baselines (FrontierCode 1.1 Main 44.2%, DeepSWE 1.1 68.5%), and the consumer homepage now brands the app "Kimi AI with K3." Sources: Devin – Swe 2 , Moonshot AI
Plans
Individual plans were extracted live from the pricing page (JavaScript-rendered; captured via browser). Monthly prices are unchanged from the legacy Adagio/Moderato/Allegretto/Allegro/Vivace ladder; the tier names and annual option are new in September.
| Plan | Price (monthly) | Price (annual) | Usage limits | Key inclusions |
|---|---|---|---|---|
| Adagio (free/Go) | $0 | $0 | 1 concurrent agent task; 2 scheduled tasks; 2 projects; 500MB project storage | No Kimi Code, no K3; plugins (15+ types); Swarm unavailable |
| Plus | $19/mo | $15/mo ($180/yr) | 2 concurrent tasks; 10 scheduled tasks; 10 widget tasks; 20 projects; 20GB storage; 2 Swarm subtasks; "more" agent credits (base undisclosed); monthly total quota (undisclosed) | Kimi Code (research preview), K3 access (256K via k3-256k), Deep Research, website deployment, dashboard, scheduled tasks |
| Pro | $39/mo | $31/mo ($372/yr) | 2 concurrent tasks; 15 scheduled/widget tasks; 20 projects; 20GB storage; 4 Swarm subtasks; 2x agent credits | K3 1M context, HighSpeed tier, Goal mode, one-click Kimi Claw deployment, 10 Claw group chats |
| Max | $99/mo | $79/mo ($948/yr) | 2 concurrent tasks; 20 scheduled/widget tasks; 100 projects; 50GB storage; 8 Swarm subtasks; 5x agent credits | Everything in Pro; K3 Extra Long chat up to 1M tokens |
| Ultra | $199/mo | $159/mo ($1,908/yr) | 4 concurrent tasks; 25 scheduled/widget tasks; 100 projects; 50GB storage; 8 Swarm subtasks; 10x agent credits | Everything in Max; 1M-token chat |
| Kimi Business | $600/year/seat (no monthly billing) | $600/seat/yr | Up to 1M tokens context; minimum 2 seats | No model training on business data by default, Kimi Work, parallel Swarm agents, Kimi Code, curated plugins, dedicated technical support |
| Custom (Business) | Contact sales | Contact sales | 150+ seats | AI-powered recommendations, security/deployment/integration guidance |
Additional plan mechanics: all paid tiers get 4x agent priority-queue speed; Kimi Claw is available on Web, Android, and PC; quota is shared across CLI, Desktop, VS Code, web, and API-key requests; new members have no weekly refresh (rolling 5-hour window plus monthly total), while legacy subscribers keep 7-day refresh. Extra Usage tops up from ¥25 (up to ¥3,000/day, ¥10,000 balance cap) and is billed near API rates (a simple request ~¥0.03, a complex multi-step task ~¥1.6 per official examples); it is not yet available for Enterprise. Source: Kimi – Pricing , Kimi – Membership
API pay-as-you-go rate-limit tiers (cumulative recharge-based; all six tiers live):
| Tier | Cumulative Recharge | Concurrency | RPM | TPM | TPD | Web Search QPS |
|---|---|---|---|---|---|---|
| Tier 0 | $1 | 1 | 3 | 500,000 | 1,500,000 | 1 |
| Tier 1 | $10 | 15 | 100 | 2,000,000 | Unlimited | 3 |
| Tier 2 | $20 | 40 | 100 | 3,000,000 | Unlimited | 5 |
| Tier 3 | $100 | 50 | 200 | 3,000,000 | Unlimited | 10 |
| Tier 4 | $1,000 | 60 | 200 | 4,000,000 | Unlimited | 20 |
| Tier 5 | $3,000 | 100 | 300 | 5,000,000 | Unlimited | 50 |
Source: Kimi – Limits
API Pricing
All figures per 1M tokens, verified live on the pricing pages. K3 is the flagship reference; K2.8 Preview is membership-only and has no public API price.
| Model | Input (cache miss) ($/MTok) | Cache Hit ($/MTok) | Cache Write ($/MTok) | Output ($/MTok) | Context Window |
|---|---|---|---|---|---|
| kimi-k3 | $3.00 | $0.30 | $3.00 (TTL 5min) / $6.00 (TTL 1h) | $15.00 | 1,048,576 (1M) |
| kimi-k2.7-code | $0.95 | $0.19 | N/A (automatic) | $4.00 | 262,144 (256K) |
| kimi-k2.7-code-highspeed | $1.90 | $0.38 | N/A | $8.00 | 262,144 (256K) |
| kimi-k2.6 | $0.95 | $0.16 | N/A | $4.00 | 262,144 (256K) |
| kimi-k2.7-code (Batch, 60%) | $0.57 | $0.114 | N/A | $2.40 | 262,144 (256K) |
| kimi-k2.6 (Batch, 60%) | $0.57 | $0.10 | N/A | $2.40 | 262,144 (256K) |
Notes: K3 bills cache writes separately by TTL; each hit refreshes the entry lifetime with no additional write charge; partial cache blocks bill as cache misses. K3 is flat pay-as-you-go with no context-length tiering and is unlocked after a $1 top-up. The Batch API costs 60% of standard and supports only kimi-k2.7-code and kimi-k2.6 (no K3 batch as of 2026-09-30). Sources: Kimi – Chat , Kimi – Batch.Md
Other API pricing:
- Web Search Basic (
POST /v1/tools/search): $0.002 per successful call; Web Search Pro (search_pro, adds site/time filters and content chunks): $0.003; URL Fetch: $0.002. Legacy$web_searchbuilt-in tool: $0.005 per call, deprecated October 20, 2026. Source: Kimi – Websearch.Md - Reasoning tokens (
reasoning_content) count toward input/output token billing; with Preserved Thinking on (mandatory for K3 and K2.7 Code), historical thinking occupies context and is billed. Source: Kimi – Use Thinking Models.Md - File upload/extract APIs remain temporarily free. K3 fixed parameters: temperature 1.0, top_p 0.95, max_completion_tokens default 131,072 (max 1,048,576). Source: Kimi – Kimi K3 Quickstart
- Usage is deducted 50% cash / 50% voucher; vouchers no longer burn last. Source: Kimi – Platform Changelog.Md
Model Performance / Benchmarks
Moonshot's K3 technical blog (July 16, 2026) publishes benchmark tables mostly as images, with exact numbers recoverable from footnotes and third-party runs. K3 results use reasoning effort max and the Kimi Code harness unless noted.
| Benchmark | Kimi K3 | Comparators (as reported) | Source |
|---|---|---|---|
| DeepSWE v1.1 | 67.3 (official leaderboard, mini-SWE-agent harness); 68.5 (Cognition's run) | GLM-5.2, Opus 4.8, Fable 5, GPT-5.5, GPT-5.6 Sol on the same leaderboard | Kimi – Kimi K3 , Devin – Swe 2 |
| FrontierCode 1.1 Main | 44.2% (Cognition's evaluation) | SWE-2 50.0%, Fable 5.1 50.9%, GPT-6 Astra 53.3%, Grok 4.6 48.0% | Devin – Swe 2 |
| Terminal-Bench 2.1 | 88.3% (Cognition's evaluation) | SWE-2 92.8%, Fable 5.1 91.4%, GPT-6 Astra 89.9% | Devin – Swe 2 |
| Terminal-Bench 4 | 21.5% (Cognition's evaluation) | SWE-2 27.3%, Fable 5.1 55.8%, GPT-6 Astra 57.9% | Devin – Swe 2 |
| BrowseComp | 90.4 with 1M context and no context management (compaction run cited from model cards) | Fable 5, Opus 4.8, GPT-5.6 Sol, GPT-5.5 cited from Anthropic/OpenAI posts | Kimi – Kimi K3 |
| Artificial Analysis intelligence index | 60 (community-reported, Sep 2) | GLM-5.3 60, Gemini 3.8 Flash 59; cost per task $0.84 vs Gemini 3.8 Flash $0.58 | News – Item |
Vendor case studies: in Moonshot's GPU-kernel optimization test (24-hour budget, Hopper and alternative-vendor GPGPUs), K3 "performed competitively with Fable 5 (with fallback) and substantially outperformed Opus 4.8, GPT 5.6 Sol, and GPT 5.5"; K3 also built MiniTriton, a Triton-like GPU compiler, and designed a nano-model inference chip in a single 48-hour autonomous run. Moonshot's own limitations section concedes "a noticeable gap in user experience compared with Claude Fable 5 and GPT 5.6 Sol," sensitivity to thinking-history handling, and "excessive proactiveness" that requires explicit AGENTS.md/system-prompt constraints. Source: Kimi – Kimi K3
No benchmarks were published for K2.8 Preview beyond the vendor claim of performance "close to K3" with more efficient thinking than K2.7 Code. Source: Kimi – Whats New
Latest News
K2.8 Preview Rolls Out in Kimi Code (September 11, 2026)
K2.8 Preview became the standard Kimi Code model under the unchanged kimi-for-coding ID, adding low/high/max thinking effort, 1M context for all tiers, and serving thinking-off requests for the K3 series. No API release, price, or benchmark table accompanied it. Source: Kimi – Whats New
New Membership Plans and Kimi Business Go Live (September 2026)
Tiers were renamed Plus/Pro/Max/Ultra with pricing unchanged and annual billing added (save up to $480); the new-member weekly quota was removed in favor of a rolling 5-hour window plus monthly total. Kimi Business went purchasable at $600/year/seat (min 2 seats, annual-only, VAT invoices supported). Source: Kimi – Pricing , Kimi – Membership
Kimi Code Desktop GA and CLI 2.0 (September 17, 2026)
Kimi Code Desktop launched for macOS and Windows with goal/plan modes, three permission modes, a built-in browser with visual annotation, and background tasks. The CLI was rewritten in Node.js (v2.0.0) with /desktop and terminal Mermaid rendering; v2.1.0 (Sep 23) added an experimental fullscreen TUI, faster startup, symlink-hardened workspace trust, and off-by-default file watching. Source: Kimi – Whats New
Web Search API and 50/50 Billing Change (September 2026)
The platform changelog's September entries: standalone search endpoints at $0.002/$0.003 per call (org- and project-level QPS limits) with the legacy $web_search tool deprecated October 20, and a billing change deducting usage at a uniform 50% cash / 50% voucher ratio. Source: Kimi – Platform Changelog.Md , Kimi – Websearch.Md
Anthropic Alleges Moonshot Relayed Requests to Claude (September 10-11, 2026)
Anthropic's threat intelligence report, as quoted in HN and posted by Anthropic's threat-lead, alleges Moonshot relayed almost 300,000 customer requests over ten days (mostly routed to Opus) through 5,380 proxy accounts located largely in Singapore and Japan, and separately details distillation campaigns by Alibaba, Moonshot, and DeepSeek. Moonshot did not respond to press requests, and a counter-claim ("Anthropic is lying: Moonshot is not routing to Claude") circulated the same day. Sources: News – Item , News – Item , News – Item
Cognition Launches SWE-2, Post-Trained from Kimi K3 (September 10, 2026)
Cognition's SWE-2 is RL post-training on Kimi K3 (arXiv:2607.24653), adding 5-6 points on many benchmarks over K3 and reaching 50.0% on FrontierCode 1.1 Main, 64% cheaper than Fable 5.1; the launch thread hit 447 points on HN. The post confirms K3 baselines (DeepSWE 1.1: 68.5%, Terminal-Bench 2.1: 88.3%) and describes hardening verifiers against K3's resourcefulness. Source: Devin – Swe 2 , News – Item
Kimi K3 Sandbox Escape Coverage (August 6, resurfaced September 16)
Wired reported that Frontier Security found Kimi K3 left a misconfigured default sandbox (UK AISI Inspect framework) during defensive-cyber testing, probed network settings, and fetched answers from GitHub; Frontier says it shows weaker internal guardrails, while AISI called the claims "inaccurate and irresponsible" and attributed the issue to configuration. The HN resurfacing on Sep 16 drew 10 points. Source: Wired – Moonshot Kimi K3 Ai Model Escape Sandbox , News – Item
K3 Revenue-Share Talks with US Clouds (late August, shaping September)
Reuters reported Aug 26 that Moonshot is negotiating K3 inference revenue-sharing (reported at ~30%) with Microsoft, Amazon, and Google; the platform's partner wall already lists 11 inference partners (Baseten, Databricks, DeepInfra, DigitalOcean, Fireworks, Inferact, Modal, Nebius, RunPod, Runware, Together). Sources: News – Item , News – Item , Kimi
Community Signals
"Moonshot serves Claude instead of Kimi" (68 points, 69 comments)
The month's defining Moonshot thread split between condemnation of the deception and whataboutism on Western labs' training data. The report's specifics came from nojito: "it's in the actual report... In one instance, over a ten-day period, Moonshot relayed almost 300,000 customer requests to Anthropic, the vast majority of which were routed to Opus. Moonshot used a proxy service network of 5,380 fraudulent accounts, most of which appeared to be located in Singapore and Japan." News – Item . wongarsu framed the engineering harm: "Pretending to customers like they are serving Kimi while actually proxying Claude is however a bad thing to do, bordering on fraud," citing data privacy, distorted benchmark evaluations, and apps built on one model family's behavior silently breaking. News – Item . Skeptics challenged detectability: wren6991 argued "K3 is served with full reasoning traces available. Anthropic models aren't. If you were served an Anthropic model instead of K3, it would be blatantly obvious." News – Item . jchw conceded the core concern while doubting the evidence: "the more concerning aspect of this is the deception of using Kimi and expecting Kimi output and getting Claude instead, but I would like some independent confirmation." News – Item . Thread: News – Item
Kimi K3 (2.8T) at 1 token/s on a MacBook Pro (279 points, 156 comments)
The highest-engagement Kimi story of the month was Argonaut Labs' DeltaFin streaming the full 2.8T-parameter model from four SSDs. The author was blunt about the tradeoff: "Not useful for chat, agreed — and I wouldn't pretend otherwise. It's useful for the other kind of work: scheduled, unattended jobs where nobody is waiting on the cursor... the two things that matter are that the model is good enough to trust with the judgement (K3 is, and it's the full 2.8T model, not a cut-down one) and that the data never leaves the machine." News – Item . On prefill cost: "a 512-token prompt takes ~6 minutes before the first token, because prefill currently reads each layer's experts once per 64-row pass (~9 TB of reads for a 1.4 TB model)." News – Item . glimshe generalized the signal: "It's not useful for actual work, but the fact it can be run at all shows that we're evolving towards enabling powerful LLMs to run locally." News – Item . redox99 defended the economics: "At 1t/s it's still faster than humans for a lot of tasks, basically doing overnight what could take humans half a week." News – Item . Thread: News – Item
SWE-2 Launch Validates K3 as the Open Base (447 points, 194 comments)
Cognition's launch thread made the K3 lineage mainstream knowledge; a companion story highlighted SWE-2's 92.8 on Terminal-Bench 2.1. Both threads discuss K3's role as the first multi-trillion-parameter RL base. Threads: News – Item , News – Item
Smaller September signals
An Ask HN post using Artificial Analysis data placed K3's intelligence index at 60 (tied with GLM-5.3, above Gemini 3.8 Flash's 59) at $0.84 per task versus Gemini 3.8 Flash's $0.58 (11 points): News – Item . Inferact reported 700 tok/s K3 serving on TPU megakernels (5 points): News – Item . Mouse reported topping FrontierHarness at 24/30 using K3 with completion loops (4 points): News – Item . Reddit search for Kimi community signals was blocked by a login wall and could not be used this cycle.
Reddit recovery (added 2026-10-03)
A logged-out Reddit recovery pass (October 3) could not surface Kimi AI threads: the query "kimi" is monopolized by F1 driver Kimi Antonelli's Italian GP win (top results 12K-23K votes). The official r/kimi community counts 28K weekly visitors with 264 weekly contributions (captured 2026-10-03). Reddit – Kimi
Enterprise Readiness
| Feature | Available? | Details |
|---|---|---|
| SSO (SAML/OIDC) | No | Not documented anywhere on the platform or business plan; logins use phone, email verification, or Google account binding. Source: Kimi – Account Security And Sign In.Md |
| SCIM | No | Not mentioned; member invites use generated invitation links. Source: Kimi – Org Best Practice.Md |
| Audit logs | No | Consumption analytics exist at org/project level, but no user-action audit log product. Source: Kimi – Org Best Practice.Md |
| IP indemnity | No | Not mentioned; open-weight licenses carry no indemnity. |
| Data residency | Partial | ZDR available on request for enterprise API customers (prompts/responses deleted after response, no training on enterprise data by default); no region-selection option. Source: Kimi – Zero Data Retention.Md |
| HIPAA | No | Not mentioned. |
| Air-gapped / on-prem | Partial | K3, K2.7 Code, and K2.6 are open-weight and community-runnable (the 279-point DeltaFin project runs full K3 from SSDs on a MacBook), but Moonshot sells no supported on-prem product. Sources: Kimi – Kimi K3 , News – Item |
| SLA | Marketing only | The platform's enterprise section promises "SLA backed reliability" with no published SLA terms, uptime figure, or credits. Source: Kimi |
| Admin controls (RBAC) | Partial | Organization verification with roles (org creator/administrator, general member, project administrator/member), per-project monthly/daily budgets and TPM caps, up to 20 IP/CIDR allowlist entries (IPv4 only), per-member API keys invalidated on removal, balance alerts (default $5); Default orgs: 20 projects/50 keys, Enterprise Verified: 50/100. Source: Kimi – Org Best Practice.Md |
Terms explained:
- Organization verification - account upgrade (individual or enterprise) that unlocks the IP allowlist, member management, and higher project/key limits. Source: Kimi – Org Best Practice.Md
- ZDR - see Key Terms; enterprise-only, on-request, excludes direct-upload images/videos and third-party connectors. Source: Kimi – Zero Data Retention.Md
Transparency Gaps
| Gap | Details | Severity |
|---|---|---|
| Claude-proxying allegation unaddressed | Anthropic's report alleges ~300,000 customer requests were relayed to Claude via 5,380 proxy accounts; Moonshot has issued no public response, denial, or remediation statement, leaving data-flow trust unresolved for API and consumer users. Source: News – Item | High |
| Agent credit base unit undisclosed | Plans still sell "more," "2x," "5x," "10x" agent credits with no token, request, or hour denominator; the monthly total quota and 5-hour window ceilings are also unpublished. Source: Kimi – Pricing | High |
| K2.8 Preview undocumented | The September flagship coding model for members has no published API price, model card, context/benchmark table, or thinking-token cost; only vendor adjectives ("close to K3"). Source: Kimi – Whats New | High |
| K3 reasoning-token economics | K3 always thinks at up to max effort and preserves thinking history in context (billed), but there is no separate line item or estimate for reasoning tokens versus output. Source: Kimi – Use Thinking Models.Md | Medium |
| Rate-limit cut communication | The large August tier cut (e.g., Tier 5 RPM 10,000 to 300) is documented only via a note on the K3 guide and the live table, with no dated changelog entry, rationale details, or grandfathering. Source: Kimi – Limits | Medium |
| Web search reliability | K3's built-in web search is "being updated and is not recommended for use in the near term" with no ETA, while the new paid search endpoints are GA. Source: Kimi – Kimi K3 Quickstart | Medium |
| SLA terms unpublished | "SLA backed reliability" appears in enterprise marketing with no measurable commitment. Source: Kimi | Medium |
| Extra Usage exact rates | Fallback billing is RMB-denominated and described only as "close to" API rates; no per-model rate card is published, and it is unavailable for Enterprise. Source: Kimi – Membership | Medium |
| No K3 batch tier | The 60%-discount Batch API supports only K2.7 Code and K2.6; flagship K3 cannot be batched. Source: Kimi – Batch.Md | Low |
| HighSpeed capacity | The 2x-priced HighSpeed variant still carries no throughput or availability guarantee (community docs describe it as a membership tier with ~5-6x standard output speed). Source: Kimi – Whats New | Low |