litellm - 💡(How to fix) Fix AI21 model list outdated — only jamba-large-1.7 and jamba-mini-2 remain [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#27094Fetched 2026-05-04 04:59:07
View on GitHub
Comments
1
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
commented ×1

The AI21 model list in LiteLLM is outdated. AI21 has retired all J2 models (j2-light, j2-mid, j2-ultra) and now only offers two models:

  • jamba-large-1.7-2025-07 (alias: jamba-large-1.7)
  • jamba-mini-2-2026-01 (alias: jamba-mini-2)

Confirmed via the AI21 API:

curl -s https://api.ai21.com/studio/v1/models \
  -H "Authorization: Bearer $KEY" | python3 -m json.tool

Returns only those two models. Requests to j2-ultra etc. return "The provided model is not supported".

Root Cause

The AI21 model list in LiteLLM is outdated. AI21 has retired all J2 models (j2-light, j2-mid, j2-ultra) and now only offers two models:

  • jamba-large-1.7-2025-07 (alias: jamba-large-1.7)
  • jamba-mini-2-2026-01 (alias: jamba-mini-2)

Confirmed via the AI21 API:

curl -s https://api.ai21.com/studio/v1/models \
  -H "Authorization: Bearer $KEY" | python3 -m json.tool

Returns only those two models. Requests to j2-ultra etc. return "The provided model is not supported".

Code Example

curl -s https://api.ai21.com/studio/v1/models \
  -H "Authorization: Bearer $KEY" | python3 -m json.tool
RAW_BUFFERClick to expand / collapse

Summary

The AI21 model list in LiteLLM is outdated. AI21 has retired all J2 models (j2-light, j2-mid, j2-ultra) and now only offers two models:

  • jamba-large-1.7-2025-07 (alias: jamba-large-1.7)
  • jamba-mini-2-2026-01 (alias: jamba-mini-2)

Confirmed via the AI21 API:

curl -s https://api.ai21.com/studio/v1/models \
  -H "Authorization: Bearer $KEY" | python3 -m json.tool

Returns only those two models. Requests to j2-ultra etc. return "The provided model is not supported".

Additional issue

When adding AI21 models via the LiteLLM Admin UI, selecting an existing AI21 credential (that works for one model) does not seem to apply correctly to a second model added afterwards. The second model ends up with a wrong API key, even though the same credential was selected. After a proxy restart, the first model works fine but the second one fails with AuthenticationError. This might be a UI/credential-binding bug.

Suggested fix

  1. Update the AI21 model list to reflect the current two available models
  2. Remove the deprecated J2 models from the default model definitions
  3. Investigate credential binding when reusing existing AI21 credentials for multiple models in the Admin UI

extent analysis

TL;DR

Update the AI21 model list to reflect the current available models and investigate credential binding issues in the Admin UI.

Guidance

  • Verify the available AI21 models using the provided curl command to ensure the list is up-to-date.
  • Remove deprecated J2 models (j2-light, j2-mid, j2-ultra) from the default model definitions to prevent errors.
  • When adding multiple AI21 models via the Admin UI, test credential binding by selecting an existing credential and verifying that the correct API key is applied to each model.
  • Consider testing the Admin UI functionality with a fresh credential to isolate the issue.

Example

No code snippet is provided as the issue is more related to configuration and UI interaction.

Notes

The provided curl command can be used to verify the available AI21 models, but it requires a valid API key. The issue with credential binding in the Admin UI may be specific to the implementation and requires further investigation.

Recommendation

Apply workaround: Update the AI21 model list and investigate credential binding issues, as the root cause of the problem seems to be a combination of outdated model information and potential UI bugs.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING