Moonshot AI Model Deprecation & EOL Lifecycle Hub

Runs locally in your browser — 0 bytes uploaded Verified 2026-11-12 UTC · 21 models · 18 actionable

Monitor all 21 normalized Moonshot AI lifecycle records (3 deprecated, 15 retired, 3 active). Audit MOONSHOT_MODEL variables in the Local .env Auditor or compare replacement costs in DevToken.

Tracked Models 21
Deprecated (Upcoming) 3
Retired (Offline) 15
Active Catalog 3
Ecosystem Schedule Isolation (Moonshot AI)

Moonshot AI publishes model deprecation and retirement dates independently from third-party cloud hosters. Pin exact dated snapshots in MOONSHOT_MODEL or moonshot/ LiteLLM routes and validate upgrades against this isolated Moonshot AI catalog.

1. Interactive Moonshot AI Lifecycle Schedule (21)

Filter by 3-state lifecycle status
21 of 21 models shown
Moonshot AI deprecated, retired, and active LLM API lifecycle catalog
Model ID Provider Calculated Status Confirmed Shutdown (UTC) Vendor Lifecycle Replacement & Migration Source
kimi-k2.6 Moonshot AI DEPRECATED Not announced DeprecatedDep: 2026-11-01 Docs ↗
kimi-k2.7-code Moonshot AI DEPRECATED Not announced DeprecatedDep: 2026-11-01
kimi-k3.1-pro Cost → Audit →
Docs ↗
kimi-k2.7-code-highspeed Moonshot AI DEPRECATED Not announced DeprecatedDep: 2026-11-01
kimi-k3.1-pro-highspeed Cost → Audit →
Docs ↗
kimi-k2-0711-preview Moonshot AI RETIRED Not announced Retired Docs ↗
kimi-k2-0905-preview Moonshot AI RETIRED Not announced Retired Docs ↗
kimi-k2-thinking Moonshot AI RETIRED Not announced Retired
kimi-k3.1-pro Cost → Audit →
Docs ↗
kimi-k2-thinking-turbo Moonshot AI RETIRED Not announced Retired
kimi-k3.1-pro-highspeed Cost → Audit →
Docs ↗
kimi-k2-turbo-preview Moonshot AI RETIRED Not announced Retired
kimi-k3.1-pro-highspeed Cost → Audit →
Docs ↗
kimi-k2.5 Moonshot AI RETIRED Not announced Retired Docs ↗
kimi-latest Moonshot AI RETIRED Not announced Retired Docs ↗
kimi-thinking-preview Moonshot AI RETIRED Not announced Retired
kimi-k3.1-pro Cost → Audit →
Docs ↗
moonshot-v1-128k Moonshot AI RETIRED Not announced Retired
kimi-k3.1-pro Cost → Audit →
Docs ↗
moonshot-v1-128k-vision-preview Moonshot AI RETIRED Not announced Retired
kimi-k3.1-pro Cost → Audit →
Docs ↗
moonshot-v1-32k Moonshot AI RETIRED Not announced Retired Docs ↗
moonshot-v1-32k-vision-preview Moonshot AI RETIRED Not announced Retired
kimi-k3.1-pro Cost → Audit →
Docs ↗
moonshot-v1-8k Moonshot AI RETIRED Not announced Retired Docs ↗
moonshot-v1-8k-vision-preview Moonshot AI RETIRED Not announced Retired
kimi-k3.1-pro Cost → Audit →
Docs ↗
moonshot-v1-auto Moonshot AI RETIRED Not announced Retired Docs ↗
kimi-k3 Moonshot AI ACTIVE No EOL Active — —
kimi-k3.1-pro Moonshot AI ACTIVE No EOL Active — —
kimi-k3.1-pro-highspeed Moonshot AI ACTIVE No EOL Active — —

2. Canonical Moonshot AI Migration Guides (2)

Open family-level migration guides covering Moonshot AI model identifiers alongside sibling cloud platforms, complete with interactive .env replacement diffs.

3. Moonshot AI Keyless CI Deprecation Gate & Feeds

Feeds & CI

Run this zero-key curl + jq check in CI pipelines to block deprecated or retired Moonshot AI model IDs against GET /api/v1/eol.json, or subscribe via RSS, Atom, and iCal.

curl -fsSL https://eol.codeap.com/api/v1/eol.json | jq -e \
  --arg prov "moonshot" \
  --arg models "kimi-k2.6,kimi-k2.7-code" '
    ($models | split(",") | map(ascii_downcase)) as $targets
    | [.models[]
       | select(.providerKey == $prov)
       | select((.modelId | ascii_downcase) as $id | $targets | index($id))
       | select(.status == "deprecated" or .status == "retired")]
    | if length > 0 then
        (map("BLOCKED: \(.provider) \(.modelId) [\(.status | ascii_upcase)] EOL=\(.eolDate // "n/a") -> \(.replacementModel // "none")") | .[] | stderr), halt_error(1)
      else "PASS: zero deprecated/retired " + $prov + " models." end
  '

4. Moonshot AI Deprecation & Migration FAQ

How many Moonshot AI models are currently deprecated or retired in LLMEOL?

LLMEOL currently tracks 21 Moonshot AI model entries: 3 deprecated models with upcoming shutdowns, 15 retired models that have passed their UTC EOL date, and 3 active models with no announced shutdown date.

How should engineering teams audit Moonshot AI model IDs in .env and LiteLLM files?

Set MOONSHOT_MODEL in .env files or use the moonshot/ prefix in LiteLLM router configs, then paste your snippet into the Local Model Config Auditor to flag retired and deprecated Moonshot AI snapshots with zero network upload.

Can CI pipelines block deprecated Moonshot AI models automatically without an API key?

Yes. Query https://eol.codeap.com/api/v1/eol.json with curl and jq filtered by providerKey to fail pull requests whenever a configured Moonshot AI model enters DEPRECATED or RETIRED state.