docs: add Crusoe to LLM providers - #6530
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe LLM documentation adds a Crusoe provider accordion with ChangesCrusoe provider documentation
Merge Risk: ⚪ Minimal · up to This documentation-only change adds Crusoe provider configuration and LiteLLM usage guidance. No current merge-readiness risk is identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hey @lorenzejay @vinibrsl, friendly ping on this one. It's a small docs-only entry adding Crusoe to the LLM provider list, should be a quick look. Glad to adjust formatting or placement if the docs structure has moved since I opened it. |
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
Hi @Vidit-Ostwal, would you mind taking a look at this docs entry when you get a chance? It is a small addition to the LLM providers page. I just synced the branch with main so it should be ready for a one-click merge. |
|
Hi @Vidit-Ostwal, circling back on this small docs addition for the Crusoe LLM provider entry. Branch is synced with main. Would appreciate a quick look when you have a chance. |
|
Hey @acheamponge, do you mind opening an issue, to track this one better. I do have an internal sync today to understand how exaclty I need to tackle new providers and what's the best course if yes, |
|
Thanks for the pull request. First-time contributors need an associated open issue before we can review a PR.
See the contributing guide. |
Refreshes the entry to the models on Crusoe Managed Inference today (GLM 5.x, Kimi K2.6, DeepSeek V4, Qwen3 235B Instruct 2507, gpt-oss-120b, Nemotron 3, Llama 3.3), with a link to the full catalog.
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
Closes #7264
What
Adds Crusoe to the LLM providers list in
docs/edge/en/concepts/llms.mdx, following the same accordion format as the other LiteLLM-backed providers (Fireworks AI, Perplexity AI, etc.).Why
Crusoe is an existing LiteLLM provider (BerriAI/litellm#23195, merged), so
LLM(model="crusoe/<model>")already works in CrewAI today via thecrewai[litellm]extra — it just isn't documented. This is a docs-only change; no code is touched.Crusoe provides OpenAI-compatible managed inference for leading open-weight models (GLM 5.2, Kimi K2.6, DeepSeek V4, Qwen3 235B, gpt-oss-120b, NVIDIA Nemotron 3, Llama 3.3, and more) on renewable-powered GPU infrastructure.
Verification
crusoe/meta-llama/Llama-3.3-70B-Instructmatches LiteLLM's routing (seetests/test_litellm/llms/crusoe/test_crusoe.pyin the LiteLLM repo)CRUSOE_API_KEYis the env var LiteLLM's Crusoe provider reads