ollama - 💡(How to fix) Fix Model alias kimi-k2.6 incorrectly maps to K2.5 — both endpoints return same model in cloud models

curl -s -H "Authorization: Bearer $API_KEY" \
  -d '{"model":"kimi-k2.6","prompt":"State your exact model name and version.","stream":false}' \
  https://ollama.com/api/generate


1. Make API request to `kimi-k2.6` endpoint:
```bash
curl -s -H "Authorization: Bearer $API_KEY" \
  -d '{"model":"kimi-k2.6","prompt":"State your exact model name and version.","stream":false}' \
  https://ollama.com/api/generate


1. Make API request to `kimi-k2.6` endpoint:
```bash
curl -s -H "Authorization: Bearer $API_KEY" \
  -d '{"model":"kimi-k2.6","prompt":"State your exact model name and version.","stream":false}' \
  https://ollama.com/api/generate

2. Make API request to kimi-k2.5 endpoint:

curl -s -H "Authorization: Bearer $API_KEY" \
  -d '{"model":"kimi-k2.5","prompt":"State your exact model name and version.","stream":false}' \
  https://ollama.com/api/generate

Expected Behavior

• kimi-k2.6 should return a model identifying as Kimi K2.6
• kimi-k2.5 should return a model identifying as Kimi K2.5

Actual Behavior

| Endpoint  | Field model | Model self-identification  |
| --------- | ----------- | -------------------------- |
| kimi-k2.6 | kimi-k2.6   | "I am Kimi version K2.5" ❌ |
| kimi-k2.5 | kimi-k2.5   | "I am Kimi version K2.5" ✅ |

Both endpoints return the same underlying model (K2.5).

Evidence

Response from kimi-k2.6 endpoint:

{
  "model": "kimi-k2.6",
  "created_at": "2026-05-12T09:12:28.348524588Z",
  "response": "I am Kimi version K2.5.",
  "done": true
}

Response from kimi-k2.5 endpoint:

{
  "model": "kimi-k2.5",
  "created_at": "2026-05-12T09:17:26.000000000Z",
  "response": "I am Kimi version K2.5.",
  "done": true
}

Impact

• Users expecting Kimi K2.6 capabilities receive K2.5 instead
• Configuration confusion in multi-model setups
• Version-dependent features may not work as expected

Environment

• Client: OpenClaw 2026.5.6
• API Endpoint: https://ollama.com/api/generate
• Authentication: API Key
• Request method: HTTP POST with JSON payload
• Timestamp of tests: 2026-05-12 09:12-09:17 UTC

Suggested Fix

1. Correct the mapping: Ensure kimi-k2.6 endpoint serves the actual K2.6 model
2. Remove the alias: If K2.6 is not available, remove kimi-k2.6 from the catalog
3. Update documentation: Clarify which model versions are actually available

Additional Notes

• Both endpoints respond correctly and promptly; the issue is purely the model mapping/alias configuration.

Labels suggested: bug, model-mapping, kimi, cloud-api