The model list returned by kaggle models list shows only a small subset of models (primarily lower-tier ones), while Kaggle notebook environments can successfully call a much broader range of models, including many high-tier commercial ones.
This inconsistency is undocumented and affects discoverability. Users have no way to know which models are actually available in notebooks without trial and error.
Expected behavior:
- CLI should expose the same model list available in notebook environments, or
- Documentation should clearly explain the difference in model access between CLI and notebooks
The model list returned by kaggle models list shows only a small subset of models (primarily lower-tier ones), while Kaggle notebook environments can successfully call a much broader range of models, including many high-tier commercial ones.
This inconsistency is undocumented and affects discoverability. Users have no way to know which models are actually available in notebooks without trial and error.
Expected behavior: